Send query results to Bloomreach

Bloomreach Engagement (formerly Exponea) is a customer data and marketing automation platform. Use Bloomreach Engagement to create personalized customer experiences across multiple channels.

Note

This destination uses the Bloomreach Engagement API .

The steps that are required to send customer profiles to Bloomreach Engagement from Amperity.

	Build a query
	Add orchestration
	Run orchestration

Caution

This destination is available for sending query results to Bloomreach Engagement after it is configured by a Datagrid Operator or your Amperity representative.

If this destination cannot be selected for orchestrations ask your Datagrid Operator or Amperity representative to configure a destination for sending query results to Bloomreach Engagement.

Build query

You will need to build a query that outputs the fields you want to send to Bloomreach Engagement. The query must include a Bloomreach hard identifier such as email, external ID, cookie, or Google Analytics ID. All other columns in your query results will be sent as customer properties.

The following example shows a query that returns customer profiles using email as the identifier:

SELECT
  email
  ,given_name
  ,surname
  ,city
  ,state
  ,postal
  ,birthdate
  ,gender
FROM Customer360
WHERE email IS NOT NULL

You can also use the Amperity ID as an external identifier:

SELECT
  amperity_id AS external_id
  ,email
  ,given_name
  ,surname
  ,phone
  ,lifetime_order_revenue
  ,lifetime_order_frequency
FROM Customer360
WHERE amperity_id IS NOT NULL

Important

Your query results must include a column named to match the Bloomreach identifier selected for the destination (for example, a column named email when the identifier is email). If no column matches, the orchestration fails with an error before any data is sent. Rows with blank values in the identity column are skipped.

Caution

Bloomreach allows at most 255 attributes per customer. The connector adds a segment-membership attribute to every customer, so a single orchestration or campaign can send at most 254 attributes. A send with more than 254 attributes fails with an error before any data is sent.

Add orchestration

An orchestration defines the relationship between query results and a destination, including the destination and the frequency at which an orchestration runs.

1. Open the Activations page, select the Orchestrations tab, and then click the Add orchestration button. This opens the Add orchestration dialog box.

2. From the Object type dropdown, select Query.

3. From the Object dropdown, select the query for which results is sent to Bloomreach Engagement.

4. From the Destination dropdown, select a destination that is configured for sending data to Bloomreach Engagement.

5. Verify all settings.

6. Set the workflow to Manual. You can change this to automatic later, after verifying the end-to-end workflow.

7. Click Save.

Run orchestration

Run the orchestration manually to validate that it works.

To run the orchestration

1. Open the Activations page, select the Orchestrations tab, and then open the menu for the Bloomreach Engagement orchestration. Select Run.

2. The Status column for the orchestration updates to say “Waiting to start”, after which the notifications pane updates to include a notification that shows the current status.

3. When the orchestration has run successfully, the status is updated to “Completed”.

Note

Bloomreach Engagement processes imports asynchronously after Amperity sends the data. Amperity reports rows as succeeded once the import is triggered. There is no import status tracking. To confirm a send or troubleshoot missing customer data, check the import in the Bloomreach Engagement dashboard.

Note

Attributes accumulate across all imports in a Bloomreach project. If a project exceeds 255 attributes, Bloomreach discards the over-limit import; Amperity does not track this cumulative total, so the failure appears only in the Bloomreach Engagement dashboard.