Mailchimp Integration: setup and help

1. Upload and install the mprmailchimp ZIP in Modules > Module Manager.
2. Click Configure to open Mailchimp Settings.
3. Enter API Key and Audience/List ID for the intended audience.
4. Choose Opt-in Mode and enable Sync Opted-in New Customers if you want account-creation sync.
5. Configure the connected-site script separately if you want storefront tracking.
6. Turn on Enable Mailchimp and save.
7. Create a test customer who explicitly selects the newsletter subscription. Check the member in Mailchimp.

The API key suffix selects the Mailchimp data center, for example -us1. Copy the audience identifier from the relevant audience's settings. Do not paste an audience name in Audience/List ID.

Customer sync and the connected-site script are separate functions. For sync without storefront tracking, enable Sync Opted-in New Customers and turn off Enable Connected Site Script.

The module listens to actionCustomerAccountAdd. It checks the customer's newsletter flag, staff markers and outbound policy before admitting a sync job. The sync switch does not supply consent.

The request uses a stable member endpoint:

PUT https://us1.api.mailchimp.com/3.0/lists/YOUR_LIST_ID/members/MD5_OF_LOWERCASE_EMAIL

It sends email_address, FNAME and LNAME. For a new member, status_if_new is subscribed in single opt-in mode or pending in double opt-in mode. The PUT does not force an existing unsubscribed member back to subscribed.

The module queues the contact sync and tries the new job right away. Before sending, it checks again the customer's current state, newsletter opt-in, identity, the configured destination and the recorded opt-in mode. A job is held when the opt-in record is missing or the destination has changed.

For retries, the module declares the optional shared cron task mailchimp_member_sync, labelled Retry opted-in Mailchimp audience sync, with schedule every:60. It is disabled by default and requires the shop's existing MPR cron runner. This module does not bundle that runner. Enable the task there if you need scheduled retries. There is no module-specific public retry URL.

It does not bulk-import old customers, subscribe separate newsletter block signups or manage Mailchimp campaigns, tags, segments and journeys.

Copy the script URL from your Mailchimp connected-site snippet into Connected Site Script URL. Paste the URL only. Enable Enable Connected Site Script and save. The former generic .../users/mc.js snippet is not the current configuration.

The module bootstraps through displayBeforeBodyClosingTag. It uses live marketing-consent, staff and outbound checks, with a private configuration endpoint. Public page markup does not contain customer names or email addresses.

Test in a fresh customer browser with marketing consent. Check Network requests for your exact connected-site URL. The module itself does not send product, cart or purchase event payloads.

If you override the template, preserve its public configuration and runtime scripts:

themes/your-theme/modules/mprmailchimp/views/templates/hook/tracking.tpl

• New member absent: confirm Enable Mailchimp, credentials, Sync Opted-in New Customers and an explicit newsletter selection at registration.
• Double opt-in test: check for a pending member and Mailchimp confirmation workflow rather than expecting immediate subscription.
• Existing unsubscribed contact: the module does not force resubscription.
• Retry held: inspect integration diagnostics, current newsletter state, destination and opt-in mode. Confirm shared queue storage is available.
• Script absent: check the exact site URL, script switch, marketing consent, browser blocking and employee markers.
• Installation warning: use the module's Integrity page for required credentials and shared table checks.

No customer-by-customer audience-management screen is implemented here. Manage contact status and campaigns in Mailchimp.

Turn off the sync switch to stop new contact sync. Turn off the script switch to stop storefront connected-site loading. Turn off Enable Mailchimp for both.

Uninstall through Module Manager to remove the menu and stored module configuration. Shared queue and consent-withdrawal data remain after uninstalling. It does not delete contacts already held by Mailchimp.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.