v1.12.1

Platform

Touchpoint dates are checked against the campaign. When a touchpoint has its own dates, publishing checks they sit inside the campaign's dates, and that the end comes after the start. The message names the touchpoint and the dates it must fit. You can still pick any date: the check runs when you publish. See Touchpoint dates override and Campaign dates.

One Full Name field. The sign-up form can ask for one Full Name instead of First Name and Last Name. It suits names that don't split in two, and shortens the form. It's set per campaign, and its label and error message are editable. The participants table and exports show a Full Name column. See Acquisition form reference.

A contact_fullname field for emails. It shows the full name, or the first and last names, whichever the contact gave. Use it in new templates: a greeting built from first and last name is empty for Full Name sign-ups. See Liquid bindings reference.

Date of birth can be optional, with or without the over-18 check. These are two separate settings. Campaigns already asking for a date of birth keep it required and age-checked. See Asking for a date of birth.

The marketing checkbox can be made mandatory. Participants who leave it unticked can't finish signing up. Accept and decline buttons don't change: they already force an answer. It's a legal decision as much as a setting, so read the caution first. See Making the marketing choice mandatory.

The verification code email follows the campaign's language. It's sent in English, French, German or Italian, and in English for any other language. It follows the campaign's default language, not the one a visitor picks. See The verification code email.

Events

Booking limits work on bookable Activities. Limits per participant, in total, per day or per week, now apply to Booking and Check-In Activities, as well as Check-In Only ones. The limit is checked when someone books. Only confirmed bookings count, so a cancellation gives the booking back. Limits set before this release now apply, so check the numbers on running Activities. See How the limits work.

Admin & Access

Each Studio user signs in one way. An admin sets it in the user's Authentication Provider field. People assigned to company sign-in can no longer use an email link instead. So your identity system's rules, such as multi-factor authentication, apply to Studio too. The sign-in page explains each refusal, including a wrong method. Once a user has a method, there's no fallback to another. See Users and authentication and Company sign-in (SSO).

Integrations

The email verification screens follow the campaign's language. With double opt-in on, the screen asking people to confirm their address is translated. So is the page they land on after the link. You can rewrite the wording in the campaign's form copy. See Double opt-in email verification.

The double opt-in publishing error shows in View Details. With double opt-in on for an organisation, campaigns can't publish until something sends the confirmation email. This error now appears under Auth in View Details, and names the screens to open. The setup counts only when it's active and covers the campaign's organisation. See Validation & publishing.

Developers

Contact hooks receive the full contact. Hook inputs include the marketing consent, the phone number and the form's extra answers. Each call also carries its campaign and organisation, so one function can serve many campaigns. A name now arrives in one of two shapes: build greetings with the SDK's name helper. See Function SDK reference and Hook functions.

Next steps

• All release notes
• Users and authentication
• Double opt-in email verification