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

# 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](/sources/category/email/campaign-monitor/data-overview.md). If you're running into sync errors or missing records, check [Common Issues](/sources/category/email/campaign-monitor/common-issues.md). For tips on API key setup and scheduling, visit [Best Practices](/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 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/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.