Mailchimp landing page signup form: confirm step

With double opt-in turned on, a submit does not finish the signup. It starts a confirmation email, and the reader is subscribed only after clicking the link inside it. The landing page has to carry that news. If the message is vague, a reader who signed up assumes nothing happened and submits again, then gets a different message and decides the page is broken. The email itself can wait in a spam folder or sit in a promotions tab, so the reader has no way to know the signup worked.

• The message right after submit: does it say a confirmation is needed, and where to look for it?
• Required fields: any field the audience requires that the landing page does not show.
• The confirmation email: whether it arrives, and whether its link opens the confirmed page.
• A second signup with the same address, and whether the message it gets makes sense.
• Any hidden field in the embed code should stay empty, or the submit can look automated.

A Mailchimp audience can require a field or a consent option that the landing page never shows, usually because the page was built before the requirement was added. The reader sees a plain email box and presses the button. The submit then fails on a field the reader never saw, and the message about it sits out of sight. The owner who built the audience may have forgotten that extra field, because they set it up months ago and never submitted the page as a stranger.

Check it with two submissions. First an email alone, from a phone, to see whether the page accepts it. Then every field filled in, from a laptop, to see whether the full form goes through. If the email-only attempt fails and the full one works, a required field is missing from the page. If both fail, the problem sits in the submit or the message, and the next section is the place to look.

When double opt-in is on, the reader is not on the list until they click the confirmation link. The landing page should say that plainly, with the sender's name and what to look for, because a reader usually reads the page before opening their inbox. A message that says you are subscribed, when the reader is only waiting for a link, sets up a second submit and a confused reader. A message that says nothing about the email leaves them guessing whether to wait or try again.

A simulated visitor can finish this step, since it has a working inbox. The run opens the confirmation email, follows the link, and reports whether it landed on a confirmed page. It also reports whether the email arrived at all within the run, which is the part a reader's spam folder hides from you. If no email arrives, that tells you the message did not reach the inbox in time, and it does not by itself prove the form broke.

A reader who signs up twice with the same address gets a different response the second time, because the audience already knows that address. That response can be correct, or it can read as a failure. The page should say the address is already here and what to do next, such as checking for the earlier email. Test the second signup on purpose, from the same visitor, to see whether the message changes and whether a new confirmation email goes out.

Leave any hidden field in the embed code alone. Such a field is usually there to catch automated fills, and some form fillers type into every field on a page, hidden ones included. A filled hidden field can make the submit look automated, and the reader then gets a message that sounds like a rejection. Run a normal browser with no extensions, then read the message exactly as it appears.

Run a landing page with simulated visitors

The landing page keeps the fields it was built with, while the audience can gain a required field or a consent option later. A change made for a newsletter can quietly stop an early-access signup from working. Rerun the same signup with a phone visitor and a repeat address after each audience change, and before any ad campaign sends people to the page.