By platform
Thinkific sign up page: why students stop
A stranger opens your course sign up page, fills in the form and presses the button, and nothing finishes. Mimiq sends simulated visitors through the same form and shows the field where each one gave up.
Why won't people finish my Thinkific sign up page?
A Thinkific sign up form usually stops people at one field, not on the page around it. Three things do it: the email is already in use, a password rule rejects what they typed, or a required question has no answer that fits them. Each error appears in a different place, and a visitor often misses it. A simulated test fills in the same form, presses the button and reports the field and message where each visitor stopped.
What this looks like in a report
“I bought the first lesson last spring with this address, so I may already have an account. The error sits at the top, not by the email box. A new password fails too, so I close the tab.”
The fix. Show each error next to the field it describes, and name the password rule the visitor missed. Then sign up in a private window with an address that already has a student account, and check the form tells the student to log in.
An illustration. Run a test to see your own.See a real sample report
The error appears on a field the student never touched
A sign up form on a course site is short, but it has rules the page never explains. An email field can reject an address that an earlier purchase or free download already used, and the message can appear at the top of the form while the student is looking at the password. A password rule may need a number or a symbol and name it only in small grey text, so the student retypes the same password three times and decides the button is broken. A required question with a dropdown that has no option for their country stops the whole submit.
- Enter an email that already has a student account. Does the error name the field it is about?
- Enter a password that meets only the length rule. Does the form say which rule it misses?
- Answer every question with the first option, then with the last. Does any answer block the submit?
- Press the button with every field empty. Does the first error appear on the first field?
- Repeat the sign up in a private window with a new address. Does the same field fail?
The order a student meets the error
A student fills a course sign up form from the top: name, email, password, then any questions the course added. When the submit does nothing, they go back to the field they changed last, which is usually the password. A required question further down the form can be the one that blocks the submit, and nothing on the screen points at it. The student retypes the password, decides the course is broken, and does not come back to try again.
Three causes, and what each one says on the screen
The email rule is the first cause. When an address is already in the student list, the form should send the student to log in or reset a password. When it only says the email is invalid, the student assumes they typed it wrong and tries another spelling. The password rule is the second cause. A rule that needs a symbol but names no symbol gives the same message as a short password, so a visitor who typed a long password keeps changing it. The third cause is a required question whose answers do not fit everyone. The form blocks the submit and shows the error in no visible place, so the button looks like it does nothing.
Check the student list before you change the form
Open the course admin and search for the address you used in the test. If it is there, the email collision is real, and the only question left is what the form tells that student. If it is not there, the error comes from a rule, so change the form first. Keep one test address that has never signed up and one that already has an account, and run both. A sign up that passes with the new address and fails with the old one points at the account check. For the whole path from sign up to the first lesson, the sign up flow page covers the steps after this form.
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 new required question can close the sign up again
Each new question, password rule or plan choice on the sign up form can block a student who passed last week. Run the same visitors through the form after every change, one with a new address and one with an address that already has an account. If the course sits behind a member login, give the visitors a test account to sign in with before they reach the lesson.
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 sign up page say the email is taken when I never signed up?
The address may already be in your student list, from an earlier purchase, a free download or a test you ran. Search the course admin for that address. If it is there, the error is right, and the form should send the student to log in or reset their password instead of back to the same screen. If it is not there, look at how the form checks emails.
Will a simulated visitor show me how many students will sign up?
No. The test shows whether a simulated visitor can get through the sign up form, and the field where they stopped if they could not. It does not predict how many real students would sign up. Get rates from your analytics or a live experiment, and use the test to find the field that blocks the form first.
Does the test create a student account in my course?
Yes, when the form accepts the visitor. Each run uses an address with a working inbox, so the account appears in your student list under that address. Give the test address a clear name, so you can find those accounts later and remove them by hand. Keep real customer addresses out of the test.
What happens when the sign up page has a Google button?
Visitors cannot sign in with Google, so the test stops at that button and reports it. Test the email and password path instead, which is the path a visitor without a Google account takes. A Google sign in is a step you can only check by hand, with your own account.
Can the test get past a sign up code sent by text message?
No. Visitors can receive email but not text messages, so a form that waits for an SMS code stops at that step, and the report says so. If the code can go by email, the visitor can enter it from their inbox. Otherwise you will need to check that step with your own phone.
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.