Acquisition form reference
Every field, consent element, setting and message of the sign-up form, with the Campaign Translation key for each.
This page lists what the sign-up form holds and how it behaves. Everything is edited in Build > Settings > Campaign Translation > Acquisition Form, where each line is named by its key. If the group is read-only for you, ask your OmniLab administrator. For the steps, see Set up an acquisition form.
The form is copied into the campaign when you publish, so any change reaches participants only after you publish again.
Fields
| Field | Shown | Notes |
|---|---|---|
| Always | Checked before the participant continues | |
| First Name, Last Name | By default | Replaced by Full Name when that's on |
| Full Name | When passwordless.form.full_name.enabled is on | One name field instead of two |
| Phone Number | By default | The format is checked. passwordless.form.phone_number.required makes it compulsory |
| Date of birth | When passwordless.form.date_of_birth.enabled is on | See below |
| Gender | When set up | Its choices are in passwordless.form.gender.options |
passwordless.form.fields_order puts Email before or after the name.
Collecting one Full Name instead of first and last
Full Name suits audiences whose names don't split into a given and a family name. A contact keeps the shape they signed up with: OmniLab doesn't turn a full name into first and last names, or store first and last names as a full name. So one organisation can hold both shapes, and:
- the participants table and its export add a Full Name column when any contact has one;
- notification emails should greet with
{{ contact_fullname }}, which shows the full name, or the first and last names together.
Asking for a date of birth
Two settings, independent of each other, decide how strict it is:
| Setting | Values | Default |
|---|---|---|
passwordless.form.date_of_birth.requirement | Required, or optional | REQUIRED |
passwordless.form.date_of_birth.age_restriction | Over 18 only, or any age | ADULT_ONLY |
A date that can't be read always blocks, even with no age check. With the field optional, the age is checked only when someone fills it.
Consent and privacy
| Element | Keys |
|---|---|
| Marketing choice, as a checkbox or accept and decline buttons | passwordless.form.optin_type, passwordless.form.optin.text, passwordless.form.accept_optin.text, passwordless.form.deny_optin.text |
| Terms line and link | passwordless.form.terms_conditions.text, passwordless.form.terms_conditions.cta.link, passwordless.form.terms_conditions.requirement |
| Privacy line and link | passwordless.form.legal_notice.text, passwordless.form.legal_notice.cta.link |
Making the marketing choice mandatory
passwordless.form.optin.required makes ticking the marketing checkbox a condition of signing up. Participants who leave it unticked see Please accept to continue. It changes nothing for the accept and decline buttons, which already force an answer, or for returning participants logging in.
Compulsory marketing consent is a legal decision
Under GDPR and similar rules, consent usually counts only if it's freely given, and it isn't when people must accept marketing to take part. Making it compulsory also turns away everyone who won't subscribe. Check with whoever owns privacy at your organisation first. Use the terms acceptance, a separate control, as the place where refusing blocks entry.
Messages
The group also holds the titles and buttons (passwordless.form.signup.title.text, passwordless.create_account.button.text) and the error messages (passwordless.form.email_error.text and the other …error… keys).
The verification code email
If sign-up sends a code by email, the screen asking for it uses passwordless.enter_validation_code.title.text and passwordless.validationcode.subtitle.text. The email itself isn't editable. It's sent in the campaign's default language (English, French, German or Italian, and English otherwise), whatever language the visitor chose.
The double opt-in waiting screen
With double opt-in, participants confirm their address before they continue. The screen's title, text and buttons are the passwordless.verification… keys, translated in every supported language by default.