> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md).

# Campaign Monitor

Connect Anedot to Campaign Monitor to add Action Page donors and supporters to a subscriber list, set up custom fields, and review field mapping and payloads.

**Campaign Monitor** is an email marketing platform. The integration adds the donor or supporter from each Action Page submission to one Campaign Monitor subscriber list, or updates them if they're already on it. You set it up in **Settings > Integrations**, where you can connect Anedot to Campaign Monitor, manage your connection, and review how data relays work, where to find your data, field mapping and payload data.

## Before You Begin

* You need **Integrations: Edit permissions** to add, edit, push or delete a connection. Integrations: Edit permissions also require **Action Pages: View permissions** and **Integrations: View permissions**. See [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md).
* You need a Campaign Monitor account with the subscriber list you want to use.
* You need the full access permission in Campaign Monitor, and a verified email address on your Campaign Monitor login, to view the API key. See [Step 1: Get Your Campaign Monitor API Key](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#step-1-get-your-campaign-monitor-api-key).
* You need two values from Campaign Monitor: an API key and the ID of the list subscribers should be added to. Both fields are required in Anedot.
* Plan which custom fields you want filled in Campaign Monitor. See [Step 3: Add Custom Fields to Your List](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#step-3-add-custom-fields-to-your-list).

## Connect Anedot to Campaign Monitor

### Step 1: Get Your Campaign Monitor API Key

You find or create the API key in your Campaign Monitor account, not in Anedot.

To get your API key:

1. In Campaign Monitor, click your profile image at the top right.
2. Select **Account settings**.
3. Click **API keys**.
4. Click **Show API key**. If you haven't generated a key yet, click **Generate API key** instead.
5. Copy the API key.

Your API key is ready to enter in Anedot.

{% hint style="info" %}
The API keys page also shows your client ID. Anedot doesn't need the client ID. Treat the API key like a password.
{% endhint %}

{% hint style="warning" %}
If you generate a new API key in Campaign Monitor, the old key keeps working for 24 hours. Delete the Anedot connection and connect again with the new key within those 24 hours.
{% endhint %}

### Step 2: Find Your List ID

To find your List ID:

1. In Campaign Monitor, click **Lists & subscribers**.
2. Click the list you want to use.
3. Click **Settings** in the left menu.
4. Scroll to the bottom of the page and copy the **List API ID**.

You'll enter this ID in the **List ID** field in Anedot.

### Step 3: Add Custom Fields to Your List

Every Campaign Monitor list has two default fields, name and email address. Anedot fills these with no setup.

Every other value Anedot sends is a custom field value with its own key. See [Field Mapping](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#field-mapping). Create a custom field on your list for each value you want filled.

To create a custom field:

1. In Campaign Monitor, click **Lists & subscribers**.
2. Click the list.
3. Click **Custom fields** in the left menu.
4. Enter a name for the field. Use the Campaign Monitor Field Name shown in Field Mapping, exactly as shown.
5. In the **Data Type** drop-down, choose **Text**.
6. Click **Create field**.
7. Repeat these steps for each field you want filled.

The field is ready to receive values from Anedot.

{% hint style="info" %}
Campaign Monitor makes each custom field's key from its name with the spaces removed, and Anedot sends the keys shown in Field Mapping, which include spaces. After you set up your fields, send a test submission and check that the subscriber's custom fields are filled.
{% endhint %}

{% hint style="info" %}
Use **Text** for every Anedot field, because Campaign Monitor Date fields expect a date such as 2026/11/10 and Anedot sends a date and time. You can't change a custom field's data type after you create it.
{% endhint %}

{% hint style="info" %}
A list can have up to 50 custom fields, and each value can be up to 250 characters. Renaming a custom field changes its key, so keep the names shown in Field Mapping.
{% endhint %}

### Step 4: Create the Connection in Anedot

To create the connection:

1. Go to **Settings > Integrations**.
2. Click **New integration**.
3. Choose **Campaign Monitor**, or enter "Campaign Monitor" in the search box.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Campaign Monitor</strong> appears under the <strong>Email Marketing</strong> category with the text "Send Action Page submissions to a Campaign Monitor list."</p></div>
4. Choose the Action Page scope:
   * Keep **All Action Pages** checked to include every Action Page, including pages you add later. (Optional) In **Exclude Pages**, enter a comma-separated list of Action Page IDs with no spaces.
   * Uncheck **All Action Pages** and choose **Selected pages** to pick specific pages.
5. (Optional) In **Team**, choose a Team to limit the connection to that Team's Action Pages. Leave it set to **All teams** to include every Team. See [Teams](https://docs.anedot.com/settings/access/teams.md).
6. Enter your Campaign Monitor API key in **Campaign Monitor API key**.
7. Enter the list's ID in **List ID**.
8. Click **Create integration**.

The connection is listed in **Settings > Integrations**.

{% hint style="success" %}
After you connect, submit a test on a covered Action Page with an email address and check **Settings > Integrations > Integration Requests** for a **Success** row. Then find the subscriber in Campaign Monitor and check that the custom fields are filled.
{% endhint %}

## Manage Your Connection

### Edit Your Connection

You can change the Action Page scope, **Team**, **Name** and **Enabled** on an existing connection.

To edit your connection:

1. Go to **Settings > Integrations**.
2. Click **Edit** on the Campaign Monitor connection.
3. Update the Action Page scope, **Team**, **Name** or **Enabled**.
4. Click **Save integration**.

New settings apply to records sent from then on. Editing doesn't resend records already sent, and unchecking **Enabled** stops sending.

{% hint style="info" %}
The Edit form also shows a **Credentials/details JSON** box. Leave it as it is.
{% endhint %}

The API key and List ID aren't shown or changed in the Edit form. To use a different API key or List ID, delete the connection and connect again with the new values. See [Reconnect Or Delete Your Connection](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#reconnect-or-delete-your-connection).

### Push Unsent Records

**Push unsent** resends failed or never-sent submissions for a date range.

* The range can be up to 31 days.
* The start date must be within the last 12 months.
* Wait about five minutes between pushes.
* Only failed or unsent submissions are sent. Successful ones aren't sent again.

For full steps, see [Push Unsent in Webhooks (API)](https://docs.anedot.com/integrations/integration-automation-tools/webhooks.md#push-unsent).

### Reconnect Or Delete Your Connection

To delete your connection:

1. Go to **Settings > Integrations**.
2. Click **Delete** on the Campaign Monitor connection.
3. Confirm the prompt "Delete this integration?".

Anedot stops sending to Campaign Monitor. Subscribers already in Campaign Monitor aren't changed.

To reconnect, follow the steps in [Connect Anedot to Campaign Monitor](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#connect-anedot-to-campaign-monitor) again.

{% hint style="info" %}
Submissions already sent successfully with the same API key aren't sent again after you reconnect.
{% endhint %}

## Data Relays

### What Anedot Sends

Anedot sends one record per Action Page submission in the connection's scope.

* Donation Pages, Event Pages and Lead Pages are all sent.
* Lead Page submissions are sent when they're submitted. Donation Page submissions are sent once the donation is completed.
* For each submission, Anedot adds the person to the list in **List ID** as a Campaign Monitor subscriber, with the email address, the person's name, and the custom field values in [Field Mapping](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#field-mapping). Blank values are sent empty.
* Custom field and hidden field answers from the Action Page aren't sent to Campaign Monitor. Tracking values reach Campaign Monitor through the source code and UTM codes.
* Each connection adds subscribers to one list.
* Recurring donation payments, commitment changes (such as a cancellation), refunds, and donation status changes aren't sent. See [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md).

If the email address is already on the list, Campaign Monitor updates that subscriber's name and custom field values with the values Anedot sends. Campaign Monitor places the data in a processing queue, so a new or updated subscriber can take a moment to show.

Only new subscribers get the follow-up email set in the list settings. If your list uses double opt-in, Campaign Monitor sends a new subscriber the verification email. Otherwise, it sends the list's confirmation email.

Every request also sends three fixed subscriber settings:

* **`ConsentToTrack`**: Sent as "No". Campaign Monitor doesn't track opens and clicks in emails to that email address. The setting applies to every subscriber with that email address in the same Campaign Monitor client.
* **`Resubscribe`**: Sent as true. If the person is inactive on the list, or was unsubscribed or added to the suppression list, Campaign Monitor adds them back to the list.
* **`RestartSubscriptionBasedAutoresponders`**: Sent as true. When a person is added back to the list, Campaign Monitor restarts their automated workflow sequences.

### Records Anedot Skips

Anedot doesn't send these records, and they don't show a row in **Settings > Integrations > Integration Requests**:

* A submission with no email address.
* A submission that was already sent successfully to a Campaign Monitor connection with the same API key, including a connection you deleted and connected again.
* A Donation Page submission whose donation isn't completed yet. It's sent when it completes.
* Any submission while **Enabled** is unchecked.
* Recurring donation payments.

### Delivery And Retries

Each submission sent shows a row in **Settings > Integrations > Integration Requests** with its status (**Success**, **Failure** or **Error**), the request and the response. The stored request doesn't include your API key. See [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md).

* **Success**: Campaign Monitor accepted the subscriber.
* **Failure**: Campaign Monitor rejected the record, and Anedot doesn't try that submission again. Fix the cause, then use [Push Unsent Records](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#push-unsent-records).
* **Error**: Anedot couldn't reach Campaign Monitor and tries again automatically.

Users with the **Integration sync failed** notification turned on get an email when a row shows **Failure**. See [Notifications](https://docs.anedot.com/get-started/security/notifications.md).

{% hint style="warning" %}
Repeated authorization errors, where Campaign Monitor rejects the API key, turn the connection off. A successful send resets this. If the connection stops sending, delete it and connect again with a working API key.
{% endhint %}

## Find Your Data in Campaign Monitor

To find a subscriber from Anedot:

1. In Campaign Monitor, click **Lists & subscribers**.
2. Click the list you connected.
3. Use the search field to find the person's email address.

The subscriber shows in the list.

## Field Mapping

| Anedot Value                                                          | Campaign Monitor Field Name              | Sent As             |
| --------------------------------------------------------------------- | ---------------------------------------- | ------------------- |
| Email                                                                 | `EmailAddress`                           | Default field       |
| Full name (title, first, middle and last name, and suffix when given) | `Name`                                   | Default field       |
| First name                                                            | `First Name`                             | Custom field (Text) |
| Last name                                                             | `Last Name`                              | Custom field (Text) |
| Phone                                                                 | `Phone`                                  | Custom field (Text) |
| Street address                                                        | `Street`                                 | Custom field (Text) |
| Address line 2                                                        | `Street 2`                               | Custom field (Text) |
| City                                                                  | `City`                                   | Custom field (Text) |
| State                                                                 | `State`                                  | Custom field (Text) |
| ZIP code                                                              | `Zip`                                    | Custom field (Text) |
| UTM campaign                                                          | `UTM Campaign`                           | Custom field (Text) |
| UTM content                                                           | `UTM Content`                            | Custom field (Text) |
| UTM medium                                                            | `UTM Medium`                             | Custom field (Text) |
| UTM source                                                            | `UTM Source`                             | Custom field (Text) |
| UTM term                                                              | `UTM Term`                               | Custom field (Text) |
| Source code                                                           | `Source Code`                            | Custom field (Text) |
| The exact value "Anedot: Donation Completed"                          | `Event`                                  | Custom field (Text) |
| Total amount in dollars, such as 100.0 (0.0 when there's no payment)  | `Amount`                                 | Custom field (Text) |
| Submission date and time in your account's time zone                  | `Date`                                   | Custom field (Text) |
| Referring page                                                        | `Referrer`                               | Custom field (Text) |
| The exact value "No"                                                  | `ConsentToTrack`                         | Subscriber setting  |
| The exact value true                                                  | `Resubscribe`                            | Subscriber setting  |
| The exact value true                                                  | `RestartSubscriptionBasedAutoresponders` | Subscriber setting  |

* **`Phone`**: Sent as a custom field, not as a Campaign Monitor mobile number.
* **`Source Code`**: The source code in the page link (`source_code`, `sc` or `refcd`), or the page's **Default Source Code** when the link has none. Set a default in [Page Settings: SEO, Sharing, and Tracking](https://docs.anedot.com/action-pages/page-builder/page-settings-seo-sharing-and-tracking.md). See [URL Parameters](https://docs.anedot.com/action-pages/advanced-features/url-parameter.md).
* **`UTM Campaign`, `UTM Content`, `UTM Medium`, `UTM Source`, `UTM Term`**: Filled only when the page link includes `utm_campaign`, `utm_content`, `utm_medium`, `utm_source` or `utm_term`. Otherwise they're sent empty. See [URL Parameters](https://docs.anedot.com/action-pages/advanced-features/url-parameter.md).
* **`Referrer`**: The page the supporter came from, or the `referrer_to_form` value in the page link. Campaign Monitor stores up to 250 characters in a custom field value. See [URL Parameters](https://docs.anedot.com/action-pages/advanced-features/url-parameter.md).
* **`ConsentToTrack`, `Resubscribe`, `RestartSubscriptionBasedAutoresponders`**: Sent with every subscriber. You don't create fields for them. Their meaning is in [What Anedot Sends](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#what-anedot-sends).
* **Hidden fields**: Hidden field values aren't sent to Campaign Monitor. To track a source in Campaign Monitor, use a source code or UTM codes in the page link instead. See [Hidden Fields](https://docs.anedot.com/action-pages/page-builder/hidden-fields.md).

## Payload Data

These are the request and response bodies shown in **Settings > Integrations > Integration Requests**.

### Request Body

```json
{
  "ConsentToTrack": "No",
  "EmailAddress": "annie@anedot.com",
  "Name": "Annie Dot",
  "Resubscribe": true,
  "RestartSubscriptionBasedAutoresponders": true,
  "CustomFields": [
    { "Key": "First Name", "Value": "Annie" },
    { "Key": "Last Name", "Value": "Dot" },
    { "Key": "Phone", "Value": "2015550123" },
    { "Key": "Street", "Value": "1340 Poydras Street" },
    { "Key": "Street 2", "Value": null },
    { "Key": "City", "Value": "New Orleans" },
    { "Key": "State", "Value": "LA" },
    { "Key": "Zip", "Value": "70113" },
    { "Key": "UTM Campaign", "Value": null },
    { "Key": "UTM Content", "Value": "gala" },
    { "Key": "UTM Medium", "Value": "web" },
    { "Key": "UTM Source", "Value": null },
    { "Key": "UTM Term", "Value": null },
    { "Key": "Source Code", "Value": "2026" },
    { "Key": "Event", "Value": "Anedot: Donation Completed" },
    { "Key": "Amount", "Value": 100.0 },
    { "Key": "Date", "Value": "2026-11-10T09:15:27.466-06:00" },
    { "Key": "Referrer", "Value": "https://www.example.com/" }
  ]
}
```

### Success Response (Status 201)

Campaign Monitor answers with status 201 and the subscriber's email address when it accepts the subscriber.

```json
"annie@anedot.com"
```

### Failure Response (Status 401)

A 401 response with code 100 means Campaign Monitor didn't accept the API key.

```json
{
  "Code": 100,
  "Message": "Invalid API Key"
}
```

## Troubleshooting

### No Row in Integration Requests

Check each of these:

* The Action Page is in the connection's scope, and in its Team if one is set.
* **Enabled** is checked.
* The submission has an email address.
* The donation is completed.
* The submission wasn't already sent to a Campaign Monitor connection with the same API key.

See [Records Anedot Skips](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#records-anedot-skips).

### Rows Show Failure

Open the row in **Settings > Integrations > Integration Requests** and read Campaign Monitor's response (`Code` and `Message`). Code 100 means the API key is wrong or was replaced in Campaign Monitor. Also check the List ID against the **List API ID** in Campaign Monitor.

Fix the cause, then use [Push Unsent Records](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#push-unsent-records). If the API key or List ID was wrong, delete the connection and connect again with the right values first.

### Some Fields Are Empty in Campaign Monitor

Check that your list has a custom field for each value, named as shown in [Field Mapping](https://docs.anedot.com/integrations/email-marketing-communication/campaign-monitor.md#field-mapping), with the **Text** data type. UTM fields are empty when the page link had no UTM codes. Campaign Monitor can also take a moment to process a new subscriber.

### Subscriber Hasn't Confirmed

Your list uses double opt-in, and Campaign Monitor sent the person a verification email. They need to confirm it.

### Opens And Clicks Aren't Tracked

Anedot sends `ConsentToTrack` as "No", so Campaign Monitor doesn't track opens and clicks for that email address.

### Connection Stopped Sending

Check that **Enabled** is checked on the connection. If the Campaign Monitor API key was changed, delete the connection and connect again with the new key.

If the issue continues, contact our Support team at <help@anedot.com>.

## Related Articles

* [Integrations](https://docs.anedot.com/integrations.md)
* [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md)
* [URL Parameters](https://docs.anedot.com/action-pages/advanced-features/url-parameter.md)
* [Teams](https://docs.anedot.com/settings/access/teams.md)
* [Notifications](https://docs.anedot.com/get-started/security/notifications.md)
* [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md)


---

# 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.anedot.com/integrations/email-marketing-communication/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.
