Skip to main content

Campaign Monitor Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Campaign Monitor location.
campaign_monitor_api.png

Campaign Monitor

  1. 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.

  2. 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.

  3. Campaign Monitor destinations can be manually configured to send data to any valid Campaign Monitor API endpoint. You can also configure Nexla to automatically send the response received from the Campaign Monitor API after each call to a new Nexla webhook data source.

    First, select the API method that will be used for calls to the Campaign Monitor API from the Method pulldown menu. Common methods used when writing data to Campaign Monitor include:

    • POST: For creating new records such as adding subscribers to a list, creating campaigns, or recording events.

    • PUT: For replacing or updating existing records.

    • DELETE: For removing subscribers from lists or deleting resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Campaign Monitor API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

    Campaign Monitor's REST API accepts data in JSON format for most write operations. Select JSON as the content format to ensure compatibility with Campaign Monitor API endpoints.

API Endpoint URL​

  1. Enter the URL of the Campaign Monitor API endpoint to which you want to send the Nexset data in the URL field. For update or upsert operations, include the ID of the object to be updated at the end of the URL.

    Common Campaign Monitor write endpoint patterns include:

    • Add subscriber to a list: https://api.createsend.com/api/v3.3/subscribers/{'{listID}'}.json — adds a single subscriber to the specified list (POST).

    • Import subscribers in bulk: https://api.createsend.com/api/v3.3/subscribers/{'{listID}'}/import.json — imports multiple subscribers into a list at once (POST). Use the Record Batching option below to send records in bulk.

    • Unsubscribe a subscriber: https://api.createsend.com/api/v3.3/subscribers/{'{listID}'}/unsubscribe.json — unsubscribes a specific email address from a list (POST).

    • Update subscriber details: https://api.createsend.com/api/v3.3/subscribers/{'{listID}'}.json?email={'{email}'}&restartautoresponderssequence=false — updates an existing subscriber's details (PUT).

Your List ID can be found in the Campaign Monitor dashboard URL when viewing a subscriber list, or retrieved via the API using the GET /clients/{'{clientID}'}/lists.json endpoint. For a complete list of available write endpoints and their required request bodies, see the Campaign Monitor API Reference.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. Authorization headers and Content-Type headers are handled automatically by Nexla based on your credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Campaign Monitor destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

Record batching is particularly useful for Campaign Monitor's bulk import endpoints, which allow multiple subscriber records to be submitted in a single API call. Using the subscriber import endpoint (/subscribers/{'{listID}'}/import.json) with record batching can significantly improve performance when loading large numbers of subscribers.

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

    Campaign Monitor's subscriber import endpoint supports batching of up to 1,000 subscriber records per request. Setting the batch size to a value between 100 and 1,000 is recommended for bulk subscriber import operations.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Campaign Monitor API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, capturing import results that include the number of new subscribers added, existing subscribers updated, or any addresses that failed to import.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Campaign Monitor API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the Campaign Monitor API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Campaign Monitor API using the current settings.

Save & Activate the Destination​

  • 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.