Place Mailchimp's signup form correctly and check that signups reach the intended audience.
This guide is for administrators with a Mailchimp account and a Diversity theme in Abicart Go, Plus or Pro. You need access to edit custom theme content. Mailchimp forms and account terms are separate from Abicart's built-in newsletter function, which requires Plus or Pro. TPL uses a different theme editor.
1. Choose the type of form
Embedded form: appears as part of a page or content block. Follow Mailchimp's embedded form guide.
Popup form: is created and published with its own display rules and site connection. Follow Mailchimp's popup guide.
The shop's own newsletter block: normally collects signups in Abicart customer records. It is not automatically a Mailchimp form. A separate integration is needed to export that data to Mailchimp.
2. Create the form in the correct Mailchimp audience
Select the correct audience, form fields, signup information and any confirmation in Mailchimp. Copy the entire publishing or embed code for the selected form. Never paste an API key into public HTML or JavaScript. Do not assume a signup also creates an Abicart account.
3. Place the code in the intended location
Check the active theme under Appearance → Themes and keep a copy of existing custom code.
If Mailchimp says the site code belongs in
HEAD, open Edit → Add-ons → Custom content in HEAD or the corresponding custom HEAD field.Add the complete snippet without replacing other working code. First check that the same code is not already present.
If you have the form's HTML, place it in the page's intended HTML content or a suitable custom HTML block instead. A visible form does not belong in HEAD.
Follow the provider's instructions if code belongs at the start or end of BODY; these are separate fields. Save only after checking the location and complete code.
Inserted code can apply to the whole theme. Do not paste truncated snippets or delete existing analytics or consent code. If an editor removes parts of a form, check the correct HTML mode and intended block rather than disabling protections or duplicating the code across fields.
4. Check display and recipients
Check form publication and audience in Mailchimp, plus the domain, page, language and display rules. A popup can be hidden after previous display or by a browser setting. Also check the consent solution; do not disable it to make an external script appear.
Make an intended test signup using an address you control and inspect the actual record in the correct Mailchimp audience. If double opt-in is used, the recipient must complete it before signup is finished. A form looking correct does not prove the recipient has the correct status. Checks sending confirmation emails or changing subscription status should use an intended test account.
Forms are separate from ecommerce integration
A form collects signups. It does not automatically enable customer, product, order or cart synchronisation. Abicart's built-in Mailchimp connection exports customers, products and orders but has no separate abandoned cart export flow. Completed orders appearing in Mailchimp therefore do not prove its cart reminders can start. Do not confuse this with the Rule connection's separate cart flow.
Quick start
Choose an embedded form or popup and the correct Mailchimp audience.
Copy the entire code and choose the correct HEAD, BODY or content field.
Keep existing code and avoid duplicates.
Check display and an intended test signup in the correct audience.
Subscription and theme
Custom code in Diversity themes is available in Go, Plus and Pro. Mailchimp has its own account terms and available form functions. Abicart's built-in newsletters and an external Mailchimp subscription are different functions.