Help
Sync captured emails to Mailchimp or Kit
Connect an email tool once, and every email your email gate captures lands there automatically, tagged with the campaign that earned it, no manual export.
Last updated
What email sync does
Every captured email becomes a contact in your connected Mailchimp audience or Kit form, tagged with the campaign that captured it. Each contact carries source, platform, username, and campaign as fields, so you can segment by exactly which post or campaign brought them in.
The moment someone submits an email on your download page, that address is pushed to your connected ESP as a new (or updated) contact: no separate import step, no CSV in between. The contact record carries a small set of fields alongside the email: source (a literal "Magnet", the product's internal tag value, shown as-is in Mailchimp/Kit), the platform the lead came from, their username, and the campaign name, plus a "Magnet" tag and the campaign name as a second tag if you've left that option on.
Because the sync is keyed on email, a lead who comments on two different campaigns and gives the same address shows up as one contact with both campaigns' tags, not two separate rows.
Connecting Mailchimp
Connecting Mailchimp needs your API key and an Audience ID. The key is checked against Mailchimp's own API before anything is saved: a bad key or a nonexistent audience is rejected right there, not discovered on the first failed sync.
Paste your Mailchimp API key (it carries its data-center suffix, like -us21, which the connect form reads automatically) and the ID of the audience you want new leads to land in. Before the connection is saved, ReplyMagnet calls Mailchimp's API to confirm the key is valid and that audience actually exists on your account; you get an immediate error if either is wrong, rather than a connection that looks fine and silently never syncs.
Once connected, the key itself is never shown again: Settings displays only a short hint (the last few characters) so you can recognize which key is connected without it being retrievable.
Connecting Kit
Connecting Kit needs your API key and a Form ID. Just like Mailchimp, the key and form are verified against Kit's API before the connection is saved, so a typo in either is caught immediately.
Kit's connect flow mirrors Mailchimp's: an API key plus the ID of the form you want new leads subscribed to. ReplyMagnet checks that the key authenticates and that the form exists on your account before saving anything, the same fail-fast behavior as Mailchimp, so you know your connection is live before your first real lead depends on it.
When sync runs
Sync fires automatically the instant an email is captured on the download page, typically within seconds. The "Sync existing leads" button in Settings backfills anyone captured before the connection existed; re-clicking it is always safe, since syncing is deduplicated by email.
New leads never need a manual step: the moment an email gate is completed, that address is queued for delivery to every connected ESP and usually lands within seconds. The only manual action is the backfill: useful right after connecting an ESP for the first time, to bring your existing lead list along instead of only syncing what comes in afterward.
Because sync is keyed on the lead's email, running the backfill button again later (say, after adding a second ESP) never creates duplicate contacts: it just re-confirms or updates what's already there.
If sync starts failing
A run of 8 consecutive sync failures (a bad key, a deleted audience, a provider outage) pauses the connection automatically. Settings shows the failure and a Re-enable button; new leads resume syncing as soon as you click it, no reconnection required.
Sync failures retry with the same backoff behavior as outbound webhooks, so an isolated hiccup never pauses anything. Only 8 misses in a row trips the pause, at which point Settings marks the connection Disabled and shows how many failures led to it. Re-enabling is one click and doesn't require re-entering your API key; the connection itself wasn't removed, just paused.
Plan availability
Automatic email sync is a Pro-and-above capability. On Starter or Basic, captured emails still land in Leads on every plan; they just don't push out to an ESP automatically until you upgrade, and any connection you've already made resumes untouched once you do.
The same emit-time gate that pauses outbound webhooks on a downgraded plan pauses ESP sync too: nothing about a saved connection is deleted, it just stops firing until the plan allows it again.
Common questions
Do I need both Mailchimp and Kit?
No. Connect whichever one you actually use. You can have both connected at once if you genuinely run two lists; a captured email syncs to every active connection.
What happens if I disconnect an ESP?
Syncing to it stops immediately. Contacts already pushed to Mailchimp or Kit stay there; disconnecting only stops future syncing, it doesn't remove anything from your ESP.
Can I re-run the backfill without creating duplicates?
Yes. The backfill is deduplicated by email, so clicking "Sync existing leads" again is always safe: it just re-confirms contacts that already synced.