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

# FAQ

<details>

<summary>Which Braze entities should I start with?</summary>

If you're building a marketing performance dashboard, start with **Campaigns analytics** and **Canvases analytics** — these have the most actionable metrics (sends, opens, clicks, conversions, revenue). Add **KPI daily new users** and **KPI daily active users** if you also want growth metrics in the same workspace.

</details>

<details>

<summary>What's the difference between the list, analytics, and details entities?</summary>

* **List entities** (Campaigns, Canvases, Segments, Events, Cards) return metadata — names, IDs, tags, active status.
* **Analytics entities** return time-series performance metrics — daily breakdowns of sends, opens, clicks, segment sizes, event counts, etc.
* **Details entities** return structural/configuration data — the actual setup of a campaign, the step logic of a canvas, or the filter rules of a segment.

For reporting, you'll mostly use analytics entities. Use list entities to enrich analytics data with human-readable names via a Join transformation.

</details>

<details>

<summary>How do I find my Braze REST endpoint URL?</summary>

In Braze, go to **Settings → Developer Console**. Your REST endpoint is displayed at the top of the page and looks like `https://rest.iad-01.braze.com`. The number and prefix change based on your region (US, EU, AU, etc.). Use exactly this URL when configuring your Coupler.io data flow.

</details>

<details>

<summary>Can I sync data from multiple Braze workspaces?</summary>

Yes. Each Braze workspace has its own API key and REST endpoint. Create a separate source connection in Coupler.io for each workspace, then use the **Append** transformation to combine data from multiple workspaces into a single destination table. This is useful for agencies or businesses that manage multiple brands under separate Braze workspaces.

</details>

<details>

<summary>Why does my analytics data look different from what I see in the Braze dashboard?</summary>

Braze's API returns data in UTC, while the dashboard may display data adjusted to your workspace timezone. Attribution windows (how conversions are counted) can also differ. When comparing API data to the dashboard, account for these timezone and attribution differences. See the Data Discrepancies section for more detail.

{% hint style="info" %}
For a full list of known discrepancy causes, see [Common Issues](/sources/category/email/braze/common-issues.md).
{% endhint %}

</details>

<details>

<summary>Can I use Braze data with AI tools through Coupler.io?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route campaign performance data or KPI trends directly to these tools for automated analysis, anomaly detection, or content recommendations.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

Use the date picker in the source settings to set a start date. Braze's API supports historical analytics data, but very long date ranges (e.g., 2+ years of daily data across many campaigns) can result in slow syncs or rate limit errors. For initial historical loads, consider splitting the range across a few manual runs before switching to incremental daily updates.

{% hint style="info" %}
For tips on managing large syncs efficiently, see [Best Practices](/sources/category/email/braze/best-practices.md).
{% endhint %}

</details>

<details>

<summary>What permissions does my Braze API key need?</summary>

Your API key needs read access to the specific endpoints Coupler.io calls. At minimum:

* `/campaigns/list` and `/campaigns/data_series` for campaign data
* `/canvas/list` and `/canvas/data_series` for canvas data
* `/segments/list` and `/segments/data_series` for segment data
* `/events/list` and `/events/data_series` for event data
* `/feed/list` and `/feed/data_series` for cards data
* `/kpi/new_users/data_series`, `/kpi/dau/data_series`, `/kpi/uninstalls/data_series` for KPIs

If you get a 403 error on a specific entity, that endpoint permission is likely missing from your key.

{% hint style="info" %}
See [Common Issues — Permission Errors](/sources/category/email/braze/common-issues.md) for troubleshooting steps.
{% endhint %}

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/email/braze/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.