# Project flow defaults and identification settings

You'll choose your flow's default messages, control form prefill and visitor identification, and decide which activity appears in your reports.

Use **General** to set the messages visitors see in your flows, prefill forms, and control visitor identification. It's also where you choose what your dashboard emphasizes, filter analytics, and add code to form submissions.

Open the settings gear, then **General**. You can edit the project name in the page title. The public **Project ID** is beside it.

Changes to your project name and dashboard goal save as project information. Changes that affect your site save to the draft and need [publication](https://rightmessage.com/help/publishing-your-changes).

![General project settings showing the project name, primary dashboard goal and flow defaults](https://rightmessage.com/help/screens/settings-options.light.webp)

## Choose what your dashboard emphasizes

| Setting             | Choices and what they do                                                                                                                                                                                                          |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Primary goal**    | Choose **Automatic**, **Grow my email list**, **Quiz funnel**, **Segment my existing leads**, **Personalize my site**, or **Sell more**. Your choice sets what leads the dashboard. **Automatic** chooses based on live activity. |
| **Conversion goal** | Appears for **Personalize my site** and **Sell more**. Select an existing goal or clear the selection. Changing the primary goal to another kind clears this association.                                                         |

Choosing a primary goal doesn't create a conversion goal or start a campaign. [WorkForge](https://workforge.rightmessage.com) can choose **Grow my email list** to emphasize opt-ins without changing where its flow sends visitors.

## Set default messages and form prefill

![General settings for the post-survey message, submit button text, and form prefill](https://rightmessage.com/help/screens/account-flow-defaults.light.webp)

| Setting                  | What visitors see                                                                                                                                                                                                     |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Post-Survey 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.                                                           |
| **Submit Action Text**   | Text that replaces a form button's text during submission. Defaults to "Submitting..." It isn't the button's normal call to action.                                                                                   |
| **Disable Form Prefill** | Off allows known email and ordinary custom-field values to prefill RightMessage forms. On prevents those prefills. 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. Form prefill is on unless you disable it.

## 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](https://rightmessage.com/help/how-do-we-identify-returning-subscribers-or-contacts).

## Keep selected traffic out of your reports

**Stop collecting** accepts hostnames, IPv4 addresses, and IPv4 CIDR ranges. Choose **Add suppression rule** to add a row, or the trash control to remove one. RightMessage rejects duplicates after standardizing the rules. IPv6 isn't supported.

After publication, matching future traffic is excluded from RightMessage reporting and connected analytics providers. Existing history stays unchanged. Forms, redirects, widgets, and flows still run.

**Hide from analytics** requires Pro People access, with exceptions for eligible legacy accounts or explicit access grants. Choose **Add suppression rule**, enter an email in the row, and press Enter. That person's historical and future activity disappears from reports immediately, while collection continues. Choose **Remove** on an exclusion to make their activity visible again. You don't need to publish this change.

Neither choice [deletes analytics data](https://rightmessage.com/help/export-or-reset-project-data).

## Add bot protection keys

Use **Cloudflare Turnstile Site Key** for the public site key and **Cloudflare Turnstile Secret Key** for the encrypted server-validation secret. The secret field has a reveal control. Invalid values stay visibly invalid instead of saving. Leave the keys empty if you haven't set up bot protection.

Don't put the secret in screenshots, public code, or support messages. Bot protection uses invisible mode by default and can show a challenge when needed.

## Run JavaScript during form submission

Use **After Form Submit** for JavaScript 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 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](https://rightmessage.com/help/form-fields-reference) for question-backed inputs and [JavaScript hooks](https://rightmessage.com/help/javascript-hooks) for developer details.