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.

This destination uses the Bloomreach Engagement API .

Important

Amperity sends segment membership to Bloomreach Engagement in one of two ways, depending on the credential.

• As an external segment, when the credential has an External segments integration. Amperity registers the segment in Bloomreach Engagement under the Segment name, and then adds and removes customers as their membership changes. The segment appears in Bloomreach Engagement under Analyses > External segments and is stored on each customer profile as the boolean property ext_segment_<name>: true while the customer is in the segment, and false after the customer leaves it. The segment is ready to use in Bloomreach Engagement without further setup. Depending on how the integration is configured, a customer ID that matches no profile either creates a profile or is ignored. External segment membership updates count against your Bloomreach Engagement project’s monthly customer update limits.

• As segment membership events, when the credential has no External segments integration. Amperity records each change as an amperity-segment event whose segment_name property holds the segment name and whose action property is addition or deletion. 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 events. Until that segmentation exists, the membership data is present in Bloomreach Engagement but is not 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 limits the number of distinct attributes in a project (255 by default, though this may vary based on your Bloomreach Engagement contract). An orchestration or campaign whose query or segment has more attributes than the limit fails with an error before any data is sent. When segment membership is sent as an external segment, Amperity reserves one attribute for the segment’s ext_segment_<name> property, so the query or segment may contain at most 254 attributes.

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 only what changed since the previous run. For each run, Amperity chooses how to send each lane of data–customer attribute updates and segment membership changes are separate lanes–based on how many rows that lane contains:

• Up to 500,000 rows in a lane are sent over the Bloomreach Engagement batch API, and Amperity 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.

• More than 500,000 rows in a lane are sent over the Bloomreach Engagement Imports API as one bulk file. Bloomreach Engagement accepts each import and processes it afterward, and does not return per-row results. The run reports success when Bloomreach Engagement accepts the import, not when its rows finish processing. Import outcomes surface only in Bloomreach Engagement: in the import history in the Bloomreach Engagement console (retained for 30 days) and in ImportError and ImportRowsDiscarded notifications to project users. Because processing is progressive, an import that fails partway may leave rows partly applied.

The two lanes cross this threshold independently, so a single run may use the batch API for one lane and the Imports API for the other.

When segment membership is sent as an external segment, the membership lane never uses the Imports API, however many rows it contains. Amperity sends additions and removals in requests of up to 5,000 customer IDs and receives a result for each customer ID. Customer IDs that Bloomreach Engagement rejects (for example, an ID longer than 256 bytes) and audience members with no value for the Bloomreach identifier are counted as failed membership changes and reported as errors on the run, with a count for each reason. The first run that sends a segment as an external segment, including the first run after an External segments integration is added to the credential, sends every member of the audience, even if the audience has not changed. Bloomreach Engagement accepts about 1,000 customer IDs per second for external segment updates, so a large first load takes time: about 19 minutes per million members.

Warning

Attributes accumulate across everything sent to a Bloomreach Engagement project over time, and the attribute limit applies to the project’s total number of distinct attributes, not to each customer profile. Each external segment also uses one of these attributes. Once the project is at the limit:

• An update that would add a new attribute is discarded as a whole. Over the batch API (up to 500,000 rows), Bloomreach Engagement accepts the update and returns no error, so the run reports these rows as succeeded. Over the Imports API, the failure surfaces only in Bloomreach Engagement’s import history and notifications, as described above.

• Registering a new external segment fails, and the run stops with an error saying that the Bloomreach Engagement project has no room for another external segment.

Updates to attributes the project already has are not affected. To make room, remove unused attributes or external segments in Bloomreach Engagement, or ask Bloomreach Engagement to raise the limit.

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.