Braze
What Is Braze?
Braze is a comprehensive customer engagement platform that enables businesses to create personalized marketing campaigns across multiple channels, including email, SMS, in-app messaging, and push notifications. It offers real-time data analytics and segmentation tools to help marketers understand and target their audience more effectively. The platform is designed for scalability and integrates easily with other marketing tools and systems, providing a seamless experience for managing customer interactions. Braze's focus on personalization and real-time engagement helps businesses enhance customer loyalty and drive growth.
What are the benefits of integrating MetaRouter with Braze?
- Up to 30% more customer data in Braze
- Real-time event stream that enables real-time journeys
- First-party, parameter-by-parameter control over data sent to Braze
- No Braze or other third-party tags required
Getting Started - From Your Braze Account
Create New REST API Key
- Please see Braze documentation HERE for instructions.
Braze Instance URL
- You can obtain the Braze instance URL from your Braze dashboard. It is typically provided during the account setup process and can also be found in account settings.
- If you are unsure of your instance URL, please contact Braze support for assistance.
Getting Started - From Your MetaRouter Account
Adding a Braze integration.
From the integration library, add a Braze integration. Then, fill out the Connection Parameters:
Connection Parameter | Description |
---|---|
INSTANCE_URL | The unique URL assigned to your Braze account that you use to interact with Braze's API. |
API_KEY | A unique code that is passed into an API to authenticate the API call and identify the calling application or user |
Event Mappings
MetaRouter provides all of the event mappings that Braze integrations typically require. You may add custom events, parameters or mappings in accordance with Braze’s API documentation.
Event Specific
Identify
Output Key | Description | Expected Input |
---|---|---|
external_id Required | String: External user identifier | userId |
user_alias.alias_name | String: Alias name for the user | anonymousId |
user_alias.alias_label | String: Alias label for the user | Enrichment - anonymous_id |
Page Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties | Object: Custom properties for the event | properties |
events.name | String: Name of the event | Enrichment - page |
Cart Viewed Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties.cart_id | String: Identifier for the cart | properties.cart_id |
events.properties.currency | String: Currency for the transaction | properties.currency |
events.name | String: Name of the event | Enrichment - cart_viewed |
Product Added Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties | Object: Custom properties for the event | input |
events.name | String: Name of the event | Enrichment - product_added |
Product Viewed Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties | Object: Custom properties for the event | input |
events.name | String: Name of the event | Enrichment - product_viewed |
Products Searched Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties | Object: Custom properties for the event | properties |
events.name | String: Name of the event | Enrichment - products_searched |
Product List Viewed Event
Output Key | Description | Expected Input |
---|---|---|
attributes.external_id Required | String: External user identifier | userId |
events.external_id Required | String: External user identifier | userId |
events.time | Date-Time: The time the event occurred | timestamp |
events.properties.category | String: Category of the product list | properties.category |
events.properties.list_id | String: Identifier for the product list | properties.list_id |
events.name | String: Name of the event | Enrichment - product_list_viewed |
Order Completed Event
Output Key | Description | Expected Input |
---|---|---|
N/A Required | Expression to transform data | N/A - Expression |
Required & Recommended Identifiers
These identifiers must be mapped to Braze in order for successful user matching to occur. Without these IDs, any events sent to Braze will be rejected. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.
Attribute | Example | Sync Injector Required? |
---|---|---|
external_id Required | user12345 | No |
user_alias.alias_name Recommended | 130161d0-8fee-4167-aa4d-d151eed27c6b | No |
Additional Braze Documentation
Updated 6 months ago