Connect Mailchimp to WordPress by choosing the form route, the intended audience and the email opt-in behaviour before placing the form. Test the full journey with an authorised test address: submission, confirmation and the resulting audience status. A form that looks correct on the page still needs a clear subscription outcome and an owner for delivery problems.
Which form route are you using?
Identify whether the proposal uses Mailchimp’s embedded form, a WordPress integration or a custom API submission. Record the actual route and its applicable documentation. Similar-looking forms should not be assumed to share the same audience, confirmation process or maintenance responsibility.
Mailchimp generates code for a customised embedded signup form. Mailchimp’s form-creation process selects the audience the form will use. The embedded-form guide makes audience selection part of the setup, so keep that choice in the handover rather than relying on a remembered account setting.
For a hypothetical newsletter, create a clearly named test audience and use an address the evaluator is authorised to receive mail at. Keep test subscriptions separate from an existing customer campaign. Agree who may change the form and who owns the corresponding audience settings.
Before choosing a route, review the complete publisher-required steps against the site’s agreed requirements. If a native form process does not fit those requirements, evaluate the documented integration route deliberately rather than removing a required step and assuming the same behaviour remains.
What should the reader understand before submitting?
Write clear form copy describing the intended email subscription and what happens next. Ask the content owner to identify the actual purpose, audience and linked information the reader needs. Keep a request for service separate from a newsletter signup unless the chosen experience makes both decisions understandable.
Use only fields justified by that purpose. For the fictional newsletter, ask why each proposed field is needed and how the team will handle it. Do not add unrelated information merely because a form builder can collect it.
Mailchimp recommends customising response emails before generating the embedded code. Review those messages alongside the page copy. The confirmation message, the on-page instruction and the eventual subscription should describe the same newsletter and organisation.
Keep the evidence for the consent decision with the responsible project owner. Product configuration and the organisation’s applicable consent requirements need to be assessed together; selecting a named opt-in method is not a complete determination of every obligation.
How does double opt-in change the journey?
Mailchimp describes double opt-in as form submission followed by a confirmation link. The double-opt-in guide adds the contact as subscribed after the confirmation step. The Mailchimp double-opt-in guide explains why submission and confirmed subscription are different points to inspect.
Mailchimp says its email double-opt-in setting applies to Mailchimp signup forms, with integration or API flows needing separate implementation attention. If the WordPress site uses a plugin or custom submission route, ask its implementer to show the actual status and confirmation behaviour. Do not mark the requirement complete merely because a similarly named setting is enabled elsewhere in the account.
For the proposed test, submit the authorised address and record the on-page response. Then inspect the message actually received and the audience status before and after the confirmation action. Keep those observations together so the reviewer can trace the journey without guessing from a single screenshot.
Mailchimp allows a custom website thank-you page for the email signup flow. Use that page to make the next step understandable. Ask the tester to explain what they believe has happened and what they need to do next. If they think they are already confirmed when another step remains, revise the wording and repeat the relevant check.
Which delivery checks should be recorded?
Separate creation of a confirmation message from evidence that the intended test recipient received it. Identify the authorised inbox, message observed and the result of using its confirmation link. Give a missing message a specific investigation owner rather than claiming that the page response establishes delivery.
Mailchimp’s final welcome email is optional and disabled by default. Agree whether that optional message belongs in the intended experience. Include it in the proposed checks if enabled, but do not mistake its absence for a failed confirmation when the chosen configuration does not send it.
Use this original subscription-journey worksheet to connect each stage with an observable outcome. Complete it for one named form and audience.
| Stage | Evidence to inspect | Question for the owner |
|---|---|---|
| Route selected | Embedded, integration or API configuration | Which documentation governs the opt-in behaviour? |
| Audience selected | Actual form-to-audience association | Is the test entering the intended audience? |
| Form submitted | Recorded page response and test address | What does the reader understand has happened? |
| Confirmation sent | Actual message received at the authorised inbox | Who investigates a missing or incorrect message? |
| Confirmation completed | Resulting audience status and response | Is the subscription state consistent with the agreed flow? |
| Welcome step | Selected optional configuration and observed message | Does it match the intended experience? |
| Form changed | New snippet or integration change record | Which pages and checks need updating? |
Include an incomplete confirmation case in the proposed exercise. Record how the team distinguishes a submitted test address from a confirmed subscriber under the chosen route. Avoid triggering a live marketing campaign simply to demonstrate an audience-status change.
What can change when the form reaches WordPress?
Embedded forms inherit the website stylesheet and may look different from their Mailchimp preview. Inspect the rendered form on the actual test page, including field labels, required-field messages and the confirmation instruction. Use the intended mobile layout as well as the desktop view.
Mailchimp says an updated embedded form requires replacing the old website code with the new snippet. Keep the location of each installed snippet in the maintenance record. If the same form appears on several pages, the owner should know which placements require attention when it changes.
Ask the evaluator to record what was updated and which version of the form the test used. This gives a later reviewer a way to distinguish a content correction from an audience or opt-in configuration change.
What belongs in the handover?
Retain the chosen route, audience identity, response copy, form placements and completed test observations. Assign ownership of subscription questions, missing confirmations and future form changes. The handover should make the reader journey and the operational follow-up equally clear.
See WordPress and business email for the wider site and messaging scope. Discuss your requirements with Spout using the subscription-journey worksheet and the form route you intend to assess.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.