---
title: Braze (Device Mode)
slug: braze-device-mode
docTags: 
createdAt: 2025-05-29T21:51:16.313Z
---

# Introduction

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. It connects user behavior data with messaging tools, enabling marketers to create targeted, automated campaigns that drive retention, conversion, and loyalty—all from a single platform.

# Getting started

This is a device mode destination. You will need the Braze API key to connect this destination. **Note that this key is distinct from your Braze 'Classic' API key. **

You can find the correct API key under **Settings > App Settings > Web > API key**.

# Connecting to the Braze (Device Mode) CDP destination

1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Braze (Device Mode) **from the destination catalog.
5. Enter in the destination name and the **Braze API key**. 
6. Click **"Create" **to connect.

# Chord events relevant for destination

Not all Chord Tracking events are used downstream in your configured destinations. The most relevant and important events in the Chord tracking plan are mapped within the CDP destination, relayed and then ingested in the destination. The Chord tracking plan events used by the [Braze (Device Mode)](https://docs.customer.io/integrations/data-out/connections/braze/#track-event) destiantion are: 

| **Chord Tracking Event**   | *Destination Event*                      |
| -------------------------- | ---------------------------------------- |
| **Order Completed**        | *logPurchase*                            |
| **All Other Track Events** | *logCustomEvent*                         |
| **Identify**               | *getUser *(updates user attributes) |



:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream. ***
:::