Acquisition form reference
Look up the fixed fields, consent elements, and behavior of the campaign-level acquisition form.
Look up the parts of the acquisition form: the fixed sign-up fields, the consent elements you can show, and how the form behaves. The acquisition form is managed once for the whole Campaign.
Core participant fields
The acquisition form is a fixed registration flow. The sign-up step can include these core fields:
| Element | Purpose | Notes |
|---|---|---|
| Identifies the participant | A valid email address is required | |
| First Name | Stores the participant's given name | Used in the sign-up flow |
| Last Name | Stores the participant's family name | Used in the sign-up flow |
| Full Name | Stores the participant's name as one value | Optional alternative to First Name + Last Name — see below |
| Phone Number | Stores a contact number | The form checks the phone number format |
| Date of birth | Stores the participant's birth date | Not shown unless your administrator turns it on — see below |
| Gender | Stores the choice the participant selects | Not shown unless your administrator turns it on |
Collecting one Full Name instead of first and last
By default the form collects First Name and Last Name as two fields. A Campaign can instead collect a single Full Name field, which suits audiences whose names don't split cleanly into a given and a family part.
When Full Name is on for a Campaign:
- the sign-up step shows one name field instead of two;
- First Name and Last Name are not shown and stay empty on the contact;
- the field order setting still applies — either Email then Full Name, or Full Name then Email.
Turning Full Name on is an admin change
The whole Acquisition Form translation group is admin-only, so ask your OmniLab administrator to enable Full Name for the Campaign. You can then edit its label and its "please enter your name" message like any other acquisition form copy.
Republish after switching
The acquisition form is frozen into the Campaign when you publish. Switching a live Campaign to Full Name — or back — only reaches participants after you republish it.
The choice is per Campaign, and it applies from the moment a contact signs up. A contact keeps whichever shape they were collected with: one who signed up through a First + Last campaign keeps those two values forever, and a Full Name contact keeps the single value. OmniLab never splits a full name into parts or joins parts into a full name, because both conversions lose information it cannot recover.
That means an organisation can hold both shapes at once, so anything that displays a participant's name has to read both. The participants table and its CSV export add a Full Name column whenever the results contain at least one contact who has one, leaving the existing First Name and Last Name columns untouched. In notification templates, use the contact_fullname binding, which resolves for every contact whichever shape they carry.
Asking for a date of birth
The sign-up step can ask for a date of birth. It is not shown unless your administrator turns it on, and when it is on, two further choices control how strict it is:
- whether the participant has to fill it — required, or optional and skippable;
- whether an age check applies — the participant must be over 18, or any date is accepted.
The two are independent, so all four combinations are possible. A Campaign that needs the date for segmentation but serves every age can require the field with no age check. A Campaign that only cares about the age check can leave the field optional, in which case the age is checked only for participants who choose to fill it.
Unless your administrator changes them, both are set to the strict reading: the field is required and the participant must be over 18. That is how the field has always behaved, so a Campaign already collecting a date of birth keeps working exactly as it does today.
| What the participant did | What they see |
|---|---|
| Left a required date of birth empty | Please enter your date of birth |
| Entered a date that can't be read | Please enter your date of birth |
| Entered a date under 18, with the age check on | You must be over 18 years old to continue |
An unreadable date always blocks, even with the age check off — without a date OmniLab can read, it has nothing to store.
Turning date of birth on is an admin change
The Acquisition Form translation group is admin-only, so ask your OmniLab administrator to show the field or to change whether it is required and age-checked. You can then edit its label and its messages like any other acquisition form copy.
Republish after changing it
The acquisition form is frozen into the Campaign when you publish, so a change to the date of birth field only reaches participants after you republish.
Consent and legal elements
Depending on your setup, the acquisition form can also show:
| Element | What it does |
|---|---|
| Terms text | Explains the terms the participant must review |
| Terms link | Opens the linked terms content |
| Terms requirement | Sets whether the participant must accept the terms before continuing |
| Marketing opt-in text | Explains the subscription choice |
| Marketing opt-in requirement | Sets whether the participant must accept marketing before continuing — see below |
| Legal notice text | Adds supporting privacy or legal context |
| Legal notice link | Opens the linked legal notice |
The marketing choice can appear as a checkbox or as explicit accept and decline buttons, depending on how the copy is set up.
Making the marketing choice mandatory
By default the marketing choice is optional: the participant can sign up whether or not they accept. A Campaign shown as a checkbox can instead require it, which makes ticking the box a condition of signing up. A participant who leaves it unticked sees Please accept to continue and cannot go further.
This applies only to the checkbox. The accept and decline buttons already force a decision — neither one lets the participant past without answering — so the setting changes nothing for Campaigns using them. It also applies only to sign-up: a returning participant logging in is never asked again.
Requiring marketing consent is a legal decision, not just a form setting
Under GDPR and similar regimes, consent is generally only valid when it is freely given, and consent a participant cannot refuse without being denied the service may not qualify. Requiring the marketing opt-in also means anyone unwilling to subscribe cannot enter your Campaign at all. Confirm with whoever owns privacy at your organisation before turning it on, and keep the terms acceptance — which is a separate control — as the place where refusal genuinely blocks entry.
Sign-up and verification messages
The acquisition form copy can include labels for:
- sign-up and login titles
- buttons and helper text
- verification code instructions after sign-up
- messages for invalid email or phone number input
- the name field's label and its "please enter your name" message
The verification code email
When sign-up sends a short code by email, that email now arrives in the Campaign's language instead of always being written in English. It is translated into English, French, German, and Italian; a Campaign running in any other language receives it in English.
Two things decide the language, and neither is the participant's browser:
- it follows the Campaign's default language, so a Campaign offering several languages emails every participant in its default one — a visitor who switches the page to German on a French Campaign still receives a French code email;
- a Campaign with no default language set receives the email in English.
Unlike the waiting screen below, the wording of this email is not part of your Campaign's editable form copy. The code itself, and the message carrying it, are the same for every Campaign in that language.
The double opt-in waiting screen
When double opt-in is on, a participant who signs up sees a screen asking them to confirm their email address before they can continue. Its copy is editable in the same Acquisition Form group:
| Element | Default copy |
|---|---|
| Title | Please verify your email address |
| Body | We sent you an email with a verification link. Click the link to confirm your address and continue. |
| Refresh button | I've verified my email |
| Resend button | Resend email |
| Resent confirmation | Email sent |
These ship translated in every language OmniLab supports, so you only need to edit them if you want different wording. The verification link itself is generated in the Campaign's default language, so the confirmation page a participant lands on matches the language they signed up in.
How the form behaves
Campaign-level by design
The acquisition form is managed once at campaign level and applies the same way to every Touchpoint.
- The structure is fixed rather than built from a chosen layout.
- The email is checked before the participant can continue.
- The phone number is checked in the form.
- When terms are shown as required, the participant must accept them before continuing.
- When date of birth is shown, whether it must be filled and whether an age check applies are both set by your administrator.
- When the marketing opt-in is shown as a required checkbox, the participant must tick it before continuing.
- After sign-up, OmniLab can send a verification code by email.
Where to edit it
Open OmniLab Studio > Build > Settings > Campaign Translation, then update the Acquisition Form group. If that section is read-only in your Campaign, ask an admin to make the change.