Project flow defaults and identification settings
You'll choose your forms' default messages, control email pre-fill and visitor identification, add bot protection, and run your own code after a form submits.
Updated
View as MarkdownUse Forms & widgets to set the messages visitors see around your forms, pre-fill known email addresses, recognize visitors with Email Watcher, and add code that runs after a form submits.
Open Project settings (the gear at the bottom of the sidebar), then Forms & widgets. Every section on this page saves to your draft and reaches your website when you publish.
Set default messages and email pre-fill
| Setting | What visitors see |
|---|---|
| Thank-you message | Fallback after the last question when no offer or form follows. Defaults to "Thanks for answering!" It doesn't override an offer's own completion behavior. |
| Submitting text | Text that replaces a form button's label while the form submits. Defaults to "Submitting..." It isn't the button's normal call to action. |
| Pre-fill known email addresses | On lets known email and ordinary custom-field values pre-fill RightMessage forms. Off prevents those pre-fills. Hidden-field values and remembered multiple-choice selections are separate and can still populate. |
The text fields show your project's saved wording. Edit those values rather than assuming a copied template uses the defaults. Pre-fill is on unless you turn it off.
Identify visitors with Email Watcher
Email Watcher is off unless you turn it on. When it's on, RightMessage watches input fields and identifies a visitor from an email address when they leave the field. This can capture an address from a third-party form that RightMessage doesn't natively support.
Identification happens without waiting for the third-party form to report a successful submission. Before you turn it on, consider whether someone might enter another person's email in your forms. Publish the change before testing with the normal live snippet.
Connecting an email platform alone doesn't identify every visitor. See how RightMessage identifies visitors.
Show or hide the badge
Show the badge on widgets controls the "Powered by RightMessage" badge. The badge link includes your affiliate ID, which you manage in Your account > Affiliate. See the badge setting.
Add bot protection keys
Under Bot protection, paste your Cloudflare Turnstile Site key and Secret key. The secret is stored encrypted and has a show control. Invalid values show an error instead of saving. Leave both keys empty if you haven't set up bot protection, and see protect forms from bots for the full setup.
The keys save as you type, but they reach your website when you publish. Don't put the secret in screenshots, public code, or support messages.
Run JavaScript after a form submits
Under Developer, use JavaScript after a form submits for code that runs during a valid RightMessage form submission, before RightMessage calls your email platform. Liquid expressions such as {{ form }} and {{ form.email }} give your code access to the form data. The editor highlights your code and follows the dashboard's light or dark theme.
Paste plain JavaScript. If you paste it inside <script> tags, RightMessage removes the tags. If your code throws an error, the form still submits, records its conversion, and follows its redirect; the debugger shows the error as a warning.
The code runs before your email platform accepts the submission, so don't use it as confirmation that the contact was saved. It also runs in the debugger and can still send data to external services or make other changes.
Use this only when you need custom behavior for RightMessage forms. It doesn't run for every external form on your website. Review and test your code before publishing it, and don't pass personal data to tools without an approved purpose.
See form fields for question-backed inputs and JavaScript hooks for developer details.
Keep selected traffic out of your reports
Traffic filtering lives in Project settings > Privacy & data:
- Stop collecting accepts hostnames, IPv4 addresses, and IPv4 CIDR ranges. Enter one and choose Add rule, or remove a row with its remove button. IPv6 isn't supported. After you publish, matching future traffic is excluded from RightMessage reporting and connected analytics providers. Existing history stays unchanged, and forms, redirects, widgets, and flows still run.
- Hide people from analytics takes an email address and Hide person. That person's past and future activity disappears from reports right away, while collection continues. Unhide brings it back. You don't need to publish this change. Plans without People access see which plan includes it instead.
Neither choice deletes analytics data. See exclude test visitors for your own browser.