Engage
Email List Building

WiFi login form fields: how many should you ask for?

You will be able to decide which WiFi login form fields to ask for on a first visit and which to save for later. The default is three to four: email, an unticked marketing consent box, first name and one segment field only if a named campaign uses it within 30 days.

12 min read2,945 words

Part of the guide topicWiFi email capture: the guide for venues

WiFi login form fields are the inputs a guest completes on your captive portal before getting online. The right number is three to four. Ask for first name, email and an unticked marketing consent box, as GDPR Recital 32 requires. Add one more field only if you will use it within 30 days. Collect everything else on later visits.

What are WiFi login form fields, and how many should you ask for?

A captive portal is the web page that opens when a guest joins your WiFi network. The guest completes it before the connection works. The fields on that page are the questions you ask in exchange for access. The guest wants one thing, a connection, so every question spends some of their patience.

The working answer holds across restaurants, hotels, retail and events. Every form needs an email address and a marketing consent box that starts unticked. First name earns a place because personalised subject lines and greetings depend on it. A fourth field earns a place only when a named campaign uses it, such as a birthday offer that needs a birthday month. Four inputs is your ceiling on a first visit.

GDPR supports the short form. Article 5(1)(c) sets the data minimisation principle: personal data must be adequate, relevant and limited to what the purpose needs. A field that no campaign uses is hard to defend under that test. It also costs you completions at the door.

Judge each field against three outcomes: opt-in rate, repeat visits and revenue per send. If a field moves none of them within a month, cut it. The list you want is not the longest one. It is the one where every contact agreed to hear from you and gave you enough to send something relevant.

{"items":[{"value":"80,000+","label":"live venues","note":"In 90 countries. Purple's own data"},{"value":"500 million","label":"logins a year","note":"Purple's own data"},{"value":"~50% higher","label":"opt-in rate on branded login pages","note":"Purple's own data"}]}

The opt-in figure matters most for this decision. A login page that looks like your venue gives the guest a reason to trust the form, and Purple's data puts the lift at around 50%. Field count and branding work together. A short form on a generic page still leaves opt-ins behind.

How does a WiFi login form turn a visit into a contact?

The flow from connection to campaign

A guest picks your network from the list on their phone. The phone detects the captive portal and opens your login page automatically. The guest completes the fields, makes a consent choice and taps connect. They go online, and your platform stores a contact profile with the consent decision and a timestamp.

{"kind":"flow","direction":"lr","caption":"How a WiFi login turns a visit into a consented contact","alt":"Flow diagram showing a guest joining venue WiFi, completing a short captive portal form, making a separate consent choice, getting online either way, and becoming a contact profile that receives campaigns only if they opted in.","nodes":[{"id":"a","label":"Guest joins venue WiFi","sub":"Phone connects to your guest network","tone":"neutral"},{"id":"b","label":"Captive portal opens","sub":"Branded login page loads automatically","tone":"brand"},{"id":"c","label":"Form fields","sub":"First name, email, one optional segment field","tone":"brand"},{"id":"d","label":"Consent choice","sub":"Unticked box, separate from WiFi terms","tone":"brand"},{"id":"e","label":"Guest online","sub":"Access granted whether they opt in or not","tone":"success"},{"id":"f","label":"Contact profile","sub":"Email, consent record and visit history","tone":"brand"},{"id":"g","label":"Campaign","sub":"Sent only to guests who opted in","tone":"success"}],"edges":[{"from":"a","to":"b","label":"redirect"},{"from":"b","to":"c","label":"guest completes"},{"from":"c","to":"d","label":"submits"},{"from":"d","to":"e","label":"yes or no"},{"from":"d","to":"f","label":"choice and timestamp stored"},{"from":"f","to":"g","label":"opted-in segment"}]}

Two design choices in that flow decide your list quality. First, the consent choice sits apart from the WiFi terms. Second, the guest gets online whether they opt in or not. GDPR Article 7(4) asks whether a service depends on consent the service does not need. If it does, that consent is unlikely to count as freely given.

Each return login adds another visit to the same profile. That is where repeat-visit campaigns start. A lapsed-diner email to guests who have not logged in for 60 days is one example. You only get that profile if the first form was short enough to finish.

The field stack

Think of the form as layers. The base layers appear on every form. The upper layers appear only when they pay for themselves.

{"kind":"layers","direction":"tb","caption":"The field stack: what to ask on a first visit and what to save for later","alt":"Layered diagram showing WiFi login form fields in five tiers, from the required email address and consent box at the base to preference questions asked on later visits.","nodes":[{"id":"l1","label":"Layer 1: email address","sub":"Required. Every campaign depends on it","tone":"brand"},{"id":"l2","label":"Layer 2: marketing consent","sub":"Unticked box plus a link to your privacy notice","tone":"brand"},{"id":"l3","label":"Layer 3: first name","sub":"Personalises subject lines and greetings","tone":"neutral"},{"id":"l4","label":"Layer 4: one segment field","sub":"Birthday month, postcode or visit reason, only if a campaign uses it","tone":"neutral"},{"id":"l5","label":"Later visits","sub":"Preferences, dietary needs and interests, one question per visit","tone":"success"}],"edges":[{"from":"l1","to":"l2","label":"always paired"},{"from":"l2","to":"l3","label":"recommended"},{"from":"l3","to":"l4","label":"optional on first visit"},{"from":"l4","to":"l5","label":"ask on return"}]}

The stack also tells you what to drop when completions fall. Remove fields from the top down. Never remove the consent box. Without it, you have no clear basis to send marketing email to most of those contacts.

Why every field has a price

Your guest is standing at a bar or a hotel lift with a phone in one hand. Typed fields cost the most, because the mobile keyboard covers half the screen. A dropdown or a single tap costs far less. A birthday month picked from a list is cheaper than a date of birth typed in full.

"Optional" does not mean free. An optional field still makes the form look longer, and length is the first thing a guest judges. If an optional field is rarely completed, you pay the visual cost for little data. Move it to a later visit.

Captive portal form fields, login form length and sign-up fields: what is the difference?

These terms get used as if they mean the same thing. They do not, and mixing them up leads to the wrong fix.

{"caption":"Captive portal form fields vs login form length vs WiFi sign-up fields","asOf":"2026-06-10","columns":[{"key":"term","label":"Term"},{"key":"meaning","label":"What it means"},{"key":"decides","label":"What it decides"},{"key":"confused","label":"Often confused with"}],"rows":[["Captive portal form fields","The individual inputs on the page a guest completes before getting online","What data you hold on each guest","WiFi terms, which govern network use, not marketing"],["Login form length","The effort between joining and getting online: inputs, taps and typing","How many guests finish and reach the opt-in","Field count alone. A dropdown costs less than a typed field"],["WiFi sign-up fields","The first-visit set a new guest sees","Who enters your list","Return-visit prompts, which should ask less"],["Marketing consent box","A separate, unticked opt-in for email or SMS","Whether you may send campaigns","Accepting WiFi terms, which is not consent to marketing"],["Required field","An input the guest must complete to get online","The minimum data on every profile","Consent. A marketing opt-in should never be required for access"],["Progressive profiling","Asking one new question on a later visit","Profile depth over time","Long first-visit forms"],["Data minimisation","GDPR Article 5(1)(c): collect only what the purpose needs","Which fields you can justify asking","Storage limitation, a separate principle"]],"footnote":"GDPR references are to Regulation (EU) 2016/679, retained in the UK as UK GDPR."}

The costliest confusion is between a required field and consent. Making email required to get online is a product decision. Treating that email as permission to market is a separate legal question. In the UK, PECR Regulation 22 requires prior consent for marketing email to individuals. The narrow "soft opt-in" exception covers details collected during a sale or the negotiation of one. A free WiFi login is not obviously either, so most venues ask for explicit consent.

The second confusion is between field count and form length. Three typed fields can feel longer than five taps. Measure length as effort, not as a number of boxes.

Where do WiFi login form fields show up in a real venue?

The right fields depend on who is logging in and what you will send them. Use the vertical's own noun in your form copy: diner, guest, shopper or fan.

Venue type Who logs in First-visit fields Ask on a later visit
Restaurant, pub or bar Diner First name, email, consent, birthday month Dietary needs, favourite occasion
Hotel Guest First name, email, consent Reason for stay, loyalty scheme interest
Retail store Shopper First name, email, consent, postcode Product categories of interest
Stadium or event venue Fan or attendee Email, consent First name, team or artist preference

Restaurants, pubs and bars

Diners log in while they wait for a table or a drink. The visit is short and attention is elsewhere. Birthday month is the classic fourth field because the diner can see its purpose: an offer in the right month.

Hotels

Hotel guests stay longer and log in several times. Your property management system often holds their name and booking details already. Use the WiFi form for what that system lacks: a marketing consent choice and an email the guest actually reads. Ask about the reason for stay on a later login.

Retail

Postcode earns its place for shoppers because it maps your catchment and supports local store campaigns. Product interests are better asked once the shopper has a reason to trust you, usually on a return visit.

Stadiums and events

Fans log in at the same moment, often around kick-off or doors opening. Every extra input multiplies across a crowd of thousands. Keep the first form to email and consent, and add the rest later.

An illustrative multi-site rollout

This scenario is illustrative, not a named deployment. A 40-site pub group inherits a login form with eight fields, including phone number, full date of birth and gender. Opt-in reporting is flat. The CRM team cannot name a campaign that uses half the fields.

The marketing lead runs a field audit. Each field gets one question: which campaign used it last quarter? Phone, gender and full date of birth have no answer, so they go. Birthday month replaces date of birth because the birthday campaign only needs the month. The consent box moves out of the terms paragraph and starts unticked.

The new form has four fields. The team compares opt-in rate per site for four weeks before and after the change. Then they add one question about preferred occasions on a later visit. The decision is made field by field, against campaigns, not against a template.

{"tone":"proof","title":"Running at scale","text":"Harrods, Pizza Express and McDonald's run guest WiFi with Purple, part of **80,000+ venues in 90 countries** and **500 million logins a year** (Purple's own data)."}

Where do venues get login form length wrong, and what are the limits?

Asking for data no campaign uses

The most common mistake is collecting data "in case it is useful later". Gender, full date of birth and phone number appear on many forms with no campaign behind them. Under GDPR Article 5(1)(c), "in case" is not a purpose. Cut the field or name the campaign that needs it.

A single "I accept the terms and agree to marketing" box fails twice. It hides the marketing request inside a condition of access. It also gives you consent you may not be able to rely on. Keep two separate choices.

{"tone":"warning","title":"Pre-ticked boxes do not count","text":"[GDPR Recital 32](https://gdpr-info.eu/recitals/no-32/) states that silence, pre-ticked boxes or inactivity should not constitute consent. A pre-ticked opt-in fills your list with contacts you have no valid consent to email."}

Mandatory phone numbers and dates of birth

A mandatory phone field asks for more than WiFi access needs, and it raises the effort of every login. If you want SMS marketing, make the number optional and give it its own unticked SMS consent. If you need to know a guest is an adult, an age confirmation is often enough. A full date of birth is more data than that purpose needs.

Edge cases: younger guests, returning visitors and language

Venues that attract teenagers need extra care. GDPR Article 8 sets the age of digital consent at 16, and member states may lower it to 13. The UK set it at 13. Check how this applies to your marketing opt-in before you add an age field.

Returning guests should not see the full form again. A return visit is the moment for one new question, not a repeat of the first four. Translate the form where you see international visitors, because a field a guest cannot read is a field they skip.

The three-to-four rule is a default, not a law. Ask for more on a first visit only when the guest gets something visible in return, such as a loyalty sign-up or a members' area.

{"tone":"note","title":"Scope","text":"This guide explains the principles behind field choice for marketing teams. It is not legal advice, so confirm your consent wording with your data protection officer."}

How does Purple Engage handle WiFi login form fields?

Purple Engage builds your email list from the guest WiFi login itself. Mailchimp, Klaviyo and HubSpot send campaigns to a list you already hold. They do not build that list at the door. Purple Engage does, with consented, first-party data from every guest who chooses to opt in.

Purple runs as a hardware-agnostic cloud overlay on the WiFi you already own. That covers Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. The form lives in the platform, so the field decisions in this guide are configuration choices, not a hardware project. Opt-ins are conscious-choice opt-ins, separate from the WiFi terms. Branded login pages see opt-in rates around 50% higher (Purple's own data). Purple is ISO 27001 certified and GDPR compliant.

Each login feeds a guest profile you can segment and send to. See how those profiles come together on the guest data page. For capture, consent and campaigns end to end, start with WiFi email capture: the guide for venues. If you run Meraki, Ruckus, Cambium or UniFi, read email capture on Cisco Meraki, Ruckus, Cambium and Ubiquiti UniFi WiFi. For the wider marketing view, see Purple's WiFi marketing guide.

Where this concept bites is your first field audit. One form across every site multiplies a bad field by every login you take. The next decision is how guests identify themselves at all. Read social login vs email login on a captive portal to choose the login method that gives you better marketing data.

Frequently asked questions

How many fields should a WiFi login form have?

Three to four on a first visit. Ask for email and an unticked marketing consent box on every form. Add first name for personalisation. Add one segment field only if a named campaign uses it, such as birthday month for restaurants or postcode for retail. Save everything else for return visits, when the guest already knows your network and your brand.

Does a longer WiFi sign-up form give better marketing data?

No. A longer form gives you more columns but fewer completed profiles. Data that no campaign uses adds nothing to revenue per send. GDPR Article 5(1)(c) also expects you to collect only what your stated purpose needs. Better data comes from a short first form, a clear consent choice and one new question on each return visit.

Is collecting email at WiFi login GDPR compliant?

Yes, when you collect it properly. Use a separate, unticked marketing consent box, link to your privacy notice, and let guests get online whether they opt in or not. GDPR Recital 32 rules out pre-ticked boxes. Article 7(4) questions consent tied to a service that does not need it. In the UK, PECR Regulation 22 also applies to marketing email.

Will Purple Engage work with the WiFi hardware we already own?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You keep your access points and add the branded login page and form on top. There is no rip and replace. For vendor-specific detail, read our guide to email capture on Meraki, Ruckus, Cambium and UniFi.

How does Purple Engage compare with Mailchimp or Klaviyo for list building?

Purple Engage builds the list; email-only platforms send to a list you already have. Mailchimp, Klaviyo and HubSpot do not capture guests at your door. Purple Engage captures consented, first-party contacts at every WiFi login across your venues. Branded login pages see opt-in rates around 50% higher (Purple's own data). Your list grows with foot traffic, not with ad spend.

How much effort does it take to change our login form fields?

Changing fields is a configuration task, not a hardware project. Purple runs as a cloud overlay, so the form lives in the platform rather than on your access points. The bigger effort is the audit itself. You match each field to a campaign and agree consent wording with your data protection lead. Most of the work is a decision, not a deployment.

What does Purple Engage cost?

Pricing depends on your plan and the number of venues you run. Purple offers three plans: Connect, Capture and Engage. Ask for a quote based on your sites and the features you need. Then weigh it against what one extra repeat visit per opted-in guest is worth across your estate. That comparison is the business case for your board.