> 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

Connect Campaign Monitor to Coupler.io to export email campaigns, subscribers, and performance metrics into Google Sheets, BigQuery, or your data warehouse.

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           |

## Campaign Monitor data overview

Campaign Monitor exposes a wide range of email marketing data through Coupler.io — from campaign-level performance metrics to individual subscriber records. Here's a breakdown of what's available for each entity.

## Entities overview

| Entity              | Best used for                                     |
| ------------------- | ------------------------------------------------- |
| Sent campaigns      | Campaign performance reporting and trend analysis |
| Draft campaigns     | Auditing content in progress                      |
| Scheduled campaigns | Planning and scheduling visibility                |
| Subscriber lists    | List health and growth tracking                   |
| People              | Subscriber-level segmentation and analysis        |
| Segments            | Understanding audience targeting rules            |
| Tags                | Subscriber categorization and filtering           |
| Suppression lists   | Deliverability and compliance monitoring          |
| Templates           | Template inventory and reuse tracking             |
| Clients             | Multi-client agency reporting                     |
| Admins              | Account access auditing                           |
| Client details      | Account configuration review                      |

## Sent campaigns metrics and dimensions

#### Campaign identifiers

| Field         | Description                               |
| ------------- | ----------------------------------------- |
| Campaign ID   | Unique identifier for the campaign        |
| Campaign name | Name given to the campaign                |
| Subject       | Email subject line                        |
| From name     | Sender display name                       |
| From email    | Sender email address                      |
| Sent date     | Date and time the campaign was sent       |
| List IDs      | Subscriber lists the campaign was sent to |

#### Performance metrics

| Metric           | Description                                    |
| ---------------- | ---------------------------------------------- |
| Total recipients | Number of subscribers the campaign was sent to |
| Opened           | Total number of opens                          |
| Unique opened    | Number of unique subscribers who opened        |
| Clicks           | Total number of link clicks                    |
| Unique clicks    | Number of unique subscribers who clicked       |
| Bounces          | Number of bounced emails                       |
| Unsubscribes     | Number of unsubscribes from this campaign      |
| Spam complaints  | Number of spam complaints received             |

## Subscriber lists metrics and dimensions

#### List metadata

| Field                     | Description                      |
| ------------------------- | -------------------------------- |
| List ID                   | Unique identifier for the list   |
| List name                 | Name of the subscriber list      |
| Unsubscribe page          | Custom unsubscribe page URL      |
| Confirmed opt-in          | Whether double opt-in is enabled |
| Confirmation success page | URL shown after confirmation     |

## People (subscriber) fields

#### Subscriber data

| Field         | Description                            |
| ------------- | -------------------------------------- |
| Email address | Subscriber's email                     |
| Name          | Subscriber's name                      |
| Date added    | When the subscriber joined the list    |
| Status        | Active, unsubscribed, bounced, etc.    |
| Custom fields | Any custom fields defined on your list |

## Common metric combinations

* **Open rate analysis** — combine Unique opened ÷ Total recipients from Sent campaigns, broken down by Sent date or subject line
* **List growth over time** — use Subscriber lists + People with a date filter to track subscriber additions
* **Suppression vs. active** — join Suppression lists with People to calculate deliverable audience size
* **Campaign volume by client** — join Clients with Sent campaigns to report on activity per client (agency accounts)

## Use cases by role

{% tabs %}
{% tab title="Marketers" %}

* Track open rates, click rates, and unsubscribes across all sent campaigns in a single Google Sheets dashboard
* Use the **Aggregate** transformation to roll up campaign metrics by month or quarter
* Export **Segments** and **Tags** data to understand how your audience is categorized and whether segments are being used effectively
* Send campaign performance data to ChatGPT or Claude to generate written summaries or identify underperforming campaigns
  {% endtab %}

{% tab title="Agency teams" %}

* Use the **Clients** and **Client details** entities to maintain an up-to-date inventory of all client accounts
* Append sent campaign data from multiple clients into one sheet for cross-client performance comparisons
* Combine **Admins** data with **Client details** to audit which team members have access to which accounts
* Export **Templates** per client to ensure brand consistency across accounts
  {% endtab %}

{% tab title="Ops & compliance" %}

* Regularly export **Suppression lists** to cross-check against your CRM or other marketing tools
* Monitor **Bounces** and **Spam complaints** from Sent campaigns to stay on top of deliverability health
* Use **People** exports to audit subscriber consent status and custom field completeness
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **start date** parameter applies to time-based entities like Sent campaigns — use the date picker to limit how far back the sync reaches
* Agency-level API keys return data across all clients; client-level API keys are scoped to a single client
* **Draft campaigns** and **Scheduled campaigns** do not include performance metrics — those only appear after a campaign is sent
* Custom fields on subscriber records vary per account — they'll appear as additional columns in **People** exports
* Suppression lists are account-wide and not tied to individual subscriber lists

## Campaign Monitor common issues

### Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you're copying the full API key from Campaign Monitor — it's easy to accidentally trim the first or last character. In Campaign Monitor, go to **Account Settings > API Keys** and copy the key directly. Also confirm whether your key is an account-level key or a client-level key, as they have different scopes and may cause unexpected errors if used for the wrong entity.

</details>

<details>

<summary>I get an authentication error even though my API key looks correct</summary>

Campaign Monitor API keys can be deactivated if account ownership or billing status changes. Log in to Campaign Monitor and verify that the key is still listed and active under **Account Settings > API Keys**. If it's missing, generate a new one and update it in your Coupler.io data flow.

</details>

### Missing data

<details>

<summary>Some campaigns are not appearing in the export</summary>

Check the **start date** parameter in your data flow settings. If you've set a start date, only campaigns sent on or after that date will be returned. Adjust the date picker to an earlier date to capture older campaigns. Also confirm you're using the correct entity — **Draft campaigns** and **Scheduled campaigns** are separate from **Sent campaigns**.

</details>

<details>

<summary>People / subscriber records are incomplete or missing custom fields</summary>

Custom fields in Campaign Monitor are list-specific. If you're pulling **People** from multiple lists, each list may have a different set of custom fields, which can cause some columns to appear blank for certain subscribers. Consider filtering your data flow to a single list if you need clean, consistent columns.

</details>

<details>

<summary>Suppression list is empty even though I have suppressed contacts</summary>

Suppression lists are account-level. If you're using a client-level API key, it may not have access to the full suppression list. Try using an account-level API key instead.

</details>

### Permission errors

<details>

<summary>I can see some clients but not others in Clients or Client details</summary>

This is expected behavior when using a client-level API key — it only returns data for the client it belongs to. To pull data across all clients, use an account-level API key generated from the top-level agency account in Campaign Monitor.

</details>

### Data discrepancies

<details>

<summary>Campaign metrics in Coupler.io don't match what I see in Campaign Monitor</summary>

Campaign Monitor may update engagement metrics (opens, clicks) for a period after a campaign is sent as delayed opens are recorded. If your data flow ran shortly after the campaign was sent, re-running it a day or two later will capture more complete data. For long-term tracking, schedule regular refreshes rather than relying on a single snapshot.

</details>

### Rate limits

<details>

<summary>My data flow fails or returns partial data for large accounts</summary>

Campaign Monitor's API enforces rate limits that may affect large exports — particularly for **People** or **Sent campaigns** with thousands of records. If you're hitting limits, try narrowing the sync window using the **start date** parameter to pull data in smaller batches. Running the data flow during off-peak hours can also help reduce the chance of timeouts.

</details>

## Campaign Monitor FAQ

<details>

<summary>What's the difference between account-level and client-level API keys?</summary>

Campaign Monitor supports two types of API keys. An account-level key (generated from the top-level account) gives access to all clients, admins, suppression lists, and account-wide data. A client-level key is scoped to a single client and won't return data from other clients. For most Coupler.io use cases — especially agency accounts — an account-level key is recommended.

</details>

<details>

<summary>Can I pull data from multiple Campaign Monitor clients into one report?</summary>

Yes. Add multiple sources in the same data flow, one per client, each with its own API key. Then use the **Append** transformation to stack the data into a single table. This works well for cross-client campaign performance reports.

</details>

<details>

<summary>Why do my open rate numbers look different from what Campaign Monitor shows in the dashboard?</summary>

Campaign Monitor continues recording delayed opens and clicks for 24–48 hours after a campaign is sent. If your data flow ran shortly after sending, the numbers will be lower than the final totals. Re-run the flow a couple of days later to get more settled figures. For ongoing tracking, a scheduled daily refresh works best.

</details>

<details>

<summary>Does Coupler.io support pulling data from Campaign Monitor transactional emails?</summary>

The current Campaign Monitor integration in Coupler.io covers the entities listed — Sent campaigns, Subscriber lists, People, Segments, Tags, and others. Transactional email data is managed separately in Campaign Monitor and is not currently exposed through this integration.

</details>

<details>

<summary>Can I send Campaign Monitor data to an AI tool like ChatGPT or Claude?</summary>

Yes. When setting up your destination in Coupler.io, you can choose AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This lets you send your campaign performance data directly to an AI tool for analysis, summarization, or generating recommendations.

</details>

<details>

<summary>How do I track subscriber list growth over time?</summary>

Set up a data flow using the **People** entity with a start date set to the beginning of the period you want to track. Schedule regular refreshes and append new results to a historical table in Google Sheets or BigQuery. The **Date added** field on each subscriber record lets you group and chart growth over time.

</details>

<details>

<summary>What happens if I don't set a start date?</summary>

If you leave the start date blank, Coupler.io will attempt to pull all available historical data for that entity. For accounts with a large volume of campaigns or subscribers, this can result in slow syncs or timeouts. It's good practice to set a start date — especially on the first run.

</details>

{% hint style="info" %}
For a full list of available fields per entity, see [Data Overview](#campaign-monitor-data-overview). If you're running into sync errors or missing records, check [Common Issues](#campaign-monitor-common-issues). For tips on API key setup and scheduling, visit [Best Practices](https://docs.coupler.io/sources/category/email/campaign-monitor/best-practices.md).
{% endhint %}


---

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