Skip to main content
A registered form is ready to accept submissions, but “ready” and “tested” aren’t the same thing. Test from the form’s own Test section before relying on it.
1

Send a quick test submission

Send a test submission fills the form with sample answers and posts it from the app itself. Test submissions are marked, so they’re easy to tell apart from real ones. Want different sample values first? Edit them under Change what gets sent.
2

Test on a real page

Try it on a real page opens a hosted test page running the same install code your site uses — close enough to stand in for your cookie banner too, not just the form.
Every check, in detail: what's registered, what's allowed, and what's still blocking a real submission

Every check, in detail: what's registered, what's allowed, and what's still blocking a real submission.

3

Trip the defenses on purpose

Deliberately fail the honeypot and the bot check to confirm they’re working, rather than assuming. Every response says which defense answered, so a submission that doesn’t arrive has a reason you can look up.
You finish with a response for each test that names the check that answered, so you know the form accepts submissions or exactly what is blocking them.
A result reading “This page can’t post to your form” means that page’s origin isn’t on the form’s allowed-origins list yet — add it exactly as shown, with no trailing slash. See What protects a form for where that list lives (the in-app message currently points to “Form Processing”; the setting itself is under Web Edge Sessions).