How to Integrate Privy with Mailchimp

Connect the accounts first, then configure a Mailchimp sync rule on each Privy display that should send contacts. A successful account connection alone does not prove that a particular form is sending signups to the intended audience.

The setup and documented errors below follow Privy’s Mailchimp integration guide, checked September 6, 2026. The test checklist is editorial guidance for validating your configuration.

Connect the intended Mailchimp account

1. In Privy, open Settings → Linked Accounts.
2. Choose Mailchimp from the available integrations.
3. Sign in, review the authorization prompts and select the intended account.
4. Confirm that Mailchimp appears among authorized accounts.

Privy requires a Mailchimp Owner or Admin for this connection. If authorization fails, verify the account and role before changing unrelated display settings.

Add the display’s sync rule

Open the display and go to Settings → Advanced Settings → Sync Integrations. Choose Add Integration → Mailchimp, configure the destination options and save. Repeat for other displays that need this route.

Record the selected audience with the campaign name. This makes it easier to distinguish a missing contact from a contact sent to a different destination.

If you enable Require Double Opt-in, Privy says synced contacts receive a confirmation email and must follow its verification link before joining the mailable Mailchimp audience. Check subscription status as well as whether a contact record exists.

Verify a new signup from end to end

Use a new test address and record the campaign, page, submission time and expected audience. Run the actual form rather than treating an authorization success message as a full integration test.

If both tools send messages, document which system owns each follow-up and test for duplicate messages. The integration itself does not establish that every connected workflow is coordinated.

Diagnose documented errors

Expired or disconnected connection: use the Mailchimp Test Account control in Privy’s Linked Accounts area. Use its result to investigate authorization before editing field mappings.

Permissions error: have the Mailchimp Owner or Admin establish the connection, as required by Privy’s guide.

A required-field error: Privy documents failures such as a missing first-name or merge-field value when the selected audience requires information the signup does not provide. Inspect that audience’s field settings and compare them with the data your form actually collects.

Privy’s documented remedy is to make fields other than email optional in Mailchimp. Review the impact on other forms and workflows using that audience before changing its requirements. If a field is essential, confirm a supported way to collect and transfer it rather than silently dropping the requirement.

After a correction, submit a fresh test and verify the destination. The guide does not establish that resolving the configuration automatically replays every previously failed signup; investigate historical records separately.

Disconnect deliberately

Privy documents removal through the Mailchimp delete control in Linked Accounts. Before using it, identify affected displays and decide where future signups should go. Do not interpret disconnecting as a promise that existing contacts or automations in Mailchimp will be deleted.

For signup data checks, see Privy Profile Attributes. Browse Privy integrations for other destinations.