Amperity

Amperity resolves customer identities and builds unified customer profiles from your data sources. Connect it to Marketing to bring those profiles and audiences into your project, and then use the data in segmentations, campaigns, and scenarios. You can also send Marketing data back to Amperity.

How the integration works

Amperity sends data to your Marketing project through the Marketing API. You configure and run the connection in Amperity, and Amperity owns the sending behavior, so this page covers only what you prepare in Marketing.

Amperity can send two types of data:

• Query results: Customer properties from an Amperity query. Read the Amperity guide to sending query results.
• Audiences: Segments from an Amperity campaign. Read the Amperity guide to sending audiences.

Amperity chooses between the batch API and the imports API based on the size of each run. For the current thresholds and limits, read the Amperity guide to configuring destinations.

Before you start

Complete these tasks in your project before you connect Amperity.

Choose your identifiers

Amperity matches each row to a customer profile with one primary identifier. Choose a hard ID from your project, and enter its name in Amperity exactly as your project defines it.

• Hard IDs are case sensitive, so convert them to lowercase to prevent duplicate profiles.
• You can't rename or delete an identifier after you set it.
• You can't change a soft ID into a hard ID.

To send more identifiers with each profile, use the additional identifier setting in Amperity. For the current options, read the Amperity guide to configuring destinations. For details about hard and soft IDs, read the customer identification documentation.

Create an API key

Amperity connects with a private API key. Create a private API group, set its permissions, and generate an API key ID and API secret.

1. Go to Project settings > Access management > API.
2. Create an API group with private access.
3. Select the permissions that Amperity requires. For the current list, read the Amperity guide to configuring campaigns.
4. Generate an API key ID and API secret for the group.

Limit access to the API secret to the people who configure Amperity. For details about API groups, read the API authentication documentation.

Check your attribute limit

The number of attributes each customer profile can hold depends on your contract: 255 or 1,024. Attributes from every source count toward the limit, including the data Amperity sends.

Review the attributes Amperity sends before your first run. For details, read the customer attribute limits documentation.

Share your credentials with Amperity

Amperity needs four values to connect to your project:

• API base URL
• API key ID
• API secret
• Project token

Find the API base URL and project token at Project settings > Access management > API. Use the API key ID and API secret from the private API group you created.

For how to share the values and enter them in Amperity, read the Amperity guide to configuring campaigns.

Create a segmentation from Amperity audiences

Marketing has no API for setting segment membership directly. Amperity records membership as events instead. When a customer enters or leaves an audience, Amperity tracks an event that stores the audience name. For the current event names and properties, read the Amperity guide to sending audiences.

The membership data exists in your project, but you can't target it until you build a segmentation over these events.

1. Go to Analyses > Segmentations.
2. Click the + sign next to Segmentations.
3. Define a segment with a customer filter on the membership event, where the audience name matches your Amperity audience.
4. Save the segmentation.

Saving creates a customer attribute that you can use in analyses, filters, and campaigns. For details, read the segmentations documentation.

Monitor syncs

Amperity reports run results on its side, and large runs behave differently from small ones. For how Amperity reports each type of run, read the Amperity guide to configuring destinations.

In Marketing, check these places when a large sync doesn't look right:

• The import run history, which shows jobs from the last 30 days.
• The ImportError and ImportRowsDiscarded notifications, which go to users with permission to update imports.

For details, read the data imports documentation.

Send data from Bloomreach to Amperity

You can send customer and event data from Marketing to Amperity, such as consent, segment membership, and engagement history, with our standard export methods.

• Data exports (batch): Send customer or event data as files to your own storage, such as SFTP or Amazon S3, so Amperity can read them. Read the data exports documentation and Set up data exports.
• Webhooks (near real time): Send a request from a scenario to an endpoint when a customer reaches a point in the flow. Read the webhooks in scenarios documentation.

Learn more

• Amperity guide to configuring campaigns
• Amperity guide to configuring destinations
• Amperity guide to sending audiences
• Amperity guide to sending query results