Data capture, consent and the profile
Capturing guest data lawfully is what turns Wi-Fi into a marketing asset rather than a liability. The sign-in follows consent best practice and writes straight to the guest profile.
When you'd use it
Wherever data-protection rules apply, and whenever you want Wi-Fi sign-ins to feed audiences, campaigns and workflows without a manual export.
How it behaves
Marketing consent is a clear choice at sign-in, with separate opt-ins for email and SMS, unticked by default, and wording configured per venue. The consent state is written to the guest’s profile with the sign-in, and withdrawing consent later, for example through an unsubscribe link, writes back to the same record, giving a per-guest consent history.
Beyond name and contact, the screen can capture a date of birth, gender, country and custom questions. On repeat visits the recognised device updates the profile silently: the visit count increments and the last-seen date refreshes. Captured fields feed audiences and workflows immediately, with no export or import step.
The fields are the venue’s choice, email, first and last name, phone, postcode, date of birth, gender and country, plus custom questions, all alongside the marketing opt-in and all landing on one guest profile. The contacts captured are the venue’s own, to keep and export, held with UK data residency.
Configuration and options
- Consent options
- Separate email and SMS opt-ins, unticked by default, worded per venue.
- Consent history
- The consent state written to the profile, with later changes recorded.
- Profile fields
- Email, name, phone, postcode, date of birth, gender, country and custom questions.
- Silent updates
- Returning devices update visit count and last-seen without a fresh form.
- Data ownership
- The contacts are the venue’s own, to keep and export.
- Downstream use
- Captured fields feed audiences, campaigns and workflows immediately.
Good to know
Withdrawing consent updates the single profile, so it applies across every tool at once.
Consent is captured at the point of sign-in and stored against the guest, giving an auditable record.
A guest who signs in with a different email elsewhere may appear as a separate profile until the records share an email and merge.