> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/braze.md).

# Braze

Share segments with Braze as a user attribute, either an array element or a boolean.

The Braze connector shares your segments with Braze, where they arrive as an attribute on the user and can be used in Braze campaigns and journeys.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>User account IDs</td></tr><tr><td><strong>Authentication</strong></td><td>API token shared with your mediarithmics account manager</td></tr></tbody></table>

## Description

### What is Braze?

Braze is a customer engagement platform. A segment arriving from mediarithmics is written onto the Braze user as a custom attribute, which Braze then uses for targeting.

### What you can do with this connector

* Make a mediarithmics segment available as a Braze attribute, for use in campaigns and journeys.
* Choose how the segment is represented in Braze - as an element of an array, or as a boolean.
* Rename the segment on the Braze side without renaming it in mediarithmics.

### Which identifiers are sent

When you share a segment through this connector, mediarithmics can send:

* **User account IDs** - several different user account IDs can be used, so that the feed matches how Braze distinguishes anonymous from logged-in users.

## Connector setup

### Prerequisites

* A Braze account and an API token that grants access to your Braze environment.

### Authentication

Provide the API token to mediarithmics **in a secure way**. Your mediarithmics team updates your configuration to allow the connection; the feed then references it by **Client Name**. The feed cannot be created before that step is done.

### Setup steps

{% stepper %}
{% step %}
**Send your Braze API token to mediarithmics, securely.**
{% endstep %}

{% step %}
**Wait for your mediarithmics team to update your configuration.**
{% endstep %}

{% step %}
**Select the Braze connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="240">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed inside mediarithmics.</td></tr><tr><td><strong>Attribute type</strong></td><td><code>Array</code> or <code>Boolean</code>. See <a href="#good-to-know">Good to know</a>.</td></tr><tr><td><strong>Custom Segment Name</strong></td><td>Renames the segment on the Braze side.</td></tr><tr><td><strong>Client Name</strong></td><td>The client name used in your credentials file.</td></tr><tr><td><strong>Identifying resources</strong></td><td>The identifier types to send to Braze.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

**Attribute type** decides the shape your segment takes in Braze, and the two are not interchangeable:

<table data-search="false"><thead><tr><th width="160">Value</th><th></th></tr></thead><tbody><tr><td><strong>Array</strong></td><td>The segment becomes an element of the array property <code>mics_segments</code>.</td></tr><tr><td><strong>Boolean</strong></td><td>The segment becomes a boolean property carrying the same name as your segment.</td></tr></tbody></table>

## FAQ

#### Should I choose Array or Boolean?

`Array` keeps every mediarithmics segment inside one Braze property, `mics_segments`. `Boolean` creates one Braze property per segment, named after the segment. Pick according to how you want to filter in Braze.

#### Can I use more than one user account ID?

Yes. The connector accepts several user account IDs, which is how it accommodates the way Braze separates anonymous from logged-in users.

## Partner documentation

Braze documents its own platform at <https://www.braze.com/docs/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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.mediarithmics.io/connectors/destinations/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.