WiFi Landing Page vs. Splash Page: What's the Difference?

This technical reference guide clarifies the architectural and functional differences between WiFi landing pages and splash pages — two terms frequently conflated by both IT teams and marketing departments. It provides network architects, IT managers, and venue operations directors with actionable deployment strategies to optimise captive portal performance, ensure GDPR and PCI DSS compliance, and maximise ROI across enterprise venues including hospitality, retail, and public-sector environments.

📖 8 min read📝 1,923 words🔧 2 examples❓ 3 questions📚 9 key terms

🎧 Listen to this Guide

View Transcript

Welcome back to the Purple Technical Briefing. Today we're tackling a question that comes up in almost every initial scoping call with CTOs and network architects: What exactly is the difference between a WiFi landing page and a splash page?

In the consumer world, people use these terms interchangeably. But when you're architecting an enterprise guest network across fifty retail locations, or a high-density stadium deployment, confusing the two can lead to compliance headaches, broken user journeys, and missed ROI.

So, over the next ten minutes, we're going to define the technical distinction, look at the architecture, discuss common implementation pitfalls, and finish with a rapid-fire Q and A. Let's get into it.

[SECTION: TECHNICAL DEFINITIONS]

First, let's define the terms. When we talk about a Captive Portal, we're referring to the entire walled-garden mechanism that intercepts HTTP and HTTPS traffic and forces a client device to authenticate before granting external network access.

Within that portal flow, the Splash Page is the gatekeeper. It is the very first screen a user sees when they connect to the SSID. Its primary technical function is authentication and authorisation. It's where the user accepts the Terms and Conditions, enters their credentials, or authenticates via an identity provider — perhaps using OAuth or a loyalty integration. From a compliance standpoint, this is where you handle GDPR consent and PCI DSS disclaimers if you're processing payments.

Now, contrast that with the Landing Page. The landing page is the destination after successful authentication. Once the RADIUS server sends the Access-Accept message and the client device is placed onto the active VLAN with internet routing, the walled garden drops. The controller then redirects the user's browser to the Landing Page.

Why does this distinction matter? Because the Splash Page exists in a highly constrained environment. The device doesn't have full internet access yet. It can only reach the specific IP addresses or hostnames you've whitelisted in your Walled Garden configuration. If you try to load heavy external scripts, dynamic video players, or complex third-party trackers on a splash page without proper whitelisting, the page will break, and the user gets stuck in a connection loop.

The Landing Page, however, sits on the open internet. The user is authenticated. Here, you can load full marketing experiences, dynamic app download links, interactive venue maps, and targeted promotions driven by the first-party data you just captured on the splash page.

[SECTION: IMPLEMENTATION AND PITFALLS]

Now let's talk about implementation and where I see deployments go wrong.

The most common mistake is overloading the Splash Page. I've seen marketing teams hand over a five-megabyte page with four different external tracking pixels and a background video, asking IT to make it the login screen.

When you do that, you have to add dozens of CDNs and third-party domains to your Walled Garden whitelist. Not only is this a nightmare to maintain as those IP ranges change, but it's a security risk. You are poking holes in your pre-authentication firewall. Furthermore, modern mobile operating systems — like iOS and Android — use a specialised mini-browser to render captive portals. These Captive Network Assistants, or CNAs, have limited functionality. They often block cookies, restrict local storage, and will automatically close if they detect external navigation before the internet connection is fully established.

The best practice? Keep the Splash Page lean, fast, and focused purely on data capture and legal consent. Use a cloud-based captive portal solution that optimises the HTML payload for these CNA browsers.

Once the user hits Connect, then redirect them to the rich, dynamic Landing Page. This is where you leverage your WiFi Analytics platform. Because you've already captured their profile, the Landing Page can be personalised. If they are a returning guest at your hotel, the landing page can welcome them by name and offer a one-click booking for the spa. If they are in a retail environment, it can show a heatmap-driven promotion based on their current zone.

[SECTION: CASE STUDIES]

Let me give you two concrete case studies that illustrate this perfectly.

First, a five-hundred-room hotel resort. They were experiencing high drop-off rates on their guest WiFi login. The marketing team had added a four-megabyte promotional video and a complex interactive map to the initial connection screen. The fix was straightforward: replace the connection screen with a lightweight Splash Page under one megabyte, focused solely on room number and last name authentication plus Terms and Conditions acceptance. The video and map were moved to the post-authentication Landing Page. Connection rates improved by over forty percent within the first week.

Second, a retail chain with fifty locations. They wanted to offer seamless WiFi access to returning loyalty members without forcing them to log in every time. The solution was MAC Authentication Bypass integrated with the loyalty database. When a returning device associates with the SSID, the controller queries the RADIUS server, identifies the MAC address, and immediately returns an Access-Accept without presenting the Splash Page. The user is redirected to a personalised Landing Page with their loyalty status and a targeted offer. The result: a thirty percent increase in loyalty app engagement across the estate.

[SECTION: RAPID-FIRE Q&A]

Now, let's move to our Rapid-Fire Q and A. These are the top three questions I get from network engineers.

Question one: Can I bypass the Splash Page entirely for returning users?

Yes. This is called MAC Authentication Bypass, or seamless login. The controller recognises the device's MAC address from a previous session and automatically authorises them, taking them straight to the Landing Page or their original destination. Just ensure your privacy policy covers persistent device tracking.

Question two: Why is my Splash Page showing a certificate error?

This usually happens when you try to intercept HTTPS traffic without a valid SSL certificate on the controller, or if you're using a self-signed certificate. Always use a publicly trusted certificate for your captive portal hostname, and ensure your controller supports modern HTTPS redirection standards like RFC 8908.

Question three: Should the Landing Page be hosted locally on the controller or in the cloud?

Always in the cloud. Hosting on the controller limits your ability to update content dynamically, run A/B tests, or integrate with external CRMs. A cloud-based architecture separates the network control plane from the user experience layer, which is exactly what enterprise deployments require.

[SECTION: SUMMARY AND NEXT STEPS]

To summarise: The Splash Page is the secure, constrained gatekeeper for authentication and consent. Keep it lightweight — under one megabyte, no external dependencies, optimised for the Captive Network Assistant. The Landing Page is the post-authentication destination for engagement, marketing, and ROI generation. It operates on the open internet with full browser capabilities.

Understand the constraints of the Walled Garden and the Captive Network Assistant, and you'll avoid ninety percent of the support tickets associated with guest WiFi deployments.

The three key rules to take away: Splash for Security, Landing for Loyalty. The Walled Garden is a sandbox, not a playground. And always — Authentication before Animation.

Thanks for joining this technical briefing. If you want to dive deeper into configuring cloud-based captive portals, check out the full reference guide on the Purple website. Until next time, keep your networks secure and your users connected.

Key Takeaways

✓The Splash Page is the pre-authentication gatekeeper operating within the restricted Walled Garden — its sole purpose is identity verification and legal consent.
✓The WiFi Landing Page is the post-authentication destination operating on the open internet — its purpose is marketing engagement, personalisation, and ROI generation.
✓The Captive Network Assistant (CNA) renders the Splash Page in a sandboxed mini-browser that blocks cookies, restricts JavaScript, and limits external resource loading.
✓Overloading the Splash Page with marketing assets is the leading cause of guest WiFi connection failures and elevated support ticket volumes.
✓MAC Authentication Bypass (MAB) eliminates the Splash Page for returning devices, redirecting them directly to a personalised Landing Page — improving experience for repeat visitors.
✓A cloud-based captive portal architecture separates the network control plane from the user experience layer, enabling centralised management, dynamic content updates, and CRM integration.
✓Measurable ROI from guest WiFi is generated primarily through the Landing Page — via direct revenue attribution, loyalty engagement, and first-party data capture feeding into WiFi Analytics.

Executive Summary

For enterprise IT teams managing high-density venues — from Hospitality properties to Retail estates — the terms "splash page" and "landing page" are frequently conflated. Treating them as interchangeable in network architecture leads to broken user journeys, security vulnerabilities, and missed data capture opportunities.

At a fundamental level, the Splash Page is the pre-authentication gatekeeper. It exists within the constrained environment of a Walled Garden, responsible for identity verification, MAC authentication, and legal consent under GDPR and PCI DSS. The WiFi Landing Page is the post-authentication destination. It operates on the open internet, leveraging the data captured during login to deliver personalised experiences, drive app downloads, and generate measurable ROI through Guest WiFi integrations.

This guide details the technical specifications, deployment methodologies, and common failure modes associated with captive portal design — enabling network architects to build robust, compliant, and revenue-generating guest access networks across any venue type.

Technical Deep-Dive

The Captive Portal Architecture

A captive portal intercepts HTTP/HTTPS traffic from unauthenticated clients and redirects them to a designated web interface. This mechanism relies on a combination of DNS hijacking, HTTP 302 redirection, and RADIUS authentication — with modern implementations increasingly adopting RFC 8908 (Captive Portal Identification in DHCP and Router Advertisements) to enable native OS-level captive portal discovery without fragile HTTP interception.

Within this architecture, the Splash Page and the Landing Page serve fundamentally different roles at different points in the authentication lifecycle.

1. The Splash Page (Pre-Authentication State)

When a device associates with an SSID, the wireless controller places it in an unauthenticated VLAN. All outbound traffic is intercepted and redirected to the captive portal hostname. The operating system's Captive Network Assistant (CNA) — a specialised, sandboxed pseudo-browser built into iOS, Android, and Windows — detects the captive portal and renders the Splash Page.

Technical Constraints of the CNA Environment:

The CNA is not a full browser. It operates with significant restrictions that directly impact what can be deployed on a Splash Page:

Cookies and local storage are often blocked or severely limited
Complex JavaScript frameworks may fail to execute
External resources (fonts, scripts, images) can only load if their domains are whitelisted in the Walled Garden
The CNA will automatically close if it detects that the device has gained internet access before the user has completed authentication
Session persistence across CNA closure is unreliable

Primary Functions of the Splash Page:

Given these constraints, the Splash Page should be designed exclusively for: authentication (social login via OAuth, SMS OTP, form-based credentials, or loyalty programme integration); Terms and Conditions acceptance; GDPR consent capture; and MAC address registration for future seamless login.

Payload Recommendation: Keep the Splash Page under 1MB. Use inline CSS, avoid external font libraries, and minimise JavaScript. Every external dependency requires a corresponding Walled Garden whitelist entry — each of which represents both a maintenance burden and a potential security exposure.

2. The Landing Page (Post-Authentication State)

Upon successful authentication, the RADIUS server returns an Access-Accept message. The wireless controller updates the client's session, migrating the device to an authenticated VLAN with full internet routing. The Walled Garden is dropped. The controller — or the cloud-based captive portal platform — issues an HTTP 302 redirect to the WiFi Landing Page.

At this point, the device is operating with a full browser and unrestricted internet access. The Landing Page can leverage the complete capability set of modern web development:

Dynamic, personalised content driven by the user profile captured at the Splash Page
Full analytics instrumentation (Google Analytics, custom tracking pixels, CRM webhooks)
Rich media including video, interactive maps, and loyalty dashboards
App download prompts with deep-link routing
Targeted promotions based on WiFi Analytics data, including visit frequency, dwell time, and venue zone

Authentication Flow: End-to-End

The sequence below illustrates the complete flow from SSID association to Landing Page delivery:

Client device associates with the guest SSID
Controller assigns the device to an unauthenticated VLAN
Client attempts an HTTP request; controller intercepts and issues a 302 redirect to the Splash Page
CNA loads the Splash Page (assets served only from Walled Garden-whitelisted domains)
User completes authentication and accepts Terms and Conditions
Captive portal platform sends an Access-Request to the RADIUS server
RADIUS returns Access-Accept; controller receives a Change of Authorization (CoA) message
Controller migrates the client to the authenticated VLAN
Captive portal platform issues a 302 redirect to the WiFi Landing Page
Client browser loads the full Landing Page over the open internet

This clean separation of concerns — authentication on the Splash Page, engagement on the Landing Page — is the architectural foundation of every well-designed guest WiFi deployment.

Implementation Guide

Deploying a scalable, enterprise-grade guest WiFi solution requires separating the network control plane from the user experience layer. The following steps provide a vendor-neutral deployment framework applicable across Cisco Meraki, Aruba, Ruckus, and Ubiquiti infrastructure.

Step 1: Walled Garden Configuration

Configure your Wireless LAN Controller (WLC) to whitelist only the domains and IP ranges strictly required for the Splash Page to function. This typically includes:

The captive portal platform hostname (e.g., portal.purple.ai)
Identity provider domains for social login (e.g., accounts.google.com, graph.facebook.com)
SMS gateway domains if using OTP authentication
Any CDN assets used by the Splash Page itself

Avoid over-whitelisting. Each additional entry increases the attack surface of your pre-authentication network and complicates ongoing maintenance as IP ranges change.

Step 2: SSL Certificate Management

Configure the WLC with a valid, publicly trusted SSL certificate for the captive portal redirection hostname. Self-signed certificates will trigger browser security warnings in the CNA, causing users to abandon the connection process. Certificate expiry is a leading cause of guest WiFi outages — implement automated renewal via Let's Encrypt or your certificate management platform.

Step 3: CNA Optimisation

Design the Splash Page specifically for the CNA environment. Use inline CSS, avoid external JavaScript frameworks, and test across multiple iOS and Android versions. iOS CNA behaviour in particular changes between major OS releases — maintain a regression test matrix covering at least the two most recent major versions of both platforms.

Step 4: Post-Authentication Redirection Logic

Configure post-authentication redirection to support dynamic Landing Page URLs. The RADIUS server can return vendor-specific attributes (VSAs) or the captive portal platform can use the authenticated user profile to construct a personalised URL. This enables segmentation — a first-time visitor receives a welcome offer, while a loyalty member with Gold status receives a personalised dashboard.

Step 5: Analytics Integration

Instrument the Landing Page with your analytics stack. Because the user is now on the open internet with a full browser, standard analytics tools function normally. Integrate with your CRM to create a unified customer profile that combines WiFi session data with purchase history, loyalty status, and marketing engagement metrics.

For a detailed comparison of cloud-based versus on-premise captive portal architectures, see Cloud-Based vs. On-Premise Captive Portal: Which Is Right for Your Business? .

Best Practices

Decouple Authentication and Marketing. The single most impactful architectural decision is to use the Splash Page strictly for secure access and consent, and to move all marketing assets to the Landing Page. This improves connection rates, reduces support tickets, and simplifies compliance audits.

Leverage MAC Authentication Bypass for Returning Users. For returning devices, MAC Authentication Bypass (MAB) eliminates the Splash Page entirely, redirecting users directly to a personalised Landing Page. This dramatically improves the user experience for repeat visitors in Hospitality and Retail environments. Ensure your privacy policy explicitly covers persistent device tracking.

Adopt Cloud-Centric Architectures. Just as the networking industry has moved toward software-defined WAN for centralised management — as detailed in The Core SD WAN Benefits for Modern Businesses — captive portal platforms should be cloud-hosted. This enables centralised management across distributed venue estates, rapid content updates without controller firmware changes, and seamless integration with external CRMs and marketing automation platforms.

Implement RFC 8908 for Modern OS Compatibility. Native captive portal detection via RFC 8908 reduces reliance on HTTP interception, improving reliability across modern iOS and Android versions that increasingly enforce HTTPS-only browsing.

Maintain a Walled Garden Audit Schedule. Review Walled Garden entries quarterly. IP ranges for major identity providers change without notice. Stale entries that no longer resolve create authentication failures; missing entries block legitimate authentication flows.

Troubleshooting & Risk Mitigation

The Connection Loop. If a user authenticates but is repeatedly redirected back to the Splash Page, verify that the RADIUS Access-Accept message is reaching the controller and that the client is successfully receiving a DHCP lease on the authenticated VLAN. Also check that the CoA (Change of Authorization) port (UDP 3799) is not blocked by an intermediate firewall.

CNA Premature Closure. If the CNA closes before the user can authenticate, the device has likely detected internet access prematurely. This can occur if the Walled Garden is over-permissive, inadvertently allowing full internet routing before authentication completes. Review Walled Garden entries for overly broad CIDR ranges.

HTTPS Interception Errors. Modern browsers enforce HTTP Strict Transport Security (HSTS). If a user attempts to navigate to an HSTS-preloaded domain before authenticating, the browser will block the captive portal redirect. Implement RFC 8908 to enable native captive portal discovery, or instruct users to navigate to a non-HSTS domain to trigger the CNA.

Third-Party Script Failures on Splash Page. If marketing teams have added tracking pixels or analytics scripts to the Splash Page, these will fail silently in the CNA environment if their domains are not whitelisted. The correct resolution is to remove these scripts from the Splash Page entirely and redeploy them on the Landing Page, where they will function correctly.

GDPR Compliance Gaps. Ensure that the consent mechanism on the Splash Page meets the requirements of GDPR Article 7 — consent must be freely given, specific, informed, and unambiguous. Pre-ticked consent boxes are non-compliant. Maintain a consent audit log for a minimum of three years.

ROI & Business Impact

A correctly implemented Splash/Landing Page architecture transforms guest WiFi from a cost centre into a measurable revenue-generating asset. The financial case operates across three dimensions.

Data Capture and First-Party Intelligence. By streamlining the Splash Page, venues increase connection rates and the volume of first-party data captured. In Healthcare and Transport environments, this data supports operational analytics — footfall patterns, dwell time by zone, and peak demand forecasting — enabling resource allocation decisions with measurable cost savings.

Direct Revenue Attribution. The Landing Page is the primary conversion surface. A stadium deployment can use the Landing Page to promote in-seat food and beverage ordering, directly correlating network access with transactional revenue. A hotel can offer spa bookings or room upgrades. A retailer can serve zone-specific promotions driven by real-time location data from WiFi Analytics .

Loyalty and Retention. Personalised Landing Page experiences — driven by the user profile captured at the Splash Page — increase loyalty programme engagement. Returning users who receive a personalised welcome experience demonstrate significantly higher session duration and repeat visit frequency compared to users presented with a generic landing page.

The measurable KPIs for a guest WiFi deployment should include: WiFi connection rate (target >70% of venue visitors), data capture rate (target >85% of connected users), Landing Page click-through rate on primary CTA, and direct revenue attributed to WiFi-driven promotions.

Listen to the full technical briefing podcast below:

Key Terms & Definitions

Captive Portal

A web-based access control mechanism that intercepts network traffic from unauthenticated clients and redirects them to an authentication interface before granting broader network access.

The overarching system IT teams deploy to manage guest access, enforce acceptable use policies, capture user consent, and collect first-party data.

Splash Page

The initial authentication interface presented within the captive portal flow, operating within the restricted Walled Garden environment before the user has been granted internet access.

Where network architects must focus on lightweight design, identity verification, and legal consent. Incorrectly overloading this page with marketing assets is the leading cause of guest WiFi connection failures.

WiFi Landing Page

The post-authentication destination page loaded in the user's full browser after the device has been granted internet access by the RADIUS server.

Where marketing and operations teams deploy rich media, personalised content, loyalty integrations, and engagement campaigns. Operates without the constraints of the Walled Garden.

Walled Garden

A restricted network environment that allows unauthenticated users to access only a specific, explicitly whitelisted set of IP addresses or hostnames, blocking all other internet traffic.

The technical boundary within which the Splash Page must operate. Every external resource used by the Splash Page must have its domain or IP range added to the Walled Garden whitelist.

Captive Network Assistant (CNA)

A specialised, sandboxed pseudo-browser built into mobile operating systems (iOS, Android, Windows) that automatically detects and renders captive portal login pages.

The primary reason Splash Pages must be lightweight and avoid complex JavaScript, external cookies, or large media assets. CNA behaviour varies between OS versions and requires ongoing regression testing.

MAC Authentication Bypass (MAB)

A network access control technique that authenticates devices based on their hardware MAC address without requiring user interaction, enabling seamless login for returning devices.

Used to provide frictionless login experiences for returning guests or registered IoT devices. Requires integration between the RADIUS server and the venue's loyalty or device registry database.

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol providing centralised Authentication, Authorisation, and Accounting (AAA) management for network access, defined in RFC 2865.

The backend server infrastructure that validates credentials submitted on the Splash Page, instructs the controller to grant access, and returns user attributes used to personalise the Landing Page.

RFC 8908

The IETF standard defining the Captive Portal API, enabling devices to discover and interact with captive portals natively through DHCP options and Router Advertisements rather than relying on HTTP interception.

A modern standard that improves captive portal reliability across iOS 14+ and Android 11+, reducing CNA-related connection failures caused by HTTPS interception issues.

Change of Authorization (CoA)

A RADIUS extension (RFC 5176) that allows the RADIUS server to dynamically modify an active network session — for example, migrating a client from an unauthenticated to an authenticated VLAN after successful login.

The mechanism by which the captive portal platform instructs the wireless controller to grant internet access after the user completes authentication on the Splash Page.

Case Studies

A 500-room hotel resort is experiencing high drop-off rates on their guest WiFi login. The marketing team recently added a 4MB promotional video and a complex interactive venue map to the initial connection screen. Connection rates have dropped from 68% to 31% since the update. How should the network architect resolve this?

The architect must decouple the authentication and marketing functions. Step 1: Replace the current connection screen with a lightweight Splash Page under 1MB, containing only the authentication form (room number and last name), a GDPR-compliant consent checkbox, and Terms and Conditions acceptance. Step 2: Remove all external script dependencies from the Splash Page and serve all assets from the captive portal platform's own CDN, which is already whitelisted in the Walled Garden. Step 3: Configure the wireless controller's post-authentication redirection to send the user to a newly created Landing Page hosted on the open internet. Step 4: Move the 4MB promotional video and interactive venue map to this Landing Page. Step 5: Instrument the Landing Page with the hotel's CRM integration to personalise the welcome message based on the authenticated user profile. Step 6: Implement MAC Authentication Bypass for returning guests to eliminate the Splash Page entirely on subsequent visits.

Implementation Notes: This approach resolves the drop-off issue by acknowledging the fundamental constraints of the Captive Network Assistant (CNA). The heavy assets were causing the CNA to time out or fail to render within the restricted Walled Garden environment. Moving them to the post-authentication Landing Page ensures they load correctly using the device's full browser capabilities over an established internet connection. The MAB implementation for returning guests further improves the experience for the hotel's most valuable repeat customers, while the CRM integration on the Landing Page creates a measurable revenue attribution pathway.

A retail chain wants to offer seamless WiFi access to returning loyalty programme members across 50 locations, bypassing the login screen while still displaying a personalised welcome offer and current loyalty points balance. What is the recommended technical architecture?

Implement MAC Authentication Bypass (MAB) integrated with the loyalty database via RADIUS. Architecture: (1) When a returning device associates with the SSID, the controller sends a RADIUS Access-Request containing the device MAC address. (2) The RADIUS server queries the loyalty database to match the MAC address to a loyalty profile. (3) If a match is found, the RADIUS server returns an Access-Accept with a vendor-specific attribute (VSA) containing a signed user token. (4) The controller grants immediate internet access and issues a redirect to the Landing Page URL, appending the signed token as a query parameter. (5) The cloud-hosted Landing Page decodes the token, queries the loyalty API for the user's current points balance and personalised offer, and renders a customised welcome experience. For new users or unrecognised devices, the standard Splash Page flow is presented, with an option to link the device to their loyalty account for future seamless access.

Implementation Notes: This solution correctly utilises MAB for network access control while leveraging the Landing Page for the marketing requirement. The signed token approach prevents URL manipulation and ensures the personalised content is served only to the authenticated user. The fallback to the standard Splash Page for unrecognised devices ensures that new customer acquisition is not compromised. This architecture demonstrates a mature understanding of decoupled captive portal design and is directly applicable to enterprise retail deployments across distributed venue estates.

Scenario Analysis

Q1. A public sector organisation requires all guest WiFi users to accept a lengthy Acceptable Use Policy (AUP) before accessing the internet. The communications team also wants to display a dynamic feed of upcoming community events and a live social media wall. How should you architect this requirement across the captive portal flow?

💡 Hint:Consider the constraints of the Captive Network Assistant (CNA) and the Walled Garden when deciding where to place each content element.

Show Recommended Approach

Place the Acceptable Use Policy (AUP) on the Splash Page to ensure legal compliance before authentication. The AUP should be presented as inline text or a scrollable div — not loaded from an external URL — to avoid Walled Garden dependencies. Once the user accepts the AUP and is authenticated, redirect them to the Landing Page to display the dynamic community events feed and social media wall. The social media wall in particular requires external API calls that cannot function within the Walled Garden, making the Landing Page the only viable location.

Q2. During a new deployment at a conference centre, users report that the login screen appears correctly but when they click 'Sign in with LinkedIn', the page times out and returns an error. The controller configuration and RADIUS server are both functioning correctly for email/password authentication. What is the most likely cause and resolution?

💡 Hint:Think about what network access is required for a third-party OAuth identity provider to complete its authorisation flow during the pre-authentication phase.

Show Recommended Approach

The Walled Garden configuration is incomplete. LinkedIn's OAuth flow requires the client device to communicate with LinkedIn's authorisation servers (e.g., www.linkedin.com, api.linkedin.com) during the pre-authentication phase. These domains are not whitelisted, so the OAuth redirect fails. The resolution is to identify all IP ranges and hostnames used by LinkedIn's OAuth API and add them to the Walled Garden whitelist on the wireless controller. Note that LinkedIn (and other major identity providers) may use multiple CDN-hosted domains — review the OAuth documentation or use a packet capture to identify all required endpoints.

Q3. A retail client wants to track user behaviour on the initial WiFi login screen using Google Analytics 4 and a custom retargeting pixel from their advertising platform. The marketing team has provided a tag manager snippet to be added to the Splash Page. Why is this technically problematic, and what is the recommended alternative that preserves the marketing team's measurement requirements?

💡 Hint:Evaluate the capabilities of the CNA mini-browser and the implications of adding external script domains to the Walled Garden.

Show Recommended Approach

This is problematic for two reasons. First, the CNA often blocks cookies and restricts JavaScript execution, rendering client-side tracking scripts ineffective or unreliable. Second, Google Tag Manager and advertising pixels load scripts from multiple external domains — adding all of these to the Walled Garden creates significant security exposure and ongoing maintenance overhead. The recommended alternative is a two-part approach: (1) Capture the authentication event server-side via the captive portal platform's API or RADIUS accounting logs, and push this event to Google Analytics 4 using the Measurement Protocol (server-side), which does not require client-side JavaScript. (2) Deploy the full Google Tag Manager container and retargeting pixel on the post-authentication Landing Page, where the full browser environment ensures reliable script execution and cookie-based tracking functions normally.