Sync ad leads to Campaign Monitor subscriber lists with custom fields and GDPR-compliant consent tracking -- no middleware or Zapier needed.
Connect Campaign Monitor with 4 lead sources
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.
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.
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.
Set up your Campaign Monitor integration in under 60 seconds. Free 14-day trial, no credit card required.
Start Your Free Trial