> 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/campaign-monitor.md).

# Campaign Monitor

Campaign Monitor is an email marketing platform that lets you create, send, and track email campaigns to your subscriber lists. It's used by marketing teams to manage contacts, build segments, and measure campaign performance. Connecting Campaign Monitor to Coupler.io lets you pull your email data into any destination for reporting and analysis.

## Why connect Campaign Monitor to Coupler.io?

* **Centralize your email data** — export campaigns, subscribers, and performance metrics into Google Sheets, BigQuery, or Excel without manual exports
* **Automate reporting** — schedule data refreshes so your dashboards always reflect the latest campaign results
* **Combine with other sources** — use Join or Append transformations to merge Campaign Monitor data with CRM, ad, or revenue data for a full-funnel view
* **AI-ready analysis** — send your campaign data directly to ChatGPT, Claude, or Gemini to spot trends and generate insights

## Prerequisites

* A Campaign Monitor account (any plan)
* Your Campaign Monitor API key — find it under **Account Settings > API Keys** in Campaign Monitor
* Access to the client(s) you want to export data from

## Quick start

{% hint style="success" %}
Start with the **Sent campaigns** entity to get a high-level view of your campaign performance, then add **Subscriber lists** or **People** as additional sources in the same data flow.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account, click **Add data flow**, and select **Campaign Monitor** as your source.
{% endstep %}

{% step %}
**Enter your API key.** Paste your Campaign Monitor API key into the authentication field. You can find this in Campaign Monitor under **Account Settings > API Keys**. If you don't have one yet, click **Generate API Key** in that same screen.
{% endstep %}

{% step %}
**Select an entity.** Choose the data you want to import — for example, **Sent campaigns**, **Subscriber lists**, or **People**. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Choose your destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm that data is flowing correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity              | What it contains                                         |
| ------------------- | -------------------------------------------------------- |
| Sent campaigns      | All campaigns that have been sent, with performance data |
| Draft campaigns     | Campaigns saved as drafts, not yet sent                  |
| Scheduled campaigns | Campaigns queued for future sending                      |
| Subscriber lists    | Your mailing lists and their metadata                    |
| People              | Individual subscriber records and custom fields          |
| Segments            | Dynamic subscriber segments and their criteria           |
| Tags                | Tags applied to subscribers                              |
| Suppression lists   | Contacts suppressed from receiving emails                |
| Templates           | Email templates in your account                          |
| Clients             | Client accounts (for agency accounts)                    |
| Admins              | Admin users on the account                               |
| Client details      | Detailed settings and configuration per client           |


---

# 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/campaign-monitor.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.