Purple vs Cloud4Wi: Captive Portal and WiFi Marketing Compared

This technical reference guide provides a direct, side-by-side comparison of Purple and Cloud4Wi for enterprise captive portal and WiFi marketing deployments. It covers feature parity, pricing model differences, architectural considerations, integration breadth, and compliance requirements to help IT managers, network architects, and CTOs make an informed shortlist decision. The guide includes real-world implementation scenarios from hospitality and retail, a full Mermaid architecture diagram, and a 10-minute executive briefing podcast.

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

🎧 Listen to this Guide

View Transcript

Welcome to the Enterprise Network Briefing. Today we're tackling a decision that sits right at the intersection of IT infrastructure and marketing strategy: choosing the right captive portal and guest WiFi analytics platform. Specifically, we are doing a deep-dive comparison of two major players: Purple and Cloud4Wi. If you're a CTO, a network architect, or an operations director evaluating these platforms for your venues — whether that's a retail chain, a hotel group, or a large stadium — this briefing is for you. We're cutting through the marketing material to look at feature parity, architectural differences, and, crucially, how their pricing models dictate their deployment speed. Let's get into it.

First, let's establish the baseline. Both Purple and Cloud4Wi are enterprise-grade, cloud-based overlays. They are hardware-agnostic. Whether you're running Cisco Meraki, Aruba, Fortinet, or Ruckus, both platforms will integrate with your existing wireless LAN controllers via RADIUS and API connections. You don't need to rip and replace your access points. Both provide highly customisable captive portals, supporting multiple languages, social logins, and compliance with frameworks like GDPR and CCPA. So, where do they diverge? It comes down to their core philosophy and commercial models.

Let's talk about Purple first. Purple's strategy is built on market disruption through rapid deployment and transparent pricing. Their foundational tier, called Connect, is entirely free. It gives you a secure captive portal, branded splash pages, network analytics, and compliance. This is a massive advantage for IT teams that need to stand up a compliant guest network quickly without fighting through a six-month enterprise procurement cycle. Once deployed, venues can upgrade to the Capture or Engage tiers to unlock deep CRM integrations — Purple boasts over four hundred native connectors — and built-in marketing automation. Purple's focus is on turning anonymous footfall into actionable, first-party data as quickly and efficiently as possible. Furthermore, Purple acts as a free identity provider for OpenRoaming, which is a significant step toward seamless, secure connectivity across federated networks.

Now, let's look at Cloud4Wi. Cloud4Wi operates on a much more traditional enterprise software model. There is no free tier, and there is no transparent pricing on their website. Every deployment requires a custom quote and engagement with their sales team. This model reflects their focus on complex, highly customised deployments. Where Cloud4Wi really stakes its claim is in Real-Time Location Services, or RTLS. While Purple provides excellent footfall and dwell time analytics, Cloud4Wi's architecture is deeply integrated with granular location tracking. If your primary use case involves highly precise indoor positioning to optimise physical floor plans or trigger hyper-localised experiences, Cloud4Wi offers a very robust, albeit complex, solution. Their platform is trusted by over one hundred and fifty million users across seventy thousand enterprise locations in one hundred and fifty countries, which demonstrates their scale and enterprise credibility.

Now let's get into the technical architecture. Both platforms intercept a user's initial HTTP request when they connect to an open SSID, redirecting them to the captive portal splash page. This is achieved through a combination of DNS redirection and RADIUS-based access control on the wireless LAN controller. The key configuration requirement on your side is the Walled Garden. This is the set of domains and IP addresses that a device can access before authentication is complete. You need to ensure that all resources required by the portal — including social login APIs, CSS frameworks, and any Passpoint profile servers — are allowlisted in your Walled Garden configuration. Getting this wrong is the single most common cause of portal rendering failures.

Authentication methods are broadly comparable between the two platforms. Both support social login via providers like Facebook and LinkedIn, custom registration forms with configurable fields, and one-time passcodes via SMS or email. Both platforms also support Passpoint, also known as Hotspot 2.0, which is the IEEE 802.11u standard for seamless WiFi onboarding. Passpoint is critical for enterprise deployments because it transitions users from the initial captive portal interaction to a certificate-based, WPA2 or WPA3-Enterprise encrypted connection. This means that on all subsequent visits, the device connects automatically and securely without requiring the user to interact with the portal again.

This brings us to one of the most important technical challenges in the space: MAC address randomisation. Since iOS 14 and Android 11, smartphones generate a random MAC address for each network they connect to. This is a privacy feature, but it completely undermines MAC-based analytics and loyalty tracking. If your guest WiFi strategy relies on recognising returning visitors by their device's hardware address, you are already working with unreliable data. The solution is Passpoint. By using certificate-based identity rather than MAC addresses, you can accurately identify returning visitors regardless of their device's privacy settings. Both Purple and Cloud4Wi support this, but it requires deliberate configuration and user prompting during the initial portal interaction.

Let's talk about the integration ecosystem, because this is where the day-to-day operational impact is felt most acutely. Purple's four hundred plus native connectors cover virtually every major CRM, marketing automation platform, and loyalty system. Salesforce, HubSpot, Microsoft Dynamics, Mailchimp, ActiveCampaign — they're all there. This means that captured first-party data flows directly into your existing marketing stack without requiring custom development. For organisations that have already invested in a marketing technology stack, this is a significant operational advantage.

Cloud4Wi's integration story is more focused on enterprise-grade systems and their own platform ecosystem. They have strong integrations with Cisco infrastructure, which is unsurprising given their partnership history. For organisations running large Cisco deployments, this tight integration can simplify the overall architecture. However, the breadth of out-of-the-box connectors is narrower than Purple's offering.

Now let's move to implementation recommendations. When deploying either platform, start with a thorough network audit. Document your SSID architecture, VLAN segmentation, and RADIUS server configuration before touching the captive portal platform. Guest traffic must be completely isolated from corporate traffic at the VLAN level. This is not just a security best practice — it's a compliance requirement under PCI DSS if your venue processes card payments anywhere on the same physical network.

For the captive portal user journey, keep it simple. Every additional field you add to a registration form reduces your completion rate. A name and email address is the minimum viable data set for most marketing use cases. Use progressive profiling — capture the basics at first login, then use follow-up surveys or portal prompts on subsequent visits to enrich the profile. Purple's Surveys add-on is particularly useful here, achieving a ninety-seven percent average response rate according to their published data.

Now let's do a rapid-fire section on common scenarios. Scenario one: You have two hundred retail stores and need to start capturing customer emails for a new loyalty programme by next month. Which platform? Purple. The transparent pricing and ability to instantly deploy the Connect tier, then upgrade to Capture, fits the aggressive timeline perfectly. Cloud4Wi's enterprise sales cycle would likely miss the deadline.

Scenario two: You are managing a large international airport and need granular, real-time tracking of passenger flow to optimise security queue staffing. Budget is secured. Which platform? Cloud4Wi. Their deep RTLS capabilities are designed exactly for this type of complex, location-centric enterprise requirement.

Scenario three: A hotel group needs a guest WiFi solution that integrates with their existing Salesforce CRM and sends automated post-stay satisfaction surveys. Which platform? Purple. The native Salesforce connector and Surveys add-on make this a straightforward deployment with no custom development required.

Finally, let's talk about migration. If you're currently on one platform and considering switching, the key data to export is your authenticated user database — specifically email addresses and consent records. Both platforms can import existing user databases, but you must ensure that the consent records are portable and that the import process maintains the original consent timestamp and scope. Failing to do this correctly could result in a GDPR compliance breach, as you would be processing data without a valid legal basis.

To summarise the key takeaways from this briefing. First, Purple offers a disruptive, transparent pricing model starting with a robust free Connect tier, while Cloud4Wi relies on custom enterprise quoting. Second, both platforms are hardware-agnostic and integrate via RADIUS, but Purple excels in rapid deployment and built-in marketing automation. Third, Cloud4Wi provides deep Real-Time Location Services capabilities, suited for complex, location-centric enterprise deployments. Fourth, Purple features over four hundred native connectors, simplifying the process of piping first-party data into existing CRM and marketing stacks. Fifth, implementing Passpoint is critical for both platforms to mitigate the analytics disruption caused by MAC randomisation on modern smartphones. And sixth, always ensure your Walled Garden configuration is complete before going live — it is the most common cause of portal failures.

That's it for today's briefing. If you're at the shortlist stage evaluating these two platforms, the decision framework is straightforward: Purple for speed, transparency, and marketing automation; Cloud4Wi for deep location intelligence and complex enterprise customisation. Thanks for listening, and we'll see you on the next one.

Key Takeaways

✓Purple offers a disruptive, transparent pricing model starting with a robust free 'Connect' tier, while Cloud4Wi relies on traditional, custom enterprise quoting with no self-service option.
✓Both platforms are hardware-agnostic and integrate via RADIUS, but Purple excels in rapid deployment, built-in marketing automation, and a 400+ connector integration ecosystem.
✓Cloud4Wi provides deep Real-Time Location Services (RTLS) capabilities, making it the stronger choice for complex, location-centric enterprise deployments such as airports and large stadiums.
✓Implementing Passpoint (Hotspot 2.0) is critical for both platforms to mitigate the analytics disruption caused by MAC address randomisation on modern iOS and Android devices.
✓Purple acts as a free identity provider for OpenRoaming under its Connect licence, enabling seamless, secure connectivity for users across participating venues globally.
✓An incomplete Walled Garden configuration on the wireless LAN controller is the single most common cause of captive portal rendering failures — verify this before going live.
✓For organisations at the shortlist stage: choose Purple for speed, transparency, and marketing ROI; choose Cloud4Wi for deep location intelligence and complex enterprise customisation.

Executive Summary

When evaluating enterprise guest WiFi platforms, IT leaders and network architects are often forced to choose between complex, rigid systems and lightweight tools that fail to scale. Both Purple and Cloud4Wi have emerged as dominant players in the captive portal and WiFi analytics space, but they approach the market with fundamentally different philosophies. Purple drives market disruption through its free "Connect" tier and transparent pricing, functioning as a free identity provider for services like OpenRoaming, while delivering a robust Guest WiFi marketing and analytics engine. Cloud4Wi, conversely, maintains a traditional enterprise sales model with a heavy emphasis on Real-Time Location Services (RTLS) and custom deployments.

This guide provides a direct, technical comparison of Purple vs Cloud4Wi. We dissect captive portal capabilities, integration ecosystems, compliance frameworks, and pricing models. For CTOs and venue operations directors managing Retail , Hospitality , or large public venues, the decision hinges on whether your priority is rapid deployment with built-in marketing automation (Purple) or highly customised, location-centric enterprise deployments (Cloud4Wi).

Technical Deep-Dive: Architecture and Core Capabilities

Both platforms operate as hardware-agnostic, cloud-based overlays that integrate with your existing wireless infrastructure — Cisco, Fortinet, Aruba, Ruckus — via RADIUS and API connections. No access point replacement is required. However, their feature sets diverge significantly when examining the captive portal experience and downstream data handling.

Captive Portal and Authentication

The captive portal is the critical ingestion point for first-party data. Purple offers a highly customisable portal supporting over 25 languages with automatic device detection. It provides diverse authentication methods, including social login (Facebook, X, LinkedIn), custom forms, click-to-connect, and seamless Passpoint integration. Crucially, Purple's profile-based authentication supports a network of over 440 million users worldwide, enabling frictionless roaming across participating venues without repeated portal interactions.

Cloud4Wi also delivers robust captive portal customisation, supporting multiple login options including OTPs and enterprise SSO. They similarly emphasise Passpoint onboarding to transition users from open networks to secure, encrypted connections. While both platforms achieve parity in basic captive portal functionality, Purple's built-in marketing automation and transparent data capture workflows provide a more immediate path to ROI for marketing teams.

Analytics and Data Integration

Data utility is where the platforms differentiate most clearly. Purple's WiFi Analytics platform is engineered to turn anonymous footfall into actionable CRM data. With over 400 native connectors, Purple seamlessly pushes captured data into platforms like Salesforce, HubSpot, and Microsoft Dynamics. The "Engage" tier includes built-in marketing automation, allowing venues to trigger personalised communications based on dwell time, visit frequency, and demographic profiles.

Cloud4Wi positions itself strongly in the Real-Time Location Services (RTLS) space. While Purple provides excellent footfall and dwell time analytics, Cloud4Wi's architecture is deeply integrated with location tracking, offering granular visibility into visitor movement patterns. For environments requiring precise Indoor Positioning System capabilities — such as large airports or multi-floor retail centres — Cloud4Wi offers a compelling, albeit complex, solution.

Pricing Models: Disruption vs Traditional Enterprise

The most stark contrast between Purple and Cloud4Wi lies in their commercial strategies.

Purple employs a transparent, tiered pricing model designed to reduce friction and accelerate deployment. The foundational tier, "Connect," is entirely free, providing a secure captive portal, branded splash pages, network analytics, and GDPR compliance. This tier effectively commoditises basic guest WiFi, allowing IT teams to deploy a compliant solution immediately without a procurement cycle. Organisations can then upgrade to the "Capture" or "Engage" tiers for advanced CRM integration, behavioural insights, and marketing automation.

Cloud4Wi operates on a traditional enterprise software model. Pricing is entirely custom, requiring engagement with their sales team for a quote. There is no free tier or self-service signup. This approach aligns with their focus on complex, large-scale deployments but presents a significant barrier to entry for organisations seeking rapid proof-of-concept deployments or transparent cost forecasting.

Dimension	Purple	Cloud4Wi
Pricing Model	Transparent tiers; free entry tier	Custom enterprise quote
Free Tier	Yes (Connect)	No
Self-Service Signup	Yes	Demo required
Marketing Automation	Built-in (Engage plan)	Via third-party integrations
CRM Connectors	400+ native	Select enterprise
RTLS / Location Services	Analytics-focused	Full RTLS engine
Passpoint Support	Yes (Engage plan)	Yes (native)
OpenRoaming	Yes (free identity provider)	Yes
Hardware Agnostic	Yes	Yes
GDPR / CCPA Compliance	Yes	Yes
AI Assistant	No	Yes (Hedy)
Content Filtering	Yes (Shield add-on)	No

Implementation Guide

Deploying an enterprise captive portal requires careful coordination between network engineering and marketing teams. Regardless of the chosen platform, the following steps ensure a secure, compliant, and high-performing deployment.

Step 1 — Network Audit and Segmentation. Document your SSID architecture, VLAN segmentation, and RADIUS server configuration before touching the captive portal platform. Guest traffic must be completely isolated from corporate traffic at the VLAN level. This is not merely a security best practice; it is a compliance requirement under PCI DSS if your venue processes card payments on the same physical network.

Step 2 — Walled Garden Configuration. The Walled Garden defines the domains and IP ranges a device can access before authentication is complete. Ensure all resources required by the portal — social login APIs, CSS frameworks, Passpoint profile servers, and the portal's own domain — are allowlisted on your wireless LAN controller. An incomplete Walled Garden is the single most common cause of captive portal rendering failures.

Step 3 — Compliance and Consent Design. Capturing first-party data introduces obligations under GDPR, CCPA, and regional privacy frameworks. Ensure the captive portal explicitly requests consent for data processing and marketing communications before authentication. Avoid pre-ticked consent boxes. Both Purple and Cloud4Wi provide native consent management, but the specific opt-in language and granularity must be configured by your legal team.

Step 4 — Passpoint Transition. Use the initial captive portal login to prompt users to download a Passpoint profile. On all future visits, their device will authenticate automatically using WPA2/WPA3-Enterprise encryption, bypassing the portal entirely. This is the definitive mitigation for MAC address randomisation issues and significantly improves the returning visitor experience.

Step 5 — CRM Integration and Data Flow Testing. Before going live, validate the end-to-end data flow from portal registration to CRM record creation. Test edge cases including duplicate email handling, consent flag propagation, and field mapping. Purple's 400+ native connectors simplify this step considerably compared to custom API integrations.

Best Practices

Several industry-standard practices apply regardless of platform selection. First, minimise registration form fields. Every additional required field measurably reduces completion rates; a name and email address is the minimum viable data set for most marketing use cases. Use progressive profiling to enrich records over subsequent visits rather than front-loading the registration experience.

Second, implement network monitoring for RADIUS latency. High latency between the wireless LAN controller and cloud RADIUS servers causes authentication timeouts and poor user experience. Monitor RADIUS response times and consider redundant RADIUS configurations if your hardware supports it.

Third, align your WiFi infrastructure standards with your platform choice. If you are evaluating Wi-Fi 6E vs Wi-Fi 7 for a new deployment, ensure your chosen captive portal platform is tested and certified against the hardware you are deploying. Both Purple and Cloud4Wi are hardware-agnostic, but dense, high-throughput environments require careful RF planning to ensure the portal experience is not degraded by network congestion.

Troubleshooting & Risk Mitigation

Even with robust platforms, captive portal deployments encounter predictable failure modes. Understanding them in advance significantly reduces mean time to resolution.

Portal Not Rendering. Most commonly caused by an incomplete Walled Garden. Review the vendor's documentation and ensure all required domains are allowlisted. Check for overly aggressive firewall rules that may be blocking HTTP redirects used to trigger the portal.

Authentication Timeouts. Typically caused by high latency or packet loss between the WLC and the cloud RADIUS endpoint. Monitor RADIUS response times and check for network path issues between your site and the vendor's cloud infrastructure.

MAC Randomisation Disconnects. Modern smartphones rotate MAC addresses, breaking session persistence and forcing repeated portal interactions. The strategic mitigation is deploying Passpoint, which uses certificate-based identity rather than MAC addresses.

Data Not Appearing in CRM. Usually caused by misconfigured field mappings or API authentication failures. Verify OAuth tokens and API keys have not expired, and check the integration's error logs in both the WiFi platform dashboard and the CRM.

GDPR Consent Audit Failures. Ensure the platform is storing consent timestamps, consent scope, and the specific portal version shown at the time of consent. Both Purple and Cloud4Wi provide consent audit logs, but these must be configured and retained in line with your data retention policy.

ROI & Business Impact

The ultimate measure of a captive portal platform is its ability to generate measurable business value. Purple's approach focuses on rapid time-to-value through its Free Connect tier and built-in marketing automation. Venues in Healthcare or Transport can quickly establish a compliant network and begin capturing data to drive loyalty programmes or retail media monetisation. Purple reports an average ROI of 873% across its customer base, driven primarily by first-party data capture and automated marketing campaigns.

Cloud4Wi's value proposition is tied to deep location analytics and complex enterprise integrations. Their Guess retail deployment demonstrates the scale of potential: 35,000 opted-in contacts captured per month and over one million real-time location "moments" revealed annually. While the initial investment and deployment time are higher, organisations that require granular RTLS data to optimise floor plans or trigger highly localised experiences may find the investment justified.

For organisations evaluating the Internet of Things Architecture implications of their WiFi deployment — particularly those integrating WiFi analytics with broader sensor networks — Cloud4Wi's RTLS capabilities provide a richer data layer. Purple, however, remains the stronger choice for organisations prioritising marketing ROI, integration breadth, and deployment speed.

Key Terms & Definitions

Captive Portal

A web page that intercepts a user's web browser when attempting to connect to a public WiFi network, requiring interaction — authentication, payment, or accepting terms — before granting internet access.

The primary mechanism for capturing first-party data and ensuring legal compliance on guest networks. Both Purple and Cloud4Wi use captive portals as the entry point for their data capture and analytics pipelines.

Passpoint (Hotspot 2.0)

An industry standard (IEEE 802.11u) that streamlines network access, allowing devices to automatically and securely connect to WiFi networks using enterprise-grade WPA2/WPA3 encryption without requiring manual captive portal logins after the initial profile installation.

Essential for providing a cellular-like roaming experience and mitigating the impact of MAC address randomisation on analytics. Both Purple and Cloud4Wi support Passpoint, but it requires deliberate configuration.

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol that provides centralised Authentication, Authorisation, and Accounting (AAA) management for users who connect and use a network service.

The core protocol used by both Purple and Cloud4Wi to communicate with the venue's wireless infrastructure to grant or deny internet access following captive portal authentication.

Walled Garden

A limited network environment that controls access to web content and services. In WiFi deployments, it refers to the specific IP addresses or domains a device can access before completing captive portal authentication.

IT teams must configure Walled Gardens correctly on their wireless LAN controllers to ensure the captive portal page, social login APIs, and Passpoint profile servers are accessible pre-authentication.

Real-Time Location Services (RTLS)

Technologies used to automatically identify and track the location of objects or people in real time, usually within a building or contained area, using WiFi signal triangulation, BLE beacons, or UWB.

A key differentiator for Cloud4Wi, requiring dense AP placement and specific network configurations to achieve high accuracy. Purple provides footfall and dwell time analytics but does not offer full RTLS.

First-Party Data

Information a company collects directly from its customers and owns outright, rather than purchasing from a third party or inferring from third-party cookies.

The primary ROI driver for marketing teams using platforms like Purple to capture emails, demographics, and behavioural data via the captive portal, particularly valuable in the post-third-party-cookie era.

MAC Randomisation

A privacy feature in modern operating systems (iOS 14+, Android 11+) that generates a random Media Access Control (MAC) address when connecting to WiFi networks, preventing long-term device tracking.

Forces IT teams to move away from MAC-based authentication and analytics toward identity-based solutions like Passpoint. Ignoring this renders loyalty analytics unreliable.

OpenRoaming

A WBA (Wireless Broadband Alliance) federation of WiFi networks that allows users to automatically connect securely across different venues without needing to register or log in repeatedly, using Passpoint as the underlying technology.

Purple acts as a free identity provider for OpenRoaming under its Connect licence, enabling seamless connectivity for users across participating venues globally.

PPSK (Private Pre-Shared Key)

A WiFi security mechanism that assigns a unique pre-shared key to each user or device, providing WPA2-level encryption without requiring a RADIUS server for every authentication event.

Supported by Cloud4Wi for device-level authentication in IoT and BYOD scenarios. Useful in environments where Passpoint is not feasible.

Case Studies

A 500-location retail chain needs to deploy a compliant guest WiFi solution across all stores within 30 days to support a new loyalty app launch. They have existing Cisco Meraki infrastructure but a limited IT budget for the current quarter.

Deploy Purple's 'Connect' tier immediately. Because Purple is hardware-agnostic and integrates natively with Meraki via RADIUS, the deployment requires no new hardware procurement. The Free Connect tier provides the necessary branded captive portal and GDPR compliance framework at zero software cost. The IT team can complete the configuration centrally via Purple's cloud dashboard and push the configuration to all 500 sites without on-site visits. Once the loyalty app is launched and budget is secured in the next quarter, the organisation can upgrade to the 'Capture' tier via a simple license change to begin piping first-party data directly into their CRM.

Implementation Notes: This scenario highlights Purple's disruptive pricing model. Cloud4Wi would require a lengthy enterprise sales cycle and significant upfront investment, making a 30-day deployment across 500 sites operationally challenging. Purple's self-service, free-tier approach allows IT to solve the immediate connectivity and compliance requirement while providing a seamless upgrade path for the marketing team's data needs. The key risk to mitigate is ensuring the Walled Garden configuration is correctly templated before mass deployment.

A large stadium with 60,000 capacity requires granular tracking of attendee movement to optimise concession stand staffing and manage crowd flow during halftime. They have a high-density Aruba network deployed and a significant capital budget.

In this specific scenario, Cloud4Wi's deep focus on Real-Time Location Services (RTLS) makes it the stronger candidate. The platform must be integrated with the Aruba analytics engine to process location data at the required granularity. The IT team must configure the network to support high-frequency location updates and ensure the captive portal clearly communicates the extent of location tracking to comply with privacy regulations. A phased rollout — starting with a single stand or section — is recommended to validate location accuracy before full deployment.

Implementation Notes: While Purple provides excellent footfall and dwell time metrics, Cloud4Wi's architecture is heavily optimised for complex RTLS use cases requiring sub-metre accuracy. The stadium must weigh the significant cost of the Cloud4Wi enterprise license against the operational savings generated by optimised staffing and reduced queue times. The privacy communication on the captive portal is critical: attendees must be clearly informed that their location is being tracked, and this consent must be captured and stored in compliance with GDPR.

Scenario Analysis

Q1. A hospital IT director needs to implement a guest WiFi portal that strictly complies with GDPR and HIPAA, while also allowing the marketing team to collect optional feedback surveys. They want to avoid a lengthy procurement process. Which platform architecture best suits this requirement, and what specific configuration steps are required?

💡 Hint:Consider the procurement cycle, the availability of specific add-on features for feedback collection, and the compliance requirements for healthcare environments.

Show Recommended Approach

Purple is the recommended choice. The hospital can immediately deploy the 'Connect' tier to establish a GDPR-compliant captive portal without a lengthy enterprise procurement cycle. They can then add Purple's 'Surveys' add-on to collect the required feedback. The IT team must configure the consent management carefully to separate WiFi access consent from marketing communications consent, ensuring HIPAA-relevant data is not captured through the portal. Network segmentation must isolate guest WiFi from clinical systems.

Q2. Your network engineering team reports high drop-off rates on the captive portal splash page before users authenticate. The portal is deployed on a Fortinet FortiGate controller integrated with Cloud4Wi. What is the most likely architectural cause, and what is the remediation process?

💡 Hint:Think about what network configurations are required for a device to load external resources before authentication is complete, and which specific Fortinet configuration may be involved.

Show Recommended Approach

The most likely cause is an incomplete Walled Garden configuration on the FortiGate. If the portal relies on external resources — such as Cloud4Wi's CDN for CSS and JavaScript, or social login APIs — that are not allowlisted, the page will fail to render correctly. The remediation process is to review Cloud4Wi's Fortinet integration documentation, extract the full list of required domains and IP ranges, and add them to the FortiGate's exempt list for pre-authentication traffic. After updating, clear the browser cache on a test device and re-test the portal flow.

Q3. The marketing team at a shopping mall wants to track returning visitors to measure loyalty, but the IT team notes that MAC randomisation on iOS 14+ and Android 11+ makes this data unreliable. The current deployment uses Purple's Capture tier. What technology should be implemented, and what does the user journey look like after implementation?

💡 Hint:What standard replaces MAC address tracking with secure, certificate-based authentication, and which Purple pricing tier enables it?

Show Recommended Approach

The venue should upgrade to Purple's 'Engage' tier to unlock Passpoint and profile authentication. By prompting users to download a Passpoint profile during their initial captive portal interaction, subsequent visits will automatically authenticate using WPA2/WPA3-Enterprise encryption and certificate identity, entirely bypassing the MAC randomisation issue. The user journey becomes: first visit — portal interaction and Passpoint profile download; all subsequent visits — automatic, secure connection with no portal interaction. This provides accurate, persistent identity for loyalty analytics.