Email question reference
You'll see how an email question identifies visitors, which contact actions you can use, and how consent and typo suggestions work.
An Email question lets you collect an address, identify the visitor, and keep asking questions in the same flow.
When to use it
Use it when you want to connect someone's answers to their contact record without ending the flow at a form. Saving an email response and creating or updating a contact are separate actions.
Identification requires a supported, connected email platform or CRM. Without it, collecting an email address does not identify the visitor. A provider that only supports existing-contact lookup cannot create a new contact from the question.
Settings
| Control | Default and behavior |
|---|---|
| Placeholder | name@example.com. |
| Identify the visitor | On. Lets the submission identify the visitor. Turning it off hides contact-action and consent controls. |
| Contact action | Provider-dependent. Chooses how the connected platform finds or creates the contact. |
| Suggest fixes for typos | On. Offers a correction for recognized domain typos. |
| Show a disclosure | Off. When enabled, Disclosure supplies the explanatory text. |
| Show a consent checkbox | Off. When enabled, Checkbox label defaults to "I agree to receive emails." |
| Required | On. Controls whether the question can be skipped. |
Available contact actions can include Create/Update contact, Submit form, Add to list, and Add to tag. The list label can vary by provider. Actions that send to a destination require at least one selection. Structured destinations use a picker. Unstructured destinations accept comma-separated values. Replace an action saved for a different integration.
Email validation and consent
The address needs a local part, @, and a domain containing a dot, with no whitespace. This is not mailbox verification. Typo suggestions offer a correction rather than proving deliverability.
When a displayed consent checkbox is unticked, the response is kept without identifying the visitor or sending data to the email platform. Required does not force consent. The question can accept an email answer and continue without that consent.
The screenshot's demo provider only offers existing-contact lookup. Your contact actions depend on your connected provider. Follow Identify contacts with an email question for setup and a real submission check.
How answers are stored and synced
Save answers to shows your connected platform's name and offers compatible native or custom fields. An unmapped answer can still appear in Responses. A field mapping alone doesn't identify the visitor.
Email answers don't automatically create segments or per-answer branches. Use input-answer conditions to compare a stored email answer. Forms have their own native Email field rather than a linked Email question. See form fields.
The question-editor preview doesn't record answers, identify visitors, or send data to your email platform. Edits to an existing question save to your draft automatically and affect every use after you publish.
See shared question settings for wording and button labels, the Questions library reference for creation and reuse, and answer sync for destination checks.