> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/email-and-marketing/braze.md).

# Braze

Braze is a customer engagement platform that helps brands deliver personalized, real-time messaging across channels like email, push notifications, SMS and in-app messages. Chord forwards ecommerce events, such as purchases, user behavior and identity updates, to Braze, so marketers can trigger personalized campaigns from real-time shopper actions without manual data pipelines. Chord sends events to Braze from the browser and from the server.

## Use cases

* **Post-purchase messaging**: trigger order confirmation flows, upsell sequences or review requests in Braze when a customer completes an order.
* **Customer attribute sync**: keep Braze user profiles updated with the latest customer data from Chord to improve segmentation.
* **Behavioral retargeting**: use Chord event data to power win-back or re-engagement campaigns in Braze for customers who haven't converted recently.

## What each version does

* [**Braze browser**](/activate/event-streaming/destinations/email-and-marketing/braze/braze-browser.md) loads the Braze Web SDK in the shopper's browser and sends events from there. In Chord, you add it as **Braze (Device Mode)**.
* [**Braze server**](/activate/event-streaming/destinations/email-and-marketing/braze/braze-server.md) sends events to Braze's REST API from Chord's servers. In Chord, you add it as **Braze**.

## Why use both

The browser version catches on-page behavior. The server version survives ad blockers and closed tabs. Using both gives you the most coverage.

## Prerequisites

You need a Chord account and a Braze account. The two versions use two different Braze API keys, so each version page tells you where to find its key and endpoint.

## What Chord sends

Chord sends every `track` event to Braze. In the browser version, `Order Completed` is sent as a Braze purchase. In the server version, `Order Completed`, `Order Cancelled` and `Order Refunded` are sent as purchases. Every other `track` event is sent as a Braze custom event. See each version page for the full mapping.

## Troubleshooting

If you can't see events arriving in Braze, check the following.

1. **Check that live events are arriving in Chord.** In the [Live Events](/activate/event-streaming/live-events.md) tab, verify that your relevant sources are firing events. Without live events, there is nothing to pass to Braze.
2. **Check your Braze destination settings.** Confirm the API key, SDK version and endpoint are correct.
3. **Check that the destination is connected to a source** in Chord.
4. **Check that events are sent to Braze.** In **Live Events > API Destinations & Functions Logs**, confirm that events fire and send successfully. Look for successful hits to the `/users/track` and `/users/identify` endpoints.
5. **Confirm the events in your Braze dashboard.**

## Set up

* [Braze browser](/activate/event-streaming/destinations/email-and-marketing/braze/braze-browser.md)
* [Braze server](/activate/event-streaming/destinations/email-and-marketing/braze/braze-server.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/destinations/email-and-marketing/braze.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.