Send audiences 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 required to configure campaigns to send customer profiles to Bloomreach Engagement.

Note

Ask your DataGrid Operator or your Amperity representative for help configuring Bloomreach Engagement as a destination to which you can send campaigns for customer activation.

Caution

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

If this destination cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending campaign audiences to Bloomreach Engagement.

Build a segment

Use the Segment Editor to build any audience using a series of drop-downs and picklists.

As you define the attribute profile for an audience be sure to refresh segment insights to view audience size and to see the value it brings to your business.

When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.

About paid media campaigns

You can use any attribute that is in your customer 360 database to define your audience.

When sending the list of customers who belong to this audience to Bloomreach Engagement as part of a campaign you must choose specific attributes to send.

Bloomreach Engagement supports the following attributes: customer profiles.

Important

The segment you build must include an attribute named to match the Bloomreach identifier selected for the destination, such as email, external ID, cookie, or Google Analytics ID. If no attribute matches, the campaign fails with an error before any data is sent. All other attributes in your segment are sent as customer properties to Bloomreach Engagement. Rows with blank values in the identity column are skipped, counted as failed rows, and reported as an error on the run.

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 to a campaign

Use the campaign editor to configure Amperity to send data to Bloomreach Engagement. Add a segment, define exclusions and sub-audiences, and then define each audience sent to Bloomreach Engagement.

To add a campaign for Bloomreach

	Open the Campaign Editor. This is available from the Campaigns page. Click the Create campaign button in the top right corner of the page.
	Assign Bloomreach Engagement as a destination for at least one treatment group. Note You may need to edit the attributes for the sub-audience to ensure Amperity is sending the right data to Bloomreach Engagement.
	Click Edit attributes to review the attributes that Amperity sends to Bloomreach Engagement. email, cookie, google_analytics, or external_id Amperity pre-selects the list of attributes sent to Bloomreach Engagement. The Edit attributes page for Bloomreach Engagement is similar to: Note The Merged Customers table is the default table for sending data to Bloomreach Engagement, even though segments are often built against the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table.

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.

Configure default attributes

Each unique destination configured to send treatment group audiences to Bloomreach Engagement has a set of default attributes.

Configure default attributes by clicking the Default attributes link next to the Create campaign button on the Campaigns page.

The source table defaults to the Merged Customers table for most attributes. This is configurable.

Source attribute	Destination attribute
email	email The email address for the customer. This is a Bloomreach hard identifier.
external_id	external_id An external identifier for the customer, such as the Amperity ID. This is a Bloomreach hard identifier.
cookie	cookie A cookie identifier for the customer. This is a Bloomreach hard identifier.
google_analytics	google_analytics A Google Analytics identifier for the customer. This is a Bloomreach hard identifier.
given_name	given_name The first name of the customer.
surname	surname The last name of the customer.
birthdate	birthdate The birthdate of the customer.
city	city The city in which the customer lives.
state	state The state in which the customer lives.
postal	postal The ZIP code or postal code for the customer.
phone	phone The phone number for the customer.
gender	gender The gender of the customer.