Braze integration with Amperity

Q: Can Amperity send data to Braze and bring Braze data back?

Yes, through separately configured connections. The Braze destination sends profile and custom attributes through the REST API. Braze Currents returns behavior and engagement events through Amazon S3, Azure Blob Storage, Google Cloud Storage, or the Streaming API.

Q: Has Salesforce acquired Braze?

On October 20, 2026, Salesforce announced an agreement to acquire Braze. The transaction remains subject to closing conditions.

Q: Should I use Amperity ID as the Braze external_id?

Use the identifier your Braze profiles already use. Amperity ID can be external_id, but do not substitute it for an established ID without an identity plan. Braze recommends the API external_id match the SDK identifier to avoid duplicate profiles.

Q: Can Amperity send events and purchases to Braze?

Profile attributes, cohorts, and purchase events use distinct connectors. Braze Purchases is in beta and sends purchase objects through /users/track. Braze limits legacy purchase events to existing eligible customers; new Braze customers should use its eCommerce recommended events. Confirm your supported path before setup.

Q: How often does Amperity update Braze?

Choose the orchestration or campaign schedule for the profile workflow. Amperity tracks changes and sends changed membership and selected attributes between syncs. Currents has its own export and ingestion route. These connections do not establish one universal end-to-end refresh interval.

Q: Can the integration update arrays or remove attributes?

Confirm array mapping and attribute removal for your selected Amperity connector before setup. Braze supports array operations and clearing many attributes with null in its API; the supported payload depends on the connector. Leaving a field out should not be treated as a deletion request.

Make Braze messaging more relevant with trusted customer context from Amperity. Send customer profile and custom attributes through the Braze REST API, and bring engagement events back through a separately configured Braze Currents connection.

Get a demo See the Braze docs

REST profile updates • Separate Currents import • Configurable identity

Personalize messages with unified purchase history and customer attributes.

Target lifecycle audiences using loyalty status and value tiers.

Refresh useful profile attributes as customer context changes.

Connect Braze engagement with purchase history for your next audience decision.

How Amperity and Braze connect

Match the customer identity. Select external_id, braze_id, or user_alias and return the matching identifier columns in your dataset.
Map the context Braze needs. Shape profile fields and custom attributes to the names used in your Braze workspace.
Configure and validate the destination. Add Braze credentials and instance settings, then check a sample audience in Braze before production.
Schedule the updates. Use campaigns or query orchestrations to send profile attributes; configure Currents separately to return engagement events.

Profile updates and inbound engagement use separate connections.

What the Braze integration supports

Capability	Supported behavior
Direction and method	Outbound: Braze REST API. Inbound: separate Braze Currents connection through cloud storage or Streaming API.
Objects	Profile and custom attributes; separate connectors for cohorts and beta purchase events.
Identifiers	Select external_id, braze_id, or user_alias. Aliases require alias_name and alias_label.
Refresh and updates	Scheduled profile sends with change tracking. Purchase runs resend every returned row without cross-run deduplication.
Authentication	Braze REST API key and instance. Currents storage credentials or Streaming API configuration are separate.

Map Amperity data to the right Braze object

Use the connector that fits the object. Sending purchase history as a custom attribute enriches a profile; it does not record a Braze purchase event.

Object	Amperity output	Braze object or field	Boundary
User profile attributes	given_name, surname, birthdate	first_name, last_name, dob	Use exact lowercase standard field names. Amperity docs • Braze docs
Custom attributes	lifetime_order_revenue, one_and_done	Brand-defined attribute names	Match existing names; unmatched names create new attributes. Amperity docs • Braze docs
User identity	Selected identifier columns	external_id, braze_id, or user_alias	Send only the configured identifier type. Amperity docs • Braze docs
Cohort membership	List of user IDs	Named cohort	Braze Cohorts sends IDs only and does not create profiles. Amperity docs • Braze docs
Purchase object, beta	product_id, price, currency, purchase_time	product_id, price, currency, time	Separate Braze Purchases connector; confirm legacy purchase eligibility. Amperity docs • Braze docs

What teams do with Amperity and Braze

Move first-time buyers toward a second order

Build a contactable audience in Amperity using purchase history and lifecycle attributes, then send the relevant profile fields and custom attributes to Braze. For example, use a one-time purchaser flag and a value tier to distinguish customers who need an introduction to another category from customers ready for a loyalty message. Use those attributes in Braze segmentation and personalization, with Braze retaining control of campaign delivery and subscription status.

Use message response to refine the next audience

Configure Braze Currents to return selected engagement events, such as email clicks or push opens, to Amperity. Bring that response data together with available customer and transaction history to build the next audience. A customer who clicked a message and later bought in a store can be evaluated differently from a customer with no subsequent purchase. Configure the inbound route and refresh schedule explicitly so audience decisions reflect the data actually available.

Set up the Braze connection with the right controls

An operator configures the destination before users can select it. Amperity’s profile connector guide specifies a REST API key with users.track, users.export.segment, and segments.list permissions, plus the correct Braze instance. Validate field names and the sample output before sending full audiences.

Keep Braze as the source of truth for customer consent and subscription status. Apply contactability criteria to outbound audiences, and decide whether the destination should update existing profiles only or create unmatched profiles. Removing someone from a source audience is not a request to delete their Braze profile.

Braze connector guide Braze Currents guide

Braze integration FAQs

Can Amperity send data to Braze and bring Braze data back?

Has Salesforce acquired Braze?

Should I use Amperity ID as the Braze external_id?

Can Amperity send events and purchases to Braze?

How often does Amperity update Braze?

Can the integration update arrays or remove attributes?

Put customer context to work in Braze

Explore how your customer history, identifiers, and audience rules can support more relevant Braze messaging.

Get a demo