> 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.md).

# Email

- [BigMailer](https://docs.coupler.io/sources/category/email/bigmailer.md): Connect BigMailer to Coupler.io to pull campaign performance, contacts, lists, and suppression data into sheets or dashboards.
- [BigMailer Best Practices](https://docs.coupler.io/sources/category/email/bigmailer/best-practices.md): Set up separate sources per BigMailer brand and use Append transformations to merge multi-brand email data cleanly.
- [Braze](https://docs.coupler.io/sources/category/email/braze.md): Connect Braze campaigns, canvases, and segments to Google Sheets or BigQuery via Coupler.io — automate marketing performance reporting.
- [Braze Best Practices](https://docs.coupler.io/sources/category/email/braze/best-practices.md): Join Braze list and analytics entities to build enriched dashboards combining campaign names with performance metrics like opens and conversions.
- [Brevo](https://docs.coupler.io/sources/category/email/brevo.md): Connect Brevo to Coupler.io to sync contacts, segments, campaign stats, and CRM deals into Google Sheets or data warehouses automatically.
- [Brevo Best Practices](https://docs.coupler.io/sources/category/email/brevo/best-practices.md): Optimize Brevo syncs by pairing contacts with attributes, using multi-source flows for list exports, and scheduling refreshes efficiently.
- [Campaign Monitor](https://docs.coupler.io/sources/category/email/campaign-monitor.md): Connect Campaign Monitor to Coupler.io to export email campaigns, subscribers, and performance metrics into Google Sheets, BigQuery, or your data warehouse.
- [Campaign Monitor Best Practices](https://docs.coupler.io/sources/category/email/campaign-monitor/best-practices.md): Set up Campaign Monitor exports with account-level API keys, historical date filters, and suppression list management for multi-client accounts.
- [Campayn](https://docs.coupler.io/sources/category/email/campayn.md): Pull Campayn contacts, lists, forms, and email reports into Google Sheets or BigQuery via Coupler.io for unified marketing analytics.
- [Campayn Best Practices](https://docs.coupler.io/sources/category/email/campayn/best-practices.md): Join Campayn Emails and Reports by campaign ID, aggregate metrics, and combine multi-account data for complete campaign visibility.
- [Kit](https://docs.coupler.io/sources/category/email/convertkit.md): Connect Kit to Google Sheets, BigQuery, or AI tools via Coupler.io. Export subscribers, broadcasts, sequences, and purchases automatically.
- [Kit Best Practices](https://docs.coupler.io/sources/category/email/convertkit/best-practices.md): Get accurate Kit exports — tips for filtering subscribers, combining entities, and keeping broadcast and purchase data clean.
- [Zoho Campaign](https://docs.coupler.io/sources/category/email/zoho-campaign.md): Connect Zoho Campaigns to Coupler.io to centralize email performance data, subscriber lists, and campaign reports for analysis across your business.
- [Zoho Campaigns Best Practices](https://docs.coupler.io/sources/category/email/zoho-campaign/best-practices.md): Join campaign details with performance reports, use Append for multi-account data, and optimize refresh schedules for accurate email campaign analysis.


---

# 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.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.
