Bloomreach integration with Amperity

Q: What data can Amperity send to Bloomreach?

Amperity sends query results or campaign audiences to Bloomreach Engagement. Selected non-identifier fields become customer properties; audience membership follows the configured external-segment or membership-event route. This connection serves Engagement workflows.

Q: Which customer identifier should I use for Bloomreach?

Choose a hard identifier defined in your Bloomreach project and map an output field with exactly the same name. Blank primary IDs fail for those rows. Additional hard or soft IDs apply to property updates; membership uses the primary ID alone.

Q: Can I use Amperity audiences as Bloomreach segments?

Yes. Configuring an External segments integration makes membership available under Analyses > External segments. Without it, Amperity sends membership events; build a Bloomreach segmentation over those events before targeting the audience.

Q: Is the Amperity Bloomreach integration real time?

The connection runs through Amperity campaigns or query orchestrations. An orchestration can run manually or automatically after validation. Amperity sends changes since the previous run; bulk imports process asynchronously. Choose a workflow schedule that fits your outreach needs.

Q: How should I handle consent and empty customer properties?

Apply your consent criteria when defining audiences and configure Bloomreach’s messaging consent controls. Before production, test how your mapped properties handle empty values and removals with your Amperity representative; agree on the intended clearing behavior for each field.

Send customer properties and audience membership from Amperity to Bloomreach Engagement through its APIs. Use customer context to tailor outreach, with external segments or membership events selected by your configured credentials.

Get a demo See the Bloomreach docs

Customer properties • External segments • Membership events

Make Bloomreach outreach more relevant

Tailor messages with purchase and loyalty context selected in Amperity.

Focus retention outreach on customers who meet your audience criteria.

Reduce irrelevant follow-ups as customers leave an Amperity audience.

Keep campaign targeting aligned with refreshed customer attributes.

How the Amperity Bloomreach integration works

Choose the customer context. Build an Amperity query or campaign audience and select the properties to send.
Align customer identity. Include a field matching the configured Bloomreach hard identifier; optional additional identifiers accompany property updates.
Send properties and membership. Amperity updates profiles and sends audience additions and removals through the membership route configured in the credential.

The credential selects the membership route; customer properties are sent separately.

What the Bloomreach Engagement integration supports

Capability	Supported behavior
Direction and data	Amperity → Bloomreach Engagement: customer properties and audience membership.
Identity	Project-defined primary hard ID; optional additional hard or soft IDs for property updates.
Audience membership	External segments credential: adds/removes membership. Otherwise: amperity-segment events with segment_name and action = addition or deletion.
Refresh and delivery	Changes since the previous run. Properties and fallback events: batch through 500,000 rows per lane, Imports API above. External membership: separate API, never Imports.
Authentication	Project API base URL, token, key ID and secret. External membership additionally needs its integration ID and access key.

How Amperity data maps to Bloomreach objects

Bloomreach object	Amperity mapping	Connector details	Vendor reference
Customer properties	Selected non-identifier columns become properties on identified customer profiles.	Amperity mapping	Bloomreach API
External segments	Configured external integration stores membership as ext_segment_<name>: true on entry, false on exit.	Amperity mapping	Bloomreach API
Membership events	Without external integration: amperity-segment records segment_name and addition/deletion action.	Amperity mapping	Bloomreach API

Put Amperity customer context to work in Bloomreach

Tailor repeat-purchase outreach

Build an Amperity audience around the purchase and loyalty information available in your customer data, then send selected properties to Bloomreach. For example, a team could use purchase recency and loyalty tier to shape different messages for recent buyers and customers due for a follow-up. Keep message creation and campaign execution in Bloomreach, where the team can use those properties alongside its existing engagement data to choose the appropriate outreach.

Keep retention targeting aligned with audience changes

Define who qualifies for retention outreach in Amperity, then maintain that audience in Bloomreach as customers enter or leave. With an External segments integration configured, membership is available as a boolean customer property for targeting. With the event route, first build a Bloomreach segmentation over membership changes. This lets the team use the Amperity audience definition in its Bloomreach campaigns while accounting for customers whose circumstances have changed since the previous run.

Set up the Bloomreach Engagement connection

Ask your Datagrid Operator or Amperity representative to configure the destination. Supply the project API base URL, project token, API key ID, and API secret; permit customer updates, event tracking, and imports, including import creation and deletion permissions.

For external segments, also provide the integration ID and access key from the same Bloomreach project. Its hard identifier must match the destination’s primary identifier.

Check attribute capacity across the project before sending new fields or external segments. The default allowance is 255 distinct attributes, subject to contract; external segments consume one attribute each. Review import history and notifications after bulk runs because import acceptance precedes processing completion.

Configure destination

Bloomreach integration FAQs

What data can Amperity send to Bloomreach?

Which customer identifier should I use for Bloomreach?

Can I use Amperity audiences as Bloomreach segments?

Is the Amperity Bloomreach integration real time?

How should I handle consent and empty customer properties?

Give Bloomreach campaigns more useful customer context

Explore how your customer properties and audiences can support more relevant outreach in Bloomreach.

Get a demo