Learn Mokapen

MailChimp

Connect MailChimp to your organization's contacts in Mokapen. Import subscribers from your audiences, keep CRM and marketing lists aligned, or export to MailChimp contacts created in Mokapen — for each audience with dedicated rules, filters, and field mapping.

General overview: Integrations.

Requirements

• MailChimp account with at least one audience (list) created.
• Permission to authorize Mokapen via MailChimp login (OAuth).
• Mokapen Premium 3 plan to connect and sync.
• The first MailChimp account connection is usually started by the organization Owner (button visible only to users with that role).
• Mokapen permissions on contacts in the org (see Roles and permissions).

Connect the MailChimp account

Unlike MailerLite (API key), MailChimp uses sign in with MailChimp account on the provider's site.

1. User menu → Integrations → MailChimp.
2. The org Owner clicks Sync MailChimp (Premium 3).
3. Sign in with the desired MailChimp account (it may differ from your Mokapen email).
4. Accept the permissions requested by Mokapen.
5. Return to Mokapen: Connected account appears with the MailChimp email and who created the connection.

If you do not accept, no audience will be synced. The page will remain without connected lists.

After account login, configure sync direction at org level, then connect one or more audiences (see below). MailChimp does not use a single global sync like MailerLite: each list has its own settings.

What Mokapen requests from MailChimp

OAuth access to your MailChimp account to read audiences, subscribers, groups, and merge fields, and to create or update subscribers when sync direction allows. Mokapen does not replace the MailChimp dashboard for creating email campaigns — this page is for the subscriber address book aligned with the CRM.

If you revoke Mokapen from the MailChimp dashboard or the session expires → disconnect and connect again in Mokapen.

Account settings (entire integration)

Sync direction

• To Mokapen only — MailChimp → CRM.
• Both — import and export between connected audiences and Mokapen.
• To MailChimp only — CRM → MailChimp.

Contact export (Owner)

With bidirectional sync, the org Owner (Premium 3) can check the option that enables explicit export of Mokapen contacts to MailChimp in addition to import from audiences. Without Owner or an appropriate plan, the checkbox remains disabled.

This does not replace per-list export filters (type, tags, GDPR): it only defines whether, in bidirectional mode, Mokapen can also send contacts from the CRM to MailChimp. Filters per audience remain in each connected list's block.

Share sync

Who connected the account can let other members use the same MailChimp login (entire org or selected users). OAuth does not need to be repeated for each colleague, but each audience must still be configured.

Connect audiences (lists)

MailChimp organizes subscribers in audiences. In Mokapen each connected audience has a separate settings block.

1. With account already connected, click Connect MailChimp list (or equivalent «Connect list»).
2. Choose the audience from the menu (already synced lists are disabled).
3. Configure filters, field mapping, duplicates, and automatic sync for that list.
4. Check the data authorization, then Save / Sync.
5. Repeat for each audience you want aligned with the CRM.

If you have no audiences in MailChimp, create at least one from the MailChimp dashboard before connecting.

Import filters from MailChimp (per list)

For each connected audience, visible when sync is to Mokapen or bidirectional. Defines which MailChimp subscribers enter the CRM for that list — not the entire MailChimp account, only the selected audience.

All subscribers — imports anyone in the audience, including non-active statuses if present. Use with caution on large historical lists.

Active subscribers — limits to active subscribers (recommended in most cases): avoids filling the CRM with unsubscribed or no-longer-valid addresses.

Group — segment or internal group within the MailChimp audience: imports only those belonging to that subset (e.g. «VIP Customers» or «March Webinar»). Useful when the same audience contains different segments and you only need one in Mokapen.

When you change the filters a warning appears: after the change it is advisable to relaunch sync on that audience.

Export filters to MailChimp (per list)

Visible with sync to MailChimp or bidirectional, inside each connected audience's block. Filters apply only to that list: different audiences can have different export rules.

They define which Mokapen contacts can go out to that MailChimp audience — not just at the first «Sync», but also every time you create or modify a contact in the CRM (if export is active and sync direction allows).

In practice: you save a contact in Mokapen → Mokapen checks whether it meets the type, tags, and privacy consents set for that audience → only if it passes all filters does it create or update the record on MailChimp in that list. A contact that does not match stays in Mokapen but is not sent (and does not appear in that audience's export preview). If you change filters after already having synced, relaunch sync on the list: contacts that no longer match may stop being updated on that audience.

Type and Type 2 — restrict export to CRM contact categories (e.g. only «Customer»). Combinable with tags and privacy below.

Tags — one or more contact tags: exports only those who have them. Example: audience «B2B Newsletter» with tag «B2B» in export → only those contacts end up there.

Privacy / GDPR permissions — checkboxes with the consents configured in your org (newsletter, data processing, marketing, etc.). Check only those that must be already recorded on the contact for the MailChimp subscription to be lawful and GDPR-compliant.

Example: on the «Newsletter» audience you check only «Newsletter consent» → Mokapen sends to that list only contacts with that consent on file. A lead without consent stays in the CRM but does not end up on MailChimp, even with correct email and tags. Configure this filter before enabling automatic sync to the audience — especially if the Owner has enabled bidirectional export.

The counter and preview in the list block show how many contacts match the filters right now, before syncing. Check that you are not about to export thousands of records by mistake or that filters are not too tight (zero contacts in preview).

Remember: the Contact export (Owner) checkbox at account level is also needed if you use bidirectional sync with explicit export from Mokapen to MailChimp — otherwise the export remains limited by the sync direction chosen at the top of the page.

Field mapping (per list)

Link MailChimp merge fields of the audience to Mokapen columns. Email stays on the contact email field and is fixed. Each Mokapen column only once per list. Different audiences can have different mappings if merge fields do not coincide.

Duplicates and conflicts (per list)

When the same email exists in MailChimp (connected audience) and in Mokapen, Mokapen decides whether to create, merge, or update. Unlike MailerLite, here email comparison can be disabled — do so only if you understand the risk of duplicates in your address book.

Email comparison — active by default. Before creating a contact from MailChimp, Mokapen searches the org for a contact with the same email: if found, it does not create a second one but updates the existing one (according to conflict rules). Recommended to leave active, especially if you connect multiple audiences with overlapping subscribers.

Conflict handling — if same email but name, phone, or other mapped fields do not match, choose who «wins» for that audience:

• MailChimp — on discrepancy, MailChimp values overwrite Mokapen at sync.
• Mokapen — the CRM prevails; MailChimp is updated when sync direction and export filters allow.

Recommendation: initial import from a marketing audience → MailChimp often prevails on demographic fields; if the CRM is the commercial source of truth, choose Mokapen. Test on a sample before automatic sync on large lists.

Automatic or manual sync (per list)

Decides when Mokapen aligns that audience, not what (account direction + per-list filters). Each connected audience can be automatic or manual independently of the others.

Automatic sync — Mokapen propagates changes in the background for that list: a new subscriber on MailChimp may appear in the CRM, a contact modification in Mokapen (if it passes that audience's export filters) may update MailChimp without pressing the button each time.

Manual sync — no updates to that audience until you press Sync in the list block. Useful during setup (checking mapping and GDPR filters), after consent changes, or if you want to approve each batch before it goes out to MailChimp.

You can change mode with Save without deleting data already synced on that audience.

Visibility (per list)

Concerns contacts imported from that MailChimp audience into Mokapen (sync to CRM or bidirectional). Does not change who sees MailChimp — only who, in Mokapen, can open records created by the sync of that list.

All members (public visibility) — every org user with contact permissions can see the profiles imported from that audience: suitable for shared CRM.

Selected members only (private visibility) — restricts access to users or teams chosen in the menu. Others in the org cannot see those records even if sync is active. Useful for restricted audiences; combine with Mokapen roles.

If the org has global privacy rules (Master Team mandatory), some options may be preset or locked — follow what appears in the list block.

Remove a single list

At the bottom of a connected audience block there is Remove LIST: stops sync for that audience only, without disconnecting the entire MailChimp account or other lists. Already imported contacts remain in Mokapen unless manual cleanup rules apply.

Mandatory authorization

As with other contact integrations, check «I authorize Mokapen to create a copy…» before Save and Sync.

Behavior in Mokapen

• You can connect multiple audiences at the same time: same MailChimp account, different rules per list.
• A subscriber present in two connected audiences may generate two contacts in Mokapen if emails match but syncs are separate — consider audiences and anti-duplicate rules.
• With export active, contact updates in Mokapen (within filter limits) may update the subscriber on the corresponding audience.
• This integration is for contacts / subscribers, not campaigns: «MailChimp Campaigns» exists as a separate connection in Integrations.

Common issues

• I do not see the Sync button — only the org Owner can start the first account connection.
• No list available — create an audience in MailChimp; verify the correct account is connected.
• Duplicates across audiences — same email on two connected lists → two contact records possible; merge with Duplicates or connect only one audience.
• Export disabled — bidirectional sync + Owner + Premium 3 required for the export checkbox.
• Connection expired — disconnect account and sign in to MailChimp again.

Disconnect the MailChimp account

The Disconnect button at the bottom of the page (not «Remove LIST») closes the entire MailChimp connection for the org. A window opens with the Keep section:

• Contacts — box checked (default): contacts imported from MailChimp remain in Mokapen without sync. Unchecked: Mokapen removes from the org contacts linked to this MailChimp integration.
• Companies — same logic for company records linked to the sync.

Account disconnect does not automatically delete subscribers on MailChimp. Also revoke Mokapen from the MailChimp dashboard if you will no longer use the integration.

To detach only one audience use Remove LIST in that list's block, without disconnecting the entire account.

Type the confirmation word and confirm Disconnect. Operations on many contacts may take minutes.

Learn more: Contacts guide.