Publish and test a form
Check preview, public URL, embedding, privacy and a test submission before going live
Publishing makes a form reachable for external people. Before going live, not only the layout but also data storage and notifications must be right.
Preflight
- mobile preview
- desktop preview
- required field errors
- email and phone validation
- privacy/consent text
- mappings to contact or ticket
- success screen
- confirmation email template
- spam protection
Go live
Open the preview
In the editor, check the form at desktop, tablet and mobile width with Preview or Open Preview.
Send a test submission
A submission from the preview is saved with the mode Preview and can later be filtered out of the responses. Use your own test address and clearly marked test data, no real customer.
Check the target system
Open the test response and check field values, attachments and links via Open ticket or Open contact.
Publish
Publish form (or Set live for later changes) makes the current state public.
Share the link
Use Copy form URL, QR code or Embed and put it on your website, email signature or campaign. Never share the internal dashboard route.
Test again after changing fields or mappings. Visitors only see the new version after Set live; old browser tabs may still show the previous one.
Deactivate
If data is processed incorrectly, choose Take offline in the editor. The form is then no longer publicly reachable, existing submissions are kept. Review open submissions and only publish again after the fix.
Related topics
How is this guide?