How to integrate Unify with Braze
To integrate Unify with Braze, configure a Unify Play Webhook action to call the documented API with POST, the required credentials, and the destination-specific JSON body. Use this connection to share selected account context with a Braze user profile.[1][2][3]
- Connection
- Via API
- Customer engagement
- Tool
- Braze
- Braze
- Data flow
- Unify → Braze
- JSON payload
At a glance
- Via API: Braze receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Send only a meaningful change
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
The most useful handoff adds context without rewriting customer history. Distinguish a prospect selected for review from a customer who completed an action. Use profile attributes for known state and reserve events for things that actually happened.
A good fit when
Teams that want to share selected account context with a Braze user profile and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Braze operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Business decision | Share selected account context with a Braze user profile |
| Receiving contract | Agree which of the 2 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Braze request and its resulting action. |
| Completion | Decide who can confirm the Braze outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Share selected account context with a Braze user profile
Start with one controlled record and one intended Braze outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Braze setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Send only a meaningful change
Send only a meaningful change: compare a repeated identical record with a record whose source-owned company attribute changed. Have the receiver suppress unnecessary writes if the volume warrants it.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Braze against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Share selected account context with a Braze user profile
Inspect the intended user profile and changed attributes. Review the response for errors and validate any downstream audience separately.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Braze.
Should every prospect handoff become a purchase or engagement event?
No. users/track accepts several kinds of data, but the chosen object must reflect the observed fact. This example updates an attribute rather than inventing customer activity.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Braze processes submitted data as supplied. Repeated unchanged attributes can consume data points; invented engagement events distort downstream logic.[3]
- API and trigger access depend on the destination account, permissions, and configuration. This request pattern is not a claim of native Unify sync.[3]
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Braze workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Agree on the external_id already used in Braze. Do not invent a second user identity from the person’s display name.[3] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Braze connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Braze environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Prepare the Braze destination
Agree on the external_id already used in Braze. Do not invent a second user identity from the person’s display name.[3]
Configure the destination action
Send only changed attributes through users/track. Add event objects only when the Play represents a real, named event whose meaning is agreed with analytics and marketing.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]
Request configuration
- Method
POST- URL pattern
https://YOUR_BRAZE_REST_ENDPOINT/users/track- Headers
Content-Type: application/jsonAuthorization: Bearer YOUR_BRAZE_REST_API_KEY- Authentication
- Use a Braze REST API key with users.track permission as a Bearer token. Copy the REST endpoint for your Braze instance.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"attributes": [
{
"external_id": "example-person-001",
"company_name": "Example Company"
}
]
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]
| Payload field | Value to send |
|---|---|
attributes.0.external_id | Map the stable identity used by this destination to the same person or company in your source. This example identifier is not a documented Unify variable. If missing: Hold the handoff rather than creating an anonymous or incorrectly matched record. |
attributes.0.company_name | Select the available company name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
attributes is an array of user updates. Map the stable external_id separately from custom profile attributes such as company_name.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
Use a Braze REST API key with users.track permission as a Bearer token. Copy the REST endpoint for your Braze instance. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Braze environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Braze resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
