Campaign Monitor
Integrations › Campaign Monitor

Campaign Monitor Integration

Sync ad leads to Campaign Monitor subscriber lists with custom fields and GDPR-compliant consent tracking -- no middleware or Zapier needed.

Available Integrations

Connect Campaign Monitor with 4 lead sources

Start Free Trial No credit card required · 14-day free trial
Trusted by
1,000+ businesses
Leads synced
2M+
Integrations
37+
Free trial
14 days, no card

How It Works

1
Connect Your Ad Account
Link your Facebook, Google, LinkedIn, or TikTok ad account to LeadSync in one click.
2
Choose Campaign Monitor
Select Campaign Monitor as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to Campaign Monitor and start syncing leads instantly.

How LeadSync Adds Subscribers to Campaign Monitor

Campaign Monitor organises subscribers into Lists -- the container that Journeys (Campaign Monitor's automation engine), Segments, and one-off email Campaigns all key off. LeadSync connects via your Campaign Monitor Client ID and API Key (the standard auth pair on the official campaignmonitor REST library) and adds each Facebook, Google, LinkedIn, or TikTok lead to the chosen List as a subscriber with name, email, and any mapped custom fields populated.

Setup is two values from your Campaign Monitor account (Account Settings › API Keys for the API key, plus your Client ID from the Clients section if you use the agency model). LeadSync stores them as a colon- or semicolon-delimited pair, then enumerates every List on the chosen Client via get_lists() so you can pick the destination per lead source.

GDPR Consent-to-Track Set Automatically

Campaign Monitor's ConsentToTrack field is required on every subscriber-add call to comply with GDPR -- it controls whether Campaign Monitor records open and click tracking on emails sent to that subscriber. LeadSync sets ConsentToTrack: Yes on every subscriber, on the basis that the lead's submission of your Facebook lead form (which carries Meta's consent disclosure) constitutes the explicit consent the GDPR audit trail expects.

LeadSync also sets Resubscribe: true, which means a previously-unsubscribed email submitting your lead form again will be re-added to the List rather than silently rejected -- the standard pattern for paid-social campaigns where users sometimes re-engage after a quiet period.

Custom Fields, EmailAddress Override, and Name Override

The field mapping screen lists every Campaign Monitor custom field on the List (pulled from the get_custom_fields() API call), plus two special pseudo-fields: __EmailAddress and __Name. These let you override the default email and name extraction if your lead form uses non-standard question keys -- map your "Work Email" question to __EmailAddress and Campaign Monitor receives that value as the primary subscriber identifier.

Standard custom fields support text, number, date, and multi-select types. The value is sent as a structured Key/Value pair so Campaign Monitor stores it correctly typed and merge tags like [firstname] or [customfield,fallback="there"] render correctly in your Journey emails.

Frequently Asked Questions

In Campaign Monitor, generate an API Key (Account Settings > API Keys) and copy your Client ID from the Clients section if you use the agency model. Paste both into LeadSync as the colon-delimited Client ID and API Key pair. LeadSync will pull every List on the chosen Client so you can pick the destination per lead source.
Yes. LeadSync sets ConsentToTrack to Yes on every subscriber, which is the GDPR-required field that controls open and click tracking. The implicit consent comes from the lead form submission carrying Meta's standard consent disclosure -- the same legal basis Campaign Monitor expects for any paid-social opt-in.
LeadSync sets Resubscribe to true on the add call, so the previously-unsubscribed contact is re-added to the List rather than silently rejected. This is the right pattern for paid-social campaigns where users sometimes re-engage after a quiet period.
Yes. Build a Journey with a "List Subscribe" trigger pointing at the List LeadSync writes to, and every new lead enters the Journey within seconds. The Journey can include email steps, Yes/No path branching on custom field values, and exit triggers when the contact converts.
LeadSync calls get_custom_fields() on the destination List, so every custom field you have defined on that List appears in the mapping dropdown automatically. Map a lead form question to a custom field once and it populates on every new lead.
Yes. The mapping screen exposes two pseudo-fields: __EmailAddress and __Name. Map your form's "Work Email" question to __EmailAddress (or your "Full Name" question to __Name) and LeadSync sends those values as the primary subscriber identifier and name fields on the add call.
Yes. Create one LeadSync connection per source and pick a different List on each. Facebook leads can land in your paid-social welcome List while LinkedIn leads land in a B2B-focused List with different Journeys, Segments, and merge-tag personalisation.
Yes. LeadSync supports Campaign Monitor as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own connection.
Campaign Monitor de-duplicates subscribers by email within a List, so a repeat submission updates the existing subscriber and refreshes their custom fields with the latest values. They stay on the List rather than getting added a second time, and your subscriber count stays accurate.

Start Syncing Leads to Campaign Monitor

Set up your Campaign Monitor integration in under 60 seconds. Free 14-day trial, no credit card required.

Start Your Free Trial
No credit card required • Set up in 60 seconds • Cancel anytime