Campaign Monitor integration summary

Stitch’s Campaign Monitor integration replicates data using the Campaign Monitor API . Refer to the Schema section for a list of objects available for replication.

Campaign Monitor feature snapshot

A high-level look at Stitch's Campaign Monitor integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release Status

Released

 Supported By

Singer Community
Stitch Plan

Free

 Singer GitHub Repository

Campaign Monitor Repository

DATA SELECTION
Table Selection

Unsupported

 Column Selection

Unsupported
REPLICATION SETTINGS
Anchor Scheduling

Supported

 Advanced Scheduling

Unsupported
Table-level Reset

Unsupported

 Configurable Replication Methods

Unsupported
TRANSPARENCY
Extraction Logs

Supported

 Loading Reports

Supported

Connecting Campaign Monitor

Step 1: Retrieve your Campaign Monitor API credentials

  1. Sign into your Campaign Monitor account.
  2. Click the user menu (your avatar), located in the top right corner.
  3. Click Account settings.
  4. On the Account Settings page, click API keys.
  5. Locate your Client ID.

Keep this page open - you’ll need it to complete the next step.

Step 2: Add Campaign Monitor as a Stitch data source

  1. Sign into your Stitch account.

  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Campaign Monitor icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Campaign Monitor” would create a schema called stitch_campaign_monitor in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Campaign Monitor Client ID field, paste your Campaign Monitor client ID.

Step 3: Define the historical sync

The Sync Historical Data setting will define the starting date for your Campaign Monitor integration. This means that:

  • For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Campaign Monitor’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Campaign Monitor integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Authorize Stitch to access Campaign Monitor

  1. Next, you’ll be prompted to sign into your Campaign Monitor account.
  2. Follow the prompts to complete the authorization process.
  3. After the authorization process is successfully completed, you’ll be directed back to Stitch.
  4. Click All Done.

Initial and historical replication jobs

After you finish setting up Campaign Monitor, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Campaign Monitor table schemas

campaign_bounces

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

CampaignID : EmailAddress : Date : ListID

 API endpoint :

Get campaign bounces

The campaign_bounces table contains info about the subscribers who bounced for a given campaign.

campaign_clicks

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

CampaignID : EmailAddress : ListID : Date

 API endpoint :

Get campaign clicks

The campaign_clicks table contains info about subscribers who clicked a link in a given campaign.

campaign_clicks table schema

CampaignID
STRING

The campaign ID.

Reference:

EmailAddress
STRING

The email address.

ListID
STRING

The list ID.

Reference:

Date
STRING

The date the click occurred.

URL
STRING

The URL that was clicked.

IPAddress
STRING

The IP address.

Latitude
NUMBER

The latitude.

Longitude
NUMBER

The longitude.

City
STRING

The city.

Region
STRING

The region.

CountryCode
STRING

The country code.

CountryName
STRING

The country name.

campaign_email_client_usage

View table schema on GitHub
Replication Method :

Full Table

 Primary Key :

CampaignID : Client : Version
API endpoint :

Get email client usage

The campaign_email_client_usage table contains info about the email clients subscribers use to open campaigns.

campaign_email_client_usage table schema

CampaignID
STRING

The campaign ID.

Reference:

Client
STRING

The name of the email client.

Version
STRING

The version of the email client.

Percentage
NUMBER

The percentage of users who use the email client and version.

Subscribers
INTEGER

The number of subscribers who used the email client and version to open the campaign.

campaign_opens

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

CampaignID : EmailAddress : ListID : Date

 API endpoint :

Get campaign opens

The campaign_opens table contains info about subscribers who opened a campaign.

campaign_recipients

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :
Primary Key :

CampaignID : EmailAddress : ListID

 API endpoint :

Get campaign recipients

The campaign_recipients table contains info about the subscribers that a campaign was sent to.

campaign_spam_complaints

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

CampaignID : EmailAddress : ListID : Date

 API endpoint :

Get campaign spam complaints

The campaign_spam_complaints table contains info about subscribers who marked a campaign as spam.

campaign_summary

View table schema on GitHub
Replication Method :

Full Table

 Primary Key :

CampaignID
API endpoint :

Get campaign summary

The campaign_summary table contains summary info about sent campaigns.

campaign_summary table schema

CampaignID
STRING

The campaign ID.

Reference:

Recipients
INTEGER

The number of campaign recipients.

TotalOpened
INTEGER

The total number of opens for the campaign.

Clicks
INTEGER

The total number of clicks for the campaign.

Unsubscribed
INTEGER

The total number of unsubscribes for the campaign.

Bounced
INTEGER

The total number of bounces for the campaign.

UniqueOpened
INTEGER

The unique number of opens for the campaign.

SpamComplaints
INTEGER

The number of spam complaints for the campaign.

WebVersionURL
STRING

The campaign’s web version URL.

WebVersionTextURL
STRING

The campaign’s web version text URL.

WorldviewURL
STRING

The campaign’s public Worldview URL.

Forwards
INTEGER

The number of forwards for the campaign.

Likes
INTEGER

The number of likes for the campaign.

Mentions
INTEGER

The number of mentions for the campaign.

campaign_unsubscribes

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

CampaignID : EmailAddress : ListID : Date

 API endpoint :

Get campaign unsubscribes

The campaign_unsubscribes table contains info about the subscribers who unsubscribed from the email for a campaign.

campaigns

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :
Primary Key :

CampaignID

 Official docs :

Official Docs

The campaigns table contains info about the the campaigns in your Campaign Monitor account.

campaigns table schema

CampaignID
STRING

The campaign ID.

Reference:

FromName
STRING

The campaign’s from name.

FromEmail
STRING

The email address campaign emails are sent from.

ReplyTo
STRING

The email address that replies to the campaign will be sent to.

WebVersionURL
STRING

The campaign’s web version URL.

WebVersionTextURL
STRING

The campaign’s web version text URL.

Subject
STRING

The subject of the campaign.

Name
STRING

The name of the campaign.

SentDate
STRING

The date the campaign was sent.

TotalRecipients
NUMBER

The total number of subscribers who received the campaign.

list_active_subscribers

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

ListID : EmailAddress : Date

 API endpoint :

Get list active subscribers

The list_active_subscribers table contains info about the active subscribers for lists.

list_active_subscribers table schema

ListID
STRING

The list ID.

Reference:

EmailAddress
STRING

The email address.

Date
STRING

The date.

Name
STRING

The name of the subscriber.

State
STRING

The subscriber’s state.

CustomFields
OBJECT

Custom fields about the subscriber.

Click to expand CustomFields

Key
STRING

The key name of the custom field.

Value
STRING

The value of the custom field.
list_active_subscribers (table), CustomFields (attribute)

ReadsEmailWith
STRING

The email client the subscriber uses to read email.

ConsentToTrack
STRING

Indicates if the subscriber has consented to tracking.

list_bounced_subscribers

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

ListID : EmailAddress : Date

 API endpoint :

Get list bounced subscribers

The list_bounced_subscribers table contains info about the bounced subscribers for lists.

list_bounced_subscribers table schema

ListID
STRING

The list ID.

Reference:

EmailAddress
STRING

The email address.

Date
STRING

The date.

Name
STRING

The name of the subscriber.

State
STRING

The subscriber’s state.

CustomFields
OBJECT

Custom fields about the subscriber.

Click to expand CustomFields

Key
STRING

The key name of the custom field.

Value
STRING

The value of the custom field.
list_bounced_subscribers (table), CustomFields (attribute)

ReadsEmailWith
STRING

The email client the subscriber uses to read email.

ConsentToTrack
STRING

Indicates if the subscriber has consented to tracking.

list_deleted_subscribers

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

ListID : EmailAddress : Date

 API endpoint :

Get list deleted subscribers

The list_deleted_subscribers table contains info about the deleted subscribers for lists.

list_deleted_subscribers table schema

ListID
STRING

The list ID.

Reference:

EmailAddress
STRING

The email address.

Date
STRING

The date.

Name
STRING

The name of the subscriber.

State
STRING

The subscriber’s state.

CustomFields
OBJECT

Custom fields about the subscriber.

Click to expand CustomFields

Key
STRING

The key name of the custom field.

Value
STRING

The value of the custom field.
list_deleted_subscribers (table), CustomFields (attribute)

ReadsEmailWith
STRING

The email client the subscriber uses to read email.

ConsentToTrack
STRING

Indicates if the subscriber has consented to tracking.

list_details

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :
Primary Key :

ListID

 API endpoint :

Get list details

The list_details table contains summary info about lists in your Campaign Monitor account.

list_details table schema

ListID
STRING

The list ID.

Reference:

ConfirmedOptIn
BOOLEAN

If true, the list is a confirmed opt-in list.

Title
STRING

The title of the list.

UnsubscribePage
STRING

The URL of the list’s unsubscribe page.

UnsubscribeSetting
STRING

The list’s unsubscribe setting.

ConfirmationSuccessPage
STRING

The URL of the list’s confirmation page.

list_unconfirmed_subscribers

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

ListID : EmailAddress : Date

 API endpoint :

List unconfirmed subscribers

The list_unconfirmed_subscribers table contains info about the unconfirmed subscribers for lists.

list_unconfirmed_subscribers table schema

ListID
STRING

The list ID.

Reference:

EmailAddress
STRING

The email address.

Date
STRING

The date.

Name
STRING

The name of the subscriber.

State
STRING

The subscriber’s state.

CustomFields
OBJECT

Custom fields about the subscriber.

Click to expand CustomFields

Key
STRING

The key name of the custom field.

Value
STRING

The value of the custom field.
list_unconfirmed_subscribers (table), CustomFields (attribute)

ReadsEmailWith
STRING

The email client the subscriber uses to read email.

ConsentToTrack
STRING

Indicates if the subscriber has consented to tracking.

list_unsubscribed_subscribers

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

Date
Primary Key :

ListID : EmailAddress : Date

 API endpoint :

List unsubscribed subscribers

The list_unsubscribed_subscribers table contains info about the unsubscribed subscribers for lists.

list_unsubscribed_subscribers table schema

ListID
STRING

The list ID.

Reference:

EmailAddress
STRING

The email address.

Date
STRING

The date.

Name
STRING

The name of the subscriber.

State
STRING

The subscriber’s state.

CustomFields
OBJECT

Custom fields about the subscriber.

Click to expand CustomFields

Key
STRING

The key name of the custom field.

Value
STRING

The value of the custom field.
list_unsubscribed_subscribers (table), CustomFields (attribute)

ReadsEmailWith
STRING

The email client the subscriber uses to read email.

ConsentToTrack
STRING

Indicates if the subscriber has consented to tracking.

lists

View table schema on GitHub
Replication Method :

Full Table

 Primary Key :

ListID
Official docs :

Official Docs

The lists table contains info about the lists in your Campaign Monitor account.

Related Troubleshooting
Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.