Rules for Showing Ads on Wi-Fi Login Pages

A Wi-Fi login page looks like ideal ad space. Every guest passes through it, nobody can skip it, and attention is undivided.

Those three qualities are precisely what makes it easy to break the rules. Space that can't be bypassed invites the temptation to hold people there, and holding people is exactly what's prohibited.

One line separates everything

If only one thing is remembered from this page, let it be this: ads may sit along the path, but must not be a condition of passing.

The difference shows in one simple question, does the guest still get connected if they ignore the ads entirely? If yes, the placement is fine. If no, it has become a gate.

What ad networks prohibit

These rules come from ad networks' own publisher policies rather than government regulation. But the consequences often arrive faster: account termination and withheld payment typically apply without warning.

Forced or incentivised impressions

An ad that must be watched to obtain something, a connection, a coupon, access, breaches the terms of virtually every major network. The reason isn't moral but economic: a forced impression demonstrates no interest, and advertisers pay for interest.

Countdowns and delayed buttons

Often treated as a safe compromise, and it isn't. It holds the ad on screen for a set period, inflates viewability artificially, and locks the visitor in place. In policy terms this counts as invalid traffic: the category carrying the heaviest penalties.

Pages that are only ads

A page with no content that stands on its own is generally judged to exist solely to display advertising. A login page containing just a connect button and two ad units falls into this category.

Ads in disguise

Ads made to look like system buttons, notifications, or part of the login flow. This breaches two things at once: publisher policy, and the principle that advertising must be recognisable as advertising.

The personal data side

Login pages often collect data at the same time. The moment that data is used to target ads, data protection rules apply in full.

• The purpose must be stated upfront, in language people can understand, not buried inside lengthy terms.
• Consent for advertising must be separate from consent to use the Wi-Fi. Bundling them makes the consent meaningless, because people have no option but to agree.
• Declining must not cost the connection. A guest who doesn't want their data used for advertising is still entitled to use the Wi-Fi.
• Keep only what's needed, and set a retention period from the outset.

A summary of the obligations is in the guide to collecting customer data, and the legal basis in the guide to personal data protection.

Placements that stay safe

What makes a placement safe isn't the number of ads but its relationship to the task the visitor is trying to complete.

Desktop versus phones

Almost every public Wi-Fi guest is on a phone, and placement rules are tighter on small screens because there's less room.

• Avoid sticky ads that follow scrolling and permanently cover part of the screen.
• Reserve fixed space for each slot, so a late-arriving ad doesn't shift the button someone is about to press. Sudden shifts are the leading cause of mis-taps.
• Don't stack ads adjacently with no content between them.
• Watch page weight. A login page opens on a connection that may not be fast, and a heavy page prolongs something that ought to be instant.

A technical quirk specific to login pages

One thing makes login pages different from ordinary pages, and it's often missed: on many devices, this page opens in a special window rather than a full browser.

That window frequently restricts scripts, storage, and connections to other domains, so ads depending on any of those simply don't appear. This isn't a violation, but it explains why some slots look empty for no obvious reason.

How that window works is explained in the guide to captive portals, and the problems that come with it in the guide to login pages that don't appear.

Checklist before going live

• Guests still connect if they ignore every ad.
• No countdown, no delayed button.
• The connect button is visible without scrolling.
• Every ad unit is labelled.
• The page contains something useful besides advertising.
• Ad consent is separate from Wi-Fi consent.
• Declining targeting doesn't remove the connection.
• Space for each slot is reserved so the layout doesn't shift.
• Terms of use are available and readable, see the guide to guest Wi-Fi terms.

Broader responsibilities as a network provider are covered in the guide to Wi-Fi owner responsibility, and general rules for publicly offered Wi-Fi in the guide to public Wi-Fi rules.

A word on the arithmetic

Login pages earn less than people imagine. Visits are brief, a guest passes through only once a day, and most never scroll at all.

That's where the temptation to compel comes from, and why it's so rarely worth it. A terminated account removes all the revenue, not just the difference. The more durable approach is to treat the page as an ordinary page that happens to be an entrance, rather than as a tollgate.

Using Wi-Fi for marketing more broadly is covered in the guide to Wi-Fi marketing for small businesses, and the cost side in the guide to the cost of guest Wi-Fi.

Ads on a login page aren't a problem. Ads that become a condition of passing are, and countdowns belong in that category, however often they're treated as a middle ground.

One test covers nearly every case: does the guest still get connected if they ignore every ad? If the answer is yes, and the page contains something worth reading, you're almost certainly on the right side of it.

Frequently asked questions