What is Social WiFi Login?

Definition

A social WiFi login lets guests authenticate to guest WiFi using an existing account, such as a social or email provider, instead of filling in a form. The venue receives whatever profile fields the guest consents to share. It replaces typing on a phone keyboard with a couple of taps.

The trade-off it makes

Manual email entry is slow on a phone keyboard and produces typos and disposable addresses. A social or federated login is two taps and returns a verified address, which removes the main reason guests give up on a phone form. The cost is dependence on a third-party identity provider: the fields they release change over time, their review processes gate what you can request, and an app policy change can alter your capture overnight. The pragmatic approach is to offer a social option alongside a plain email option rather than instead of it, so a policy change never leaves you with no way to capture a guest.

Consent does not travel with the login

A common mistake is treating a social login as consent to market. It is not. The guest authenticated; they did not necessarily agree to receive email. Under the GDPR, consent has to be freely given, specific, informed and unambiguous (Article 4(11)), so you still need a separate, unticked, specific opt-in for marketing, logged with timestamp and the wording shown. Keep the two actions visually distinct on the splash page so a guest who wants WiFi but not email can have exactly that, and so your consent record survives scrutiny.

Data quality considerations

Addresses returned by identity providers are verified, which improves deliverability, but they may be relay or alias addresses that forward to a real inbox and can be revoked by the guest at any time. Expect a slow, steady decay in that segment and monitor bounce rates by acquisition source. Segmenting your list by how the address was captured is worth doing on day one, because social-captured and manually-captured groups can behave differently and are easier to judge apart.