Campaign Monitor is an email marketing platform that enables businesses and agencies to create, send, and automate email campaigns, manage subscriber lists, and analyze campaign performance. Founded in 2004, Campaign Monitor provides a drag-and-drop email builder, advanced segmentation tools, automated customer journey workflows, and detailed analytics — making it a trusted solution for marketers who want to deliver highly personalized email experiences at scale.
Power end-to-end data operations for your Campaign Monitor API with Nexla. Our bi-directional Campaign Monitor connector is purpose-built for Campaign Monitor, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Campaign Monitor or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Campaign Monitor workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Campaign Monitor API v3.3 (https://api.createsend.com/api/v3.3) with your Campaign Monitor API key, using HTTP Basic Authentication: the API key is sent as the username, and the password is not used for authentication. Campaign Monitor also supports OAuth for its API, but this connector uses the API key.
Click your profile image in the upper-right corner, and select Account settings.
Click API keys. Copy your account API key. The same page shows the Client IDs of your clients, which many templates below require.
Use the account API key, not a client ID. The account key reaches every client in the account; Nexla tests the credential by listing the account's clients. For more information, see Campaign Monitor's Authenticating with an API key and API keys articles.
The API key grants full access to your account's data. Treat it like a password: don't share it or commit it to source control.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Campaign Monitor account API key in the API Key field. The field is masked. Do not enter your login email address or a Client ID.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by listing your clients (GET /api/v3.3/clients.json).
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Campaign Monitor connector tile, then select the credential that will be used to connect to the Campaign Monitor account, and click Next; or, create a new Campaign Monitor credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Campaign Monitor endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Most templates are scoped to a client, list, segment, campaign, or journey email. Start with List Clients to get Client IDs, then use List Subscriber Lists, List Client Segments, and the campaign list templates to find the other IDs. Templates whose description says "all pages" request 1,000 records per page and keep reading until a page comes back short; the others return the full result in one call.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Campaign Monitor sources can also be manually configured to ingest data from any valid Campaign Monitor API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or optional query parameters such as date filters and sort order. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Most Campaign Monitor list endpoints return a top-level JSON array, so use $[*] as the path to data. Paged endpoints, such as active subscribers (/lists/LIST_ID/active.json), wrap records in a Results array, so use $.Results[*]. For a complete list of endpoints, see the Campaign Monitor API reference.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Campaign Monitor data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Campaign Monitor destination, and select the Send to Destination option from the menu. Select the Campaign Monitor connector from the list of available destination connectors, then select the credential that will be used to connect to the Campaign Monitor account, and click Next; or, create a new Campaign Monitor credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Campaign Monitor endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time, using Campaign Monitor's field names (for example, {"EmailAddress": "someone@example.com", "Name": "Jane Doe", "ConsentToTrack": "Yes"} for Add Subscriber). ID and email settings, such as List ID or Email Address, are fixed on the destination and apply to every record it sends. Templates marked Side effect send email, change who can log in, or remove data in ways that can't be undone from Nexla.
The destination templates create and manage campaigns, lists, subscribers, segments, templates, and account settings, but none of them sends email campaigns or transactional email: Create Draft Campaign creates a draft only. Send campaigns from Campaign Monitor, or configure the send endpoint manually.
Side effect: Adds a client to the account (billing is set per client afterwards; agency accounts may be charged). Record: {"CompanyName", "Country", "TimeZone"}.
Update a list's title, pages, opt-in and unsubscribe settings with each record. ScrubActiveWithSuppList true unsubscribes suppressed active subscribers.
Enter the List ID. Subscriber ListID; get it from List Subscriber Lists.
Side effect: New subscribers get the list's confirmation or opt-in email; Resubscribe true re-adds unsubscribed or suppressed ones. Record: {"EmailAddress", "Name", "CustomFields", "ConsentToTrack"}.
Enter the List ID. Subscriber ListID; get it from List Subscriber Lists.
Side effect: Adds or updates many subscribers at once; new ones get the list's confirmation email and fire Subscribe webhooks. Record: {"Subscribers": [...], "Resubscribe"}.
Enter the List ID. Subscriber ListID; get it from List Subscriber Lists.
Campaign Monitor destinations can also be manually configured to send data to any valid Campaign Monitor API endpoint. Select the API method and follow the instructions in Connect to Any API to configure the data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks. Campaign Monitor's write endpoints accept JSON request bodies; see the Campaign Monitor API reference for each endpoint's fields.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Campaign Monitor endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Campaign Monitor API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.