> 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/brevo/best-practices.md). # Brevo Best Practices Optimize Brevo syncs by pairing contacts with attributes, using multi-source flows for list exports, and scheduling refreshes efficiently. ## Recommended setup


Export Contacts attributes alongside Contacts	The Contacts entity alone won't tell you what your custom fields mean. Always add Contacts attributes as a second source in the same data flow so you have field definitions handy.
Use multiple sources in one data flow for list-level contact exports	If you need contacts from several lists, add each list as a separate Contacts lists contacts source and use the Append transformation to combine them into one output table.
Join CRM deals with pipeline stages	CRM deals contain a stage ID, not a stage name. Add CRM pipeline stages as a second source and Join on stage ID to get human-readable stage names in your reports.
Whitelist IPs before connecting	Add Coupler.io's IPs (`34.123.243.115` and `34.170.96.92`) to your firewall or security group before you create a data flow. This prevents "connection refused" errors and saves troubleshooting time.

## Data refresh and scheduling


Wait a few hours after a campaign send before syncing	Open and click metrics continue updating after a send. Scheduling a sync several hours post-send gives you more settled engagement data rather than preliminary counts.
Use a fixed start date for campaign history	Set your start date to the earliest campaign you care about and leave it fixed. This avoids re-pulling the same historical data unnecessarily on every sync.

## Performance optimization


Separate high-volume contact exports from CRM syncs	If you have a large contact database, running it in the same data flow as CRM entities can slow things down or trigger rate limits. Keep contact-heavy and CRM-heavy flows separate.
Use Aggregate for campaign reporting	Instead of exporting every campaign row to a spreadsheet, use the Aggregate transformation to summarize metrics (e.g., total sends, average open rate by month) before writing to the destination.

## Common pitfalls {% hint style="danger" %} Do not share or commit your Brevo API key to public repositories or spreadsheets. If exposed, regenerate it immediately in Brevo under Account settings → SMTP & API → API Keys, then update the key in your Coupler.io data flow. {% endhint %} {% columns %} {% column %} **Do** * Add Contacts attributes as a companion source when exporting Contacts * Join CRM deals with pipeline stages for readable stage names * Verify an entity has data in Brevo before troubleshooting a missing-data issue in Coupler.io * Use Append to merge email and SMS campaign data into a single performance table {% endcolumn %} {% column %} **Don't** * Use a restricted API key if you need access to CRM or account-level entities * Expect real-time accuracy on open/click rates immediately after a campaign send * Pull Contacts lists contacts without first confirming the target list has subscribers {% endcolumn %} {% endcolumns %} --- # 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.coupler.io/sources/category/email/brevo/best-practices.md?ask=&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.