> 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 Campaign Monitor is a powerful email marketing and automation platform that enables organizations to design and send professional email campaigns, manage. Campaign Monitor is a powerful email marketing and automation platform that enables organizations to design and send professional email campaigns, manage subscriber lists, and track performance with ease. ## Connect Anedot to Campaign Monitor To integrate your Anedot fundraising account with Campaign Monitor: 1. Navigate to **Settings → Integrations → Directory** in your Anedot account. 2. Click the blue **+ New Connection** button in the upper right corner. 3. Select **Campaign Monitor** from the integration directory. 4. Choose the **Action Pages** you’d like to sync. * The default is All Pages. * To exclude specific pages, enter their Action Page IDs as a comma-separated list. 5. \_(Optional)\_Scope the integration to only include **Team**-specific data. 6. Enter your **Campaign Monitor** **List ID**. 7. Enter your **Campaign Monitor API Key**. 8. Click **Save** to complete the connection. *You can update the selected Action Pages, Team scope, or credentials at any time after setup.* ## Data Relays Anedot will relay data from both **Donation Pages** and **Lead Pages** to Campaign Monitor. * **Hidden Custom Fields** *(e.g. UTM parameters, Source Codes)* will be relayed if they are configured in Campaign Monitor. * Once relays are successful, **Subscriber** information will appear in the associated list with a detailed view of the subscriber profile. You can track new entries, updates, and related data directly from the Subscribers tab of your Campaign Monitor dashboard. * New or updated **Subscribers** appear in: * The selected **Campaign Monitor List → Subscribers** tab * The general **Subscribers** tab in Campaign Monitor * If five consecutive relays fail, the connection is marked as **Inactive** and relays will stop. ## Field Mapping Campaign Monitor Relays sends "Custom Fields" grouped with a key and value. For example: CustomFields: {"Key": "First Name", "Value": "Annie"} | Anedot Field | Campaign Monitor Field (custom field key) | | ---------------------------- | ----------------------------------------- | | \[firstName] \[lastName] | Name | | “true” | Resubscribe | | firstName | First Name | | lastName | Last Name | | phone | Phone | | address {line1} | Street | | address {line2} | Street 2 | | address {city} | City | | address {region} | State | | address {postal\_code} | Zip | | \*utmCodes {campaign} | UTM Campaign | | \*utmCodes {content} | UTM Content | | \*utmCodes {medium} | UTM Medium | | \*utmCodes {source} | UTM Source | | \*utmCodes {term} | UTM Term | | source\_code | Source Code | | “Anedot: Donation Completed” | Event | | amount (x100) | Amount | | created\_at | Date | | referrer | Referrer | | email | Email Address | | “No” | ConsentToTrack | | “true” | RestartSubscriptionBasedAutoresponders | *\*UTM fields are relayed if **added to Page URL.*** ## Payload Data ### Request Header ``` {} ``` ### Request Body ```json { "Name": "Annie Dot", "Resubscribe": true, "CustomFields": [{ "Key": "First Name", "Value": "Annie" }, { "Key": "Last Name", "Value": "Dot" }, { "Key": "Phone", "Value": "2252501301" }, { "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": "marchgala" }, { "Key": "UTM Content", "Value": null }, { "Key": "UTM Medium", "Value": "LI" }, { "Key": "UTM Source", "Value": null }, { "Key": "UTM Term", "Value": null }, { "Key": "Source Code", "Value": null }, { "Key": "Event", "Value": "Anedot: Donation Completed" }, { "Key": "Amount", "Value": 100.0 }, { "Key": "Date", "Value": "2023-03-17T11:57:08.442-04:00" }, { "Key": "Referrer", "Value": "https://secure.anedot-sandbox.com/09388ffc-9f3f-43ee-855a-1f70c7a9b764/e36d4264-b96b-4b77-9e01-3dac28e9914a?utm_campaign=marchgala&utm_medium=LI" }], "EmailAddress": "admin@anedot.com", "ConsentToTrack": "No", "RestartSubscriptionBasedAutoresponders": true} ``` ### Response Body (Success) ``` "admin@anedot.com" ``` ### Response Body (Failure) ```json { "Code": 50, "Message": "Must supply a valid HTTP Basic Authorization header"} ``` ### Response Status (Success) ``` 201 ``` ### Response Status (Failure) ``` 401 ``` --- # 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=&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.