By platform
Shopify contact form not receiving email?
A shopper presses Send, sees a thank-you line, and nothing reaches your inbox. Mimiq sends simulated visitors through the contact page and shows whether the form submits and what the page says after Send.
Why is my Shopify contact form not receiving email?
A Shopify contact form sends mail only when every field passes its check and the store's contact address is an inbox someone reads. A thank-you line on screen does not prove either one, because the page moves on once the form is submitted, whether or not the message gets anywhere. Check the page first, then the address, then the spam folder. A simulated visitor test covers the page side in minutes, but it cannot tell you whether your inbox got the message.
What this looks like in a report
“I typed my question and pressed Send. Nothing happened that I could see, so I pressed it again and left, because I did not want to send the same message twice.”
The fix. Make the phone field in the contact section optional, and show each field's error next to the Send button. Then submit the form on a phone and confirm the confirmation appears.
An illustration. Run a test to see your own.See a real sample report
A thank-you line proves the page moved on, not that mail left it
A contact form on most Shopify themes is a section, and the store's contact address is a setting outside it. When a shopper presses Send, the page checks each field, sends the message to that address and swaps the form for a confirmation. A required field the shopper cannot see, such as a phone number below the Send button, stops the send with its error off screen. A script error can stop the request before it leaves the browser. And the confirmation can show even when the message goes to an address nobody reads. From your side, all three look like a mail problem.
- Submit the form yourself on the live store, in a private window. Does a confirmation appear, or only an error?
- Look for a red error under a field you cannot see, such as a phone number marked as required.
- Check the store's email address in its settings. Is it an inbox you read every day?
- Search the spam folder of that inbox for the subject line you typed into the form.
- Note whether the form clears after Send, keeps your text, or disappears into a thank-you line.
Read the page before you read the settings
Start with what the shopper sees. After a working Send, the form shows a confirmation and the page stays where it was. A blocked Send keeps the typed text and puts an error next to one field. Most owners never see that error, because the field sits under a phone layout that hides it or below the Send button where the eye does not go. Test the form on a laptop and on a phone, and write down what each one shows after Send. A form that submits on a laptop and stalls on a phone has a layout problem, not a mail problem.
Then look at what the browser recorded. Mimiq's visitor browser records JavaScript errors and failed requests on the step where they happen, so a send that never finished shows up as a request, not as silence. If the form did send but the confirmation never appears, the fault is in the script that draws the message, and changing the mail settings will not help.
The address is a setting, and it can point somewhere old
The contact form does not hold its own address. It sends to the store's contact address, which is set outside the form, and some stores still have one from before a domain change or a staff change. A message sent to a retired mailbox never reaches anyone, and the thank-you line still shows. Check the address first, then ask whoever reads that inbox whether any messages from the last week reached them.
The second place is the spam filter. A message generated by your store can land in spam when the mail provider does not trust the sending domain. Search that folder for the subject line you used in your own test. If you find it there, the form works and the mail setup needs attention, which is a different job from editing the theme.
A visitor test covers the page and stops at your inbox
To run the check, give Mimiq the contact page and one task a shopper would have: ask a question about delivery times through the form. Each simulated visitor has a working email inbox, so a confirmation sent back to the shopper can be read as well. You get back what the visitor saw after Send, the errors under each field, the failed requests, and a screenshot of the step where the send stopped or finished. Run it again on a phone after each change to the contact section.
The test does not show your store email, your spam folder or what your mail provider does with the message. Those stay yours to check. The quickest check is to send one message from a personal address to the store email after each change. A passing visitor test means the page submits. Only your own inbox can confirm the message arrived.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
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 theme edit can break the contact section after it last worked
Rerun the same visitor task after every change to the theme, the contact section or the store email. A new theme or an edited section can rebuild the form, so a check that passed last month proves little after the edit. Keep the task text with your store notes, and run it on a phone and a laptop before you publish.
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
Will the test show whether my inbox got the message?
No. The test shows what the page did after Send, including errors and failed requests, but it does not read your inbox or your spam folder. After a test, send one real message from a personal address to the store email and wait for it to arrive. That single message tells you more about delivery than any page check.
Why does the form confirm the send while my inbox stays empty?
The confirmation tells the shopper the form was submitted, and it can appear even when the message goes to an address that is no longer read. Open the store email in your settings and check that it is still an inbox you use. Then search the spam folder for messages from the last few days, using a word from the question you sent.
Can a visitor test cover a contact form that asks for a phone number?
Yes, for typing a number into the field. Simulated visitors can enter a phone number, but they cannot receive a text message, so a form that sends a code by text stops at that step and the test shows where.
Do I need to test the contact form on a phone as well as a laptop?
Yes. A form can submit on a laptop while its Send button or a required field sits off screen on a phone. Run the same task on both. The phone run shows the layout problem, and the laptop run shows script and address problems.
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.