Braze
Platform Summary
Braze users.track and event object contracts.
Scope
Primary execution surface: server.
Developer Source Map
| Source | Reason |
|---|---|
| Braze Event Object | Event Contracts; event fields, required schema |
| Braze Track Users Endpoint | Transport / Payload Rules; User Data Contracts; events, payload, user data |
RudderStack Cross-Check
RudderStack is used here only as secondary engineering evidence for discovery and cross-check.
| Destination | Type | Link |
|---|---|---|
braze | Discovery lead | source |
Verified Contracts
Event Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
event_object | name | server | string | Required | Custom event name string. | Not clearly specified | Not clearly specified | - | Braze Event Object requires name. | Braze Event Object | Verified | High |
event_object | properties | server | object | Optional | JSON object of event properties. | Not clearly specified | Not clearly specified | - | Event properties are optional and object-typed. | Braze Event Object | Verified | High |
event_object | time | server | string | Required | Datetime string (ISO 8601 accepted). | Not clearly specified | Not clearly specified | - | Braze Event Object requires time. | Braze Event Object | Verified | High |
User Data Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
users.track | external_id | server | string | Conditional | Primary user identifier string. | Not clearly specified | Not clearly specified | - | external_id is a standard identifier in Braze tracking payloads. | Braze Track Users Endpoint | Verified | High |
users.track | identifier | server | string | Conditional | Each object should include one allowed identifier set. | Not clearly specified | Not clearly specified | - | Identifier rules are explicitly documented for /users/track. | Braze Track Users Endpoint | Verified | Medium |
Transport / Payload Rules
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
users.track | attributes | server | array<object> | Optional | Array of User Attributes Objects. | Not clearly specified | Not clearly specified | - | Attributes object schema is documented by Braze. | Braze Track Users Endpoint | Verified | High |
users.track | Authorization | server | string | Required | Authorization: Bearer <REST_API_KEY> | Not clearly specified | Not clearly specified | - | REST API key with users.track permission is required. | Braze Track Users Endpoint | Verified | High |
users.track | Content-Type | server | string | Required | application/json request header. | Not clearly specified | Not clearly specified | - | JSON payload is required. | Braze Track Users Endpoint | Verified | High |
users.track | endpoint | server | string | Required | POST https://<rest-cluster>/users/track | Not clearly specified | Not clearly specified | - | Braze users.track endpoint contract. | Braze Track Users Endpoint | Verified | High |
users.track | events | server | array<object> | Optional | Array of Event Objects. | Not clearly specified | Not clearly specified | - | Event object schema is defined in Braze Event Object docs. | Braze Track Users Endpoint | Verified | High |
Candidate / Needs Review Items
No candidate rows currently tracked.
Excluded Items
No excluded rows in this revision.
Last Reviewed
2026-03-31