Before you launch or pay for traffic
Landing page email list: where signups go missing
Your form says thank you, so you assume the address is on the list. Lists with double opt-in hold a new address as pending until the subscriber confirms, and a stranger who never gets that email is not on it.
Why does a landing page collect emails but the list stays small?
Usually the form works and the list counts only part of what it collected. Double opt-in lists hold a new address as pending until the subscriber confirms, and the confirmation may land in spam, arrive late or never be mentioned on the thank-you step. Compare the form's submissions with confirmed and pending addresses to find the gap, then check the thank-you step and the confirmation email from a new inbox. A simulated visitor shows whether that step tells them to check their inbox, and whether the confirmation reaches the inbox it was sent to.
What this looks like in a report
“I entered my email and got a thank you, but nothing said a confirmation was coming. I checked my inbox and nothing came. It may be in spam, or this may be a scam, so I am leaving.”
The fix. Say on the thank-you screen that a confirmation email is on its way, and name the sender and the subject line. Send a test subscription to a new inbox, check where it lands, and fix the sender setup if it arrives in spam.
An illustration. Run a test to see your own.See a real sample report
The form counts the signup, and the list counts only confirmed ones
A landing page form can succeed in the browser and still leave the address out of the list. A list with double opt-in keeps a new address as pending until the subscriber clicks a confirmation link. The confirmation email may land in spam, arrive after the visitor has forgotten the page, or come from a sender they have never seen. Your count of signups comes from the form, so it looks healthy. The list count comes from confirmed addresses, so it stays small. A stranger sees a thank-you line with no instruction to check the inbox, and never confirms.
- The thank-you step says a confirmation email is coming, and names the sender.
- The confirmation email reaches a fresh inbox within minutes, not the spam folder.
- The confirmation link opens a page that says the subscription worked.
- Pending and confirmed addresses are counted apart, so you can see which number is small.
- The form posts to the list the page names, not to an old list left from an earlier launch.
Read the list as pending and confirmed, not as one number
The wrong version is a single signup count that comes from the form. It tells you how many people pressed the button, and nothing about how many own the inbox they gave. The right version reads the list as two numbers, confirmed and pending, and checks the pending ones each day for a week after a change. A large pending number after a launch points at the email step, not at the page. Pending addresses also carry a cost. They have not shown that the inbox is theirs, so a campaign sent to them early can bounce or reach the wrong person. Keep them apart from subscribers in every report you read.
Walk the confirmation from a new inbox, as a stranger would
Follow the path a stranger follows, in order: the form, the thank-you step, the email, the link and the page after the link. Each step can fail on its own. The form may post and be accepted, while the thank-you step never mentions the email. The email may go to spam, or its link may point at a staging address left over from the build. A simulated visitor has an inbox that works, so a confirmation can reach it, and the run shows the thank-you screen it saw. If the confirmation does not arrive, the cause sits after the form, and the thank-you step is the first place to look.
Keep the form, the list and the confirm link pointed at one place
The wrong version is a form that posts to an old list from a test launch, while the live page reads from a new one, so signups land somewhere you do not check. The confirm link can fail the same way. After a domain move, a link in the email still points at the old address, and the visitor reaches a page that no longer exists. The right version checks that the form's list, the sending domain and the confirmation link all point at the live site. The quickest check is to open the link from a test subscription and read the address bar before you click anything else.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new sender address can send the next confirmation to spam
A team changes the sender name, moves the sending domain or adds a second signup form, and the confirmation email starts landing in spam. Send a fresh test subscription after each change, to an inbox a real subscriber would use, and read where it lands and what the thank-you step said before it. With paid credits, each traffic source can get its own visitors, given the search phrase or ad text it came from.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does my form show signups but my list stays small?
The form counts the submit. The list counts subscribers, and a list with double opt-in keeps an address as pending until the confirmation link is clicked. Compare the form's count with the confirmed and pending addresses in your email tool. If pending is large, the problem sits after the form, in the thank-you step or the confirmation email.
Should I turn off the confirmation email to grow the list?
That is a choice with a cost. Without confirmation, a typo or a made up address joins the list, and the first email may reach someone who never asked for it. If you keep confirmation, make the step easy to finish, and say on the thank-you screen that it is coming.
Can a simulated visitor tell me how many signups will confirm?
No. It does not predict how many real people will confirm, because a real person decides whether to open the email. It can show whether the thank-you step told the visitor to check their inbox, and whether the confirmation reached the inbox it was sent to.
Should I count pending addresses as subscribers?
Count them as signups, and keep them apart from subscribers. Pending addresses have not shown that the person owns the inbox, so they can bounce or draw complaints if you send to them early. Look at both numbers every week, and remove pending addresses that never confirm.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.