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.

Beta

The Bloomreach Engagement connector is currently in beta. Contact your Amperity representative to learn more.

This destination uses the Bloomreach Engagement API .

Important

Bloomreach Engagement has no API for setting segment membership directly. Amperity records membership as segment-addition and segment-deletion events that carry the segment name. To act on this membership in Bloomreach Engagement–for example, to target it in a campaign–build a segmentation in your Bloomreach Engagement project over these segment-membership events. Until that segmentation exists, the membership data is present in Bloomreach Engagement but is not yet usable as a segment.

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, counted as failed rows, and reported as an error on the run in Amperity.

Caution

Bloomreach Engagement allows a limited number of attributes per customer–255 by default, though this may vary based on your Bloomreach Engagement contract. An orchestration or campaign that sends more attributes than the limit 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

Amperity sends customer updates and segment membership changes to Bloomreach Engagement over the batch API and receives a result for each row in the same request. Rows that Bloomreach Engagement rejects are reported as failed, and the rejection reason is recorded as an error on the orchestration or campaign run in Amperity.

Warning

Attributes accumulate across everything sent to a Bloomreach Engagement project over time. If the project’s total number of distinct attributes would exceed Bloomreach Engagement’s per-customer attribute limit (255 by default), Bloomreach Engagement rejects the over-limit writes and Amperity reports them as errors on the run.