Ubiquiti UniFi e Purple WiFi: Guia de Integração

This guide provides a definitive technical reference for integrating the Purple WiFi intelligence platform with Ubiquiti UniFi network deployments, covering architecture, step-by-step controller configuration, and GDPR-compliant data capture. It is designed for IT managers, network architects, and operations directors who need to deploy a secure, feature-rich guest WiFi experience across hospitality, retail, events, and public-sector environments. By correctly configuring the UniFi Network Controller to leverage Purple's external captive portal, organisations can transform a standard cost centre into a valuable source of visitor analytics and marketing intelligence.

📖 8 min de leitura📝 1,793 palavras🔧 2 exemplos❓ 4 perguntas📚 10 termos-chave

🎧 Ouça este Guia

Ver Transcrição

Welcome to the Purple Technical Briefing. I'm your host, and in the next ten minutes, we'll be providing a senior-level guide to integrating Purple's WiFi intelligence platform with Ubiquiti UniFi networks. This is for the IT managers, network architects, and operations directors who need actionable guidance to deploy a world-class guest WiFi solution. We'll cover the core architecture, a step-by-step implementation plan, and the common pitfalls to avoid.

So, let's set the context. You have a UniFi network — it's powerful, it's scalable, but its native guest portal capabilities are basic. Your organisation needs more than just a password; it needs intelligence. You want to understand visitor behaviour, capture data for marketing in a GDPR-compliant way, and provide a seamless, branded user experience. This is the problem that the Purple integration solves. It transforms your UniFi infrastructure from a simple internet provider into a rich source of business intelligence.

The core of this integration lies in UniFi's External Portal Server feature. When a guest connects, the UniFi controller doesn't handle the login itself. Instead, it redirects the user to the Purple cloud platform, which takes over the entire authentication journey. After the user logs in via a social account, a form, or a voucher, Purple makes a secure API call back to your UniFi controller to say: 'This user is authenticated, grant them access.' It's a simple, robust, and highly effective architecture.

Now for the technical deep-dive. Let's walk through the five key steps for a successful deployment. I'll keep this concise.

Step one: Controller Accessibility. Your UniFi controller must be reachable by Purple's cloud platform. This means you need a static public IP or hostname, and you must configure a port forward rule on your firewall. It's TCP port 8443 for software controllers and port 443 for hardware like the UDM Pro or Cloud Key Gen2.

Step two: The Guest SSID. Inside your UniFi Network Application, you'll create a new wireless network. The crucial setting here is that the security protocol must be Open. This is non-negotiable. It's this open state that allows the captive portal redirect to happen. Don't worry — the security is handled by the portal and network segmentation, not by a pre-shared key.

Step three: The Hotspot Portal. This is where you tell UniFi to use Purple. You'll enable the Hotspot Portal and set the authentication type to External Portal Server. You will then input the specific IP address and access domain provided by Purple. A key mistake to avoid here is enabling HTTPS redirection. Purple manages the security, so this should be disabled.

Step four: The Walled Garden. This is the most critical and often misunderstood part of the configuration. The Walled Garden is your pre-authentication whitelist. You must add all of Purple's domains, plus the domains for any social login providers you want to offer, such as facebook.com. If this list is incomplete, the portal simply will not load for your guests. It's the first place to check when troubleshooting.

Step five: The Purple Portal. Finally, you log in to your Purple account. In your venue settings, you'll enter the public address of your UniFi controller and, very importantly, the credentials for a dedicated local administrator account — not your Ubiquiti cloud account. This is what allows Purple to make that vital API call to authorise the guest.

Follow those five steps, and you have a robust, enterprise-grade guest WiFi solution.

Let's talk about implementation recommendations and pitfalls. Best practice number one: network segmentation. Your guest SSID must be on its own VLAN, completely isolated from your corporate network. This is non-negotiable for security and PCI DSS compliance. Second, use bandwidth throttling. UniFi allows you to set per-user rate limits. Use them to ensure a fair experience for everyone. Third, as I mentioned, use a dedicated local admin account for the API. It limits your security exposure.

The most common pitfall we see is a failed redirect — the portal doesn't load. Nine times out of ten, this is an incomplete Walled Garden. The second most common issue is a successful login, but no internet access. This points directly to a communication failure between Purple and your controller. Check your port forwarding rules and the admin credentials in the Purple portal.

Time for a rapid-fire Q&A. I'm often asked: Can I do this with a UDM Pro? Yes, absolutely. The process is identical, just remember to use port 443. What if my controller IP changes? You need a static IP or a dynamic DNS hostname. If the address changes, the integration will break. How secure is an Open SSID? The security is enforced by client isolation on the access point and the VLAN firewall rules. The guest network is isolated. For even greater security, we can deploy WPA3-Enterprise with RADIUS, which is what our PurpleConnex solution does.

To summarise, integrating Purple with UniFi elevates your guest WiFi from a simple utility to a strategic asset. It provides deep business intelligence, powerful marketing capabilities, and a professional user experience. The key to success is a methodical approach to the configuration: ensure public controller access, use an open SSID, configure the external portal and Walled Garden correctly, and use a dedicated local admin for the API. By following this guide, you can ensure a smooth, successful, and highly valuable deployment. For detailed, step-by-step written instructions and diagrams, please refer to the full technical reference guide on our website. Thank you for listening to the Purple Technical Briefing.

Resumo Executivo

O Ubiquiti UniFi é uma das plataformas corporativas de WiFi mais amplamente implementadas no mundo, com a confiança de hotéis, redes de varejo, estádios e organizações do setor público por seu desempenho, escalabilidade e custo-benefício. No entanto, seus recursos nativos de portal de visitantes são limitados. A plataforma de inteligência de WiFi da Purple resolve essa lacuna integrando-se diretamente ao UniFi Network Controller por meio de seu recurso External Portal Server, oferecendo uma experiência de Captive Portal totalmente personalizada e rica em análises, sem exigir nenhum hardware adicional.

Este guia fornece uma referência técnica completa para essa integração. Ele abrange a arquitetura subjacente, um processo de configuração passo a passo para as versões atuais (v7.4+) e legadas (v7.3 e anteriores) do UniFi, práticas recomendadas de segurança e conformidade, e uma estrutura de solução de problemas. As organizações que concluem essa integração ganham acesso a análises de visitantes em tempo real, captura de dados em conformidade com a GDPR, integração com CRM e a capacidade de fornecer comunicações de marketing direcionadas — transformando o WiFi de visitantes de um centro de custos em um ativo de negócios mensurável.

Aprofundamento Técnico

A integração entre o Ubiquiti UniFi e a Purple depende da funcionalidade External Portal Server do UniFi. Esse recurso redireciona os usuários visitantes do controlador UniFi local para um Captive Portal de terceiros designado — neste caso, a plataforma da Purple. O mecanismo subjacente depende de uma série de redirecionamentos HTTP e chamadas de API que gerenciam o ciclo de vida de autorização do visitante.

Quando um visitante se conecta ao SSID de autenticação aberta designado, o controlador UniFi coloca seu dispositivo em um estado 'pendente'. Nesse estado, todo o tráfego HTTP é interceptado e redirecionado para a URL da splash page da Purple, com parâmetros-chave anexados à string de consulta da URL: o endereço MAC do visitante, o endereço MAC do AP e o identificador do local. A plataforma da Purple captura esses parâmetros, apresenta a experiência de login apropriada e, após a autenticação bem-sucedida do usuário — seja via login social, formulário de e-mail ou voucher —, faz uma chamada de API HTTPS segura de volta ao UniFi Network Controller para autorizar o endereço MAC do visitante por uma duração de sessão especificada. Essa autorização move o dispositivo do estado 'pendente' para o 'autorizado', concedendo-lhe acesso à internet.

Um componente crítico dessa arquitetura é o Walled Garden — uma lista de permissões (whitelist) de endereços IP e domínios que os dispositivos dos visitantes têm permissão para acessar antes da autenticação. Isso é essencial para permitir o acesso aos próprios domínios da Purple, provedores de login social (Facebook, Google), endpoints de detecção CNA da Apple e quaisquer outros serviços externos necessários. Sem um Walled Garden configurado corretamente, o Captive Portal falhará completamente ao carregar.

Para implementações mais avançadas, o recurso PurpleConnex da Purple introduz o suporte ao Passpoint (IEEE 802.11u), usando um servidor RADIUS para reconexão contínua e sem credenciais para usuários recorrentes. Isso requer a configuração de um perfil RADIUS no UniFi apontando para o servidor de autenticação da Purple no IP 34.150.158.147, nas portas 1812 (autenticação) e 1813 (contabilidade/accounting).

Guia de Implementação

Esta seção fornece um guia passo a passo para configurar seu UniFi Network Controller para integração com a Purple. As instruções a seguir se aplicam ao UniFi Network Application versão 7.4 ou mais recente. Para versões legadas (v7.3 e anteriores), os princípios de configuração são idênticos, mas o caminho de navegação difere ligeiramente, usando Profiles > Guest Hotspot em vez do Hotspot Manager.

Passo 1: Verifique e Estabeleça a Acessibilidade do Controlador. Antes de iniciar qualquer configuração, confirme se o seu UniFi Network Controller está acessível a partir da internet pública. A plataforma em nuvem da Purple deve ser capaz de se comunicar com a API do seu controlador para autorizar as sessões dos visitantes. Para UniFi Controllers baseados em software, isso requer uma regra de encaminhamento de porta (port forward) no seu firewall mapeando a porta TCP 8443 para o endereço IP da LAN interna do controlador. Para implementações baseadas em hardware — incluindo o UniFi Dream Machine Pro (UDM Pro), UDM Special Edition, UDR e CloudKey Gen2+ —, a porta relevante é a TCP 443.

Passo 2: Crie uma Conta de Administrador Local Dedicada. Por questões de segurança, nunca use suas credenciais principais de superadministrador ou de conta em nuvem da Ubiquiti para a integração da API da Purple. Crie uma nova conta de administrador local dedicada no seu controlador UniFi especificamente para esse fim. Essa conta deve ter privilégios administrativos totais para o local relevante. O uso de uma conta dedicada limita o raio de impacto de qualquer possível comprometimento de credenciais e garante que a integração não seja interrompida por alterações em sua conta principal.

Passo 3: Crie o SSID do WiFi de Visitantes. No UniFi Network Application, navegue até Settings > WiFi e clique em Create New. Atribua um nome voltado para o público (por exemplo, 'Hotel Guest WiFi'). Defina o Security Protocol como Open — isso é obrigatório para que o mecanismo de redirecionamento do Captive Portal funcione. Atribua o SSID à sua VLAN de visitantes designada. Ative a opção Hotspot Portal.

Passo 4: Configure o Hotspot Portal e o Servidor Externo. Navegue até Hotspot Manager > Landing Page. Em Authentication, selecione External Portal Server e insira o endereço IP do External Portal fornecido pela Purple. Em Settings, configure da seguinte forma: ative Secure Portal, ative Redirect using Hostname e insira o Access Domain fornecido pela Purple, e certifique-se de que HTTPS Redirection esteja definido como Disabled. A Default Expiration da sessão deve ser definida para 8 horas.

Passo 5: Configure o Walled Garden. Nas configurações do Hotspot Manager, localize a seção Pre-Authorization Access. Adicione todos os domínios da lista fornecida pela Purple. Essa lista normalmente inclui os domínios da própria plataforma da Purple, domínios de provedores de login social (facebook.com, google.com, accounts.google.com), endpoints de detecção do Captive Network Assistant (CNA) da Apple e quaisquer outros serviços de terceiros usados em sua splash page. Este passo é a fonte mais comum de falhas de implementação e deve ser concluído com precisão.

Passo 6: Insira os Detalhes do Controlador no Portal da Purple. Faça login na sua conta da Purple e navegue até as configurações do local (Venue) relevante. Insira o endereço IP público ou o hostname do seu UniFi Controller e as credenciais da conta de administrador local dedicada criada no Passo 2. Salve a configuração. A Purple tentará validar a conexão.

Passo 7: Teste e Valide. Usando um dispositivo móvel não conectado anteriormente à rede, conecte-se ao novo SSID de visitantes. Você deve ser redirecionado automaticamente para o Captive Portal da Purple. Autentique-se usando um dos métodos configurados. Em caso de sucesso, você deverá receber acesso à internet. Se o redirecionamento falhar ou o acesso à internet não for concedido após a autenticação, consulte a seção de Solução de Problemas abaixo.

Práticas Recomendadas

A segmentação de rede é o requisito de segurança fundamental para qualquer implementação de WiFi de visitantes. O SSID de visitantes deve ser atribuído a uma VLAN dedicada, protegida por firewall contra todas as redes corporativas e administrativas. Isso impede que os dispositivos dos visitantes acessem recursos internos, atende aos requisitos de isolamento de rede do PCI DSS e limita o impacto de qualquer incidente de segurança na rede de visitantes.

O gerenciamento de largura de banda é igualmente importante em ambientes de alta densidade. O recurso de limitação de taxa por usuário do UniFi deve ser configurado para estabelecer limites razoáveis de upload e download para usuários visitantes. Isso evita que um pequeno número de usuários com alto consumo de banda degrade a experiência de todos os visitantes, o que é particularmente relevante em implementações em hotéis e centros de conferências.

O Walled Garden requer manutenção contínua. Provedores de login social e outros serviços de terceiros atualizam periodicamente suas estruturas de domínio. Uma revisão trimestral da configuração do Walled Garden, cruzada com a lista de domínios recomendada mais recente da Purple, é uma prática operacional sólida. A falha em manter essa lista é a principal causa de falhas no portal pós-implementação.

Para a integração da API, sempre use uma conta de administrador local dedicada em vez de uma conta vinculada à nuvem. Esta é tanto uma prática recomendada de segurança quanto uma medida de confiabilidade — as credenciais de contas em nuvem estão sujeitas a fluxos de autenticação multifator que podem interromper as chamadas de API automatizadas que a Purple faz para autorizar os visitantes.

Solução de Problemas e Mitigação de Riscos

O modo de falha mais comum é um Captive Portal que não carrega. Quando um visitante se conecta ao SSID, mas não vê nenhum redirecionamento, ou a página do portal não é renderizada, a causa raiz é quase invariavelmente um Walled Garden incompleto. Comece a solução de problemas conectando um dispositivo de teste e tentando navegar para uma URL HTTP conhecida. Se o redirecionamento ocorrer, mas a página não carregar, adicione os domínios ausentes ao Walled Garden. Verifique também se o DNS da rede de visitantes está configurado corretamente para resolver hostnames externos.

A segunda falha mais comum é um cenário em que o visitante se autentica com sucesso no portal da Purple, mas não recebe acesso à internet. Isso indica uma falha na comunicação da API entre a Purple e o controlador UniFi. Os passos de diagnóstico são: primeiro, confirme se o controlador está acessível publicamente na porta correta, tentando acessá-lo de uma rede externa; segundo, verifique se as credenciais de administrador local inseridas no portal da Purple estão corretas e se a conta não foi bloqueada; terceiro, revise os logs de eventos do controlador UniFi em busca de quaisquer erros de autenticação da API.

Para implementações em produção, a disponibilidade do controlador é um fator de risco crítico. Se o controlador UniFi ficar offline, as novas autorizações de visitantes falharão. As estratégias de mitigação incluem a implementação de um controlador UniFi hospedado na nuvem (que fornece redundância inerente), a implementação de um par de controladores de alta disponibilidade ou a configuração de monitoramento e alertas sobre a disponibilidade do controlador. A plataforma da Purple colocará as tentativas de autorização em fila e tentará novamente, mas um tempo de inatividade prolongado do controlador resultará em uma experiência degradada para o visitante.

Do ponto de vista da conformidade, os dados coletados por meio do Captive Portal estão sujeitos à GDPR e a regulamentações equivalentes de proteção de dados. A plataforma da Purple foi projetada para conformidade, fornecendo gerenciamento de consentimento, ferramentas de solicitação de acesso do titular dos dados (DSAR) e políticas configuráveis de retenção de dados. No entanto, a responsabilidade legal pelo processamento lícito de dados permanece com o operador do local. Certifique-se de que sua política de privacidade esteja claramente vinculada na splash page, que você tenha uma base legal documentada para a coleta de dados e que suas configurações de retenção de dados estejam alinhadas com a política da sua organização.

ROI e Impacto nos Negócios

Integrar a Purple ao UniFi não é apenas uma atualização técnica; é uma decisão estratégica de negócios que transforma o WiFi de visitantes de um centro de custos em um ativo poderoso. O retorno sobre o investimento é mensurável em várias dimensões-chave.

A inteligência de negócios (Business Intelligence) é o principal impulsionador de valor. A Purple captura dados ricos e anonimizados sobre o comportamento dos visitantes — incluindo fluxo de pessoas (footfall), tempos de permanência, frequência de visitas e padrões de movimento. Para uma rede de varejo, esses dados podem orientar diretamente as decisões de layout da loja, níveis de equipe e cronograma promocional. Para um hotel, pode revelar quais comodidades são mais usadas e em quais horários, permitindo um upselling mais direcionado e eficiência operacional.

Os recursos de marketing e engajamento representam um benefício secundário significativo. Ao capturar os detalhes de contato dos visitantes com consentimento, as organizações podem construir um banco de dados de marketing primário (first-party) que não está sujeito às limitações da descontinuação de cookies de terceiros. Campanhas de e-mail pós-visita, pesquisas de satisfação e convites para programas de fidelidade podem ser automatizados diretamente da plataforma da Purple, impulsionando melhorias mensuráveis nas taxas de visitas repetidas e no valor do ciclo de vida do cliente (LTV).

Para grandes locais, como estádios, centros de conferências e shopping centers, a inteligência operacional derivada de análises de fluxo de pessoas em tempo real e mapas de calor pode impulsionar ganhos significativos de eficiência — otimizando cronogramas de limpeza, implantação de segurança e posicionamento de concessões de varejo com base em dados reais de movimento de visitantes, em vez de suposições.

Em certos contextos, a própria infraestrutura de WiFi de visitantes pode ser monetizada por meio de modelos de acesso em níveis, splash pages patrocinadas ou publicidade direcionada, criando um fluxo de receita direto que compensa o custo do investimento em infraestrutura.

Termos-Chave e Definições

Captive Portal

A web page displayed to newly connected users of a WiFi network before they are granted broader internet access. It controls access, authenticates users, and/or presents terms of service and marketing content.

In a UniFi/Purple integration, the UniFi controller redirects the guest to the Purple-hosted captive portal, which manages the entire guest experience including authentication, consent capture, and branding.

External Portal Server

A UniFi configuration option that delegates the captive portal experience to a third-party web application, rather than using UniFi's built-in portal. The UniFi controller redirects guests to the specified external URL and relies on that system to handle authentication and to call back to the controller's API to authorise the guest.

This is the core UniFi setting that enables the Purple integration. It is found under Hotspot Manager > Landing Page > Authentication in UniFi Network v7.4+.

Walled Garden

A whitelist of IP addresses, hostnames, and domains that a guest device is permitted to access before it has been authenticated by the captive portal. Traffic to non-whitelisted destinations is blocked until the guest completes the authentication flow.

This is critical for allowing the device to load the Purple splash page itself, as well as any third-party resources it relies on, such as social login providers or payment gateways. An incomplete Walled Garden is the leading cause of captive portal failures.

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol (RFC 2865) that provides centralised Authentication, Authorisation, and Accounting (AAA) management for users connecting to a network service.

While the standard Purple integration uses the UniFi API for guest authorisation, the PurpleConnex (Passpoint) feature uses RADIUS to provide a more secure and seamless connection experience for returning users, eliminating the need to re-authenticate via the captive portal.

Passpoint (IEEE 802.11u / Hotspot 2.0)

A WiFi Alliance certification programme that enables automatic, secure authentication to WiFi networks without requiring the user to manually select a network or enter credentials. Devices with a Passpoint profile connect automatically and securely using EAP-based authentication.

Purple's PurpleConnex feature leverages Passpoint to provide a seamless reconnection experience for returning guests. Once a user has authenticated once via the captive portal, subsequent visits can connect automatically without seeing the splash page again.

SSID (Service Set Identifier)

The public name of a wireless local area network (WLAN) — the network name that appears when a user searches for available WiFi connections on their device.

For a guest network integration, a dedicated SSID is created with Open security and linked to the captive portal. This is kept separate from the corporate SSID, which uses WPA2/WPA3-Enterprise authentication.

VLAN (Virtual Local Area Network)

A method of creating logically separate networks on the same physical network infrastructure. Devices on different VLANs cannot communicate with each other without a router, providing network segmentation and security isolation.

Security best practice and PCI DSS compliance require that the guest SSID be placed on its own VLAN, completely isolated from the corporate, management, and POS networks. This prevents guest devices from accessing internal resources.

WISPr (Wireless Internet Service Provider Roaming)

An industry-standard protocol that defines how a client device discovers and authenticates to a WiFi hotspot captive portal. It uses HTTP redirects and XML-based authentication messages to manage the portal interaction.

UniFi's external portal functionality is based on WISPr principles. Understanding this protocol helps network engineers troubleshoot redirect failures and understand why certain client devices (particularly iOS and Android) behave differently when connecting to captive portal networks.

Port Forwarding

A network address translation (NAT) technique that maps an external port on a router or firewall to a specific internal IP address and port, allowing external services to initiate connections to devices on a private network.

If your UniFi controller is hosted on a local network, a port forward rule must be configured to allow the Purple cloud platform to reach the controller's API. The required port is 8443 for software controllers or 443 for hardware-based controllers.

PurpleConnex

Purple's implementation of the Passpoint (IEEE 802.11u) standard, which provides a secure, seamless WiFi connection for returning users using EAP-TTLS authentication via a dedicated RADIUS server. It eliminates the need for repeat visitors to re-authenticate via the captive portal.

PurpleConnex requires additional configuration in UniFi: a RADIUS profile pointing to Purple's authentication server and a separate Passpoint-enabled SSID. It is particularly valuable in hospitality and retail environments where repeat visitors are common.

Estudos de Caso

A 250-room boutique hotel wants to replace its basic, unreliable guest WiFi with a premium, branded experience. Their goals are to capture guest email addresses for post-stay marketing, promote their spa and restaurant on the login page, and ensure seamless connectivity for guests with multiple devices. Their infrastructure consists of a UniFi Dream Machine Pro and 40 UniFi U6 Pro access points.

The recommended deployment integrates the UDM Pro with Purple via the External Portal Server method. A new 'Hotel Guest WiFi' SSID is created with Open security and assigned to a dedicated Guest VLAN (e.g., VLAN 20), which is firewalled from the hotel's management and POS networks. The Hotspot Portal is enabled and configured to use Purple as the external portal server. Since the UDM Pro uses port 443, a port forward rule is created on the UDM Pro's WAN interface mapping TCP 443 to the UDM Pro's LAN IP. A dedicated local administrator account ('purple-api') is created on the UDM Pro with full site privileges. In the Purple portal, a custom-branded splash page is designed featuring the hotel's logo, a simple email capture form with GDPR consent checkbox, and a prominent banner advertising the spa with a direct booking link. The Walled Garden is configured to include all Purple domains, Facebook, Google, and Apple CNA endpoints. The hotel's marketing team is given access to the Purple analytics dashboard, enabling them to track daily guest counts, peak connection times, and email capture rates. Within the first quarter, the hotel captures an average of 180 new email addresses per week, which are automatically synced to their CRM for post-stay campaign automation.

Notas de Implementação: This solution correctly addresses all requirements. The choice of an external captive portal over UniFi's built-in portal is the only viable approach for achieving the required level of branding, data capture, and CRM integration. The decision to use a dedicated local admin account ('purple-api') rather than the primary super-admin is a critical security best practice — it limits the scope of API access and ensures the integration is not disrupted by changes to the primary account. The VLAN segmentation protects the hotel's POS and management systems from guest network traffic, which is a PCI DSS requirement. The port 443 configuration for the UDM Pro is a common point of confusion for engineers accustomed to software controllers; this distinction must be clearly understood before deployment.

A retail chain with 20 stores across the UK, each equipped with UniFi APs managed by a single cloud-hosted UniFi controller, wants to use guest WiFi data to understand customer behaviour. The operations director needs to measure footfall, dwell time, and repeat visitor rates across all stores to inform a store layout redesign programme and evaluate the performance of in-store promotional campaigns.

The cloud-hosted UniFi controller already has a public hostname, so no port forwarding is required — this is a significant simplification of the deployment. A single guest SSID ('Brand WiFi') is configured and applied to all 20 sites via the UniFi controller's site management capabilities. The Hotspot Portal is configured to use Purple's external portal server. In the Purple portal, each of the 20 stores is configured as a separate venue, allowing for granular, store-level analytics. The splash page is designed for maximum adoption: a single 'Connect' button with a brief privacy notice, minimising friction. Within the Purple analytics platform, the operations director can view a comparative dashboard showing footfall, dwell time, and new vs. returning visitor ratios for each store. After 90 days of data collection, the analytics reveal that three stores have significantly higher dwell times than the others, correlating with a specific store layout. This insight directly informs the layout redesign programme, with the high-performing layout rolled out to all 20 stores. A promotional campaign is run across all stores simultaneously, and the Purple dashboard provides a clear before-and-after comparison of footfall and dwell time, demonstrating measurable campaign uplift.

Notas de Implementação: This scenario highlights the power of a centralised, multi-venue Purple deployment. The key architectural decision is the use of a single cloud-hosted UniFi controller, which eliminates the port forwarding complexity present in on-premises deployments and provides a single point of management for all 20 sites. The low-friction 'one-click connect' splash page design is the correct choice for a retail environment where maximising data collection volume is the primary objective — a complex login form would significantly reduce adoption rates. The separation of each store as a distinct venue in Purple is essential for generating actionable, store-level insights rather than aggregated data that obscures performance differences between locations.

Análise de Cenário

Q1. A hotel IT manager has completed the UniFi/Purple integration configuration and tested it successfully in the office. However, after deploying to the live hotel environment, guests report that the captive portal page loads but the 'Login with Facebook' button does not work. What is the most likely cause and how should it be resolved?

💡 Dica:Consider what resources the Facebook login button needs to load and function, and whether those resources are accessible to a guest device before authentication.

Mostrar Abordagem Recomendada

The most likely cause is that the Facebook login domains are not included in the Walled Garden (pre-authorisation access list). When a guest device is in the 'pending' state, it can only access domains explicitly whitelisted in the Walled Garden. The Facebook login flow requires access to facebook.com, fbcdn.net, and related domains. The resolution is to add all required Facebook domains to the Walled Garden in the UniFi Hotspot Manager settings. Purple provides a maintained list of required domains for each social login provider. After updating the Walled Garden, test the Facebook login flow again with a fresh device connection.

Q2. A network architect is planning a guest WiFi deployment for a 5,000-seat conference centre that will host events with up to 3,000 simultaneous WiFi users. The venue uses a software-based UniFi controller hosted on a server in the venue's server room. What are the three most critical infrastructure considerations for ensuring the Purple integration remains reliable during peak events?

💡 Dica:Think about the single points of failure in the integration architecture — what happens if the controller goes offline, if the internet connection is saturated, or if the controller's hardware is underpowered?

Mostrar Abordagem Recomendada

The three most critical considerations are: First, controller availability and performance — the UniFi controller is a critical component in every guest authorisation. At 3,000 simultaneous users, the controller must have sufficient CPU and RAM to handle the load. Consider upgrading to a high-specification server or migrating to a cloud-hosted controller for inherent redundancy. Second, internet connectivity and port forwarding reliability — Purple's API calls to the controller must traverse the venue's internet connection. Ensure the port forward rule is on a resilient firewall and that the internet connection has sufficient capacity. A secondary internet connection with automatic failover is advisable for mission-critical events. Third, bandwidth management — with 3,000 users, implement strict per-user rate limits in UniFi to prevent bandwidth exhaustion. Without rate limiting, a small number of high-bandwidth users can degrade the experience for all guests.

Q3. An IT manager at a retail chain is asked by the legal team to ensure the guest WiFi data collection is fully GDPR-compliant. The current splash page has a simple 'Connect' button with no explicit consent mechanism. What changes need to be made to the Purple configuration, and what ongoing operational processes should be implemented?

💡 Dica:GDPR requires a lawful basis for processing personal data, transparency about how data will be used, and mechanisms for data subjects to exercise their rights.

Mostrar Abordagem Recomendada

The following changes and processes are required: On the splash page, the 'Connect' button must be replaced with an explicit opt-in mechanism. This means adding a clearly worded consent checkbox (unchecked by default) that states what data is being collected, how it will be used, and who it will be shared with. A link to the full privacy policy must be prominently displayed. The legal basis for processing should be explicit consent for marketing communications and legitimate interest for anonymised analytics. Within the Purple portal, configure data retention settings to align with the organisation's data retention policy — typically no longer than 24 months for marketing data. Enable Purple's GDPR tooling to handle data subject access requests (DSARs) and right-to-erasure requests. Operationally, implement a quarterly review process to ensure the privacy policy remains accurate, the consent wording is up to date, and data retention settings are enforced. Maintain a record of processing activities (ROPA) entry for the guest WiFi data collection.

Q4. A network engineer has configured the UniFi/Purple integration following all documented steps. When testing, the guest device connects to the SSID and is redirected to the Purple portal. The guest successfully authenticates, but is not granted internet access. The Purple portal shows the authentication as successful. What is the diagnostic process?

💡 Dica:If Purple shows a successful authentication but the guest has no internet access, the issue lies in the communication path between Purple and the UniFi controller.

Mostrar Abordagem Recomendada

This symptom indicates that Purple's API call to the UniFi controller — the call that moves the guest device from 'pending' to 'authorised' — is failing. The diagnostic process is as follows: First, verify that the UniFi controller is publicly accessible on the correct port (8443 for software, 443 for hardware) by attempting to reach the controller's management interface from an external network or using an online port checker tool. Second, log in to the Purple portal and verify that the controller IP/hostname and local admin credentials are correct. A common error is entering the controller's internal LAN IP rather than its public IP, or using cloud account credentials instead of local admin credentials. Third, check the UniFi controller's event log for any API authentication errors or failed login attempts from Purple's IP addresses. Fourth, verify that the firewall rule or port forward is correctly configured and that Purple's source IP addresses are not being blocked by any upstream security appliance.

Principais Conclusões

✓The UniFi/Purple integration uses UniFi's External Portal Server feature to redirect guests to the Purple captive portal, which handles authentication and calls back to the UniFi API to authorise guest access — no additional hardware is required.
✓The Walled Garden (pre-authorisation access list) is the most critical and most frequently misconfigured element of the deployment. It must include all Purple domains, social login provider domains, and Apple CNA endpoints before the portal will function correctly.
✓Always use a dedicated local administrator account on the UniFi controller for the Purple API integration — never use your primary Ubiquiti cloud account credentials. This is both a security best practice and a reliability requirement.
✓The correct API port depends on the controller type: TCP 8443 for software-based controllers, TCP 443 for hardware-based controllers (UDM Pro, UDM SE, UDR, CloudKey Gen2+). Configuring the wrong port is a common cause of API communication failures.
✓Network segmentation is non-negotiable: the guest SSID must be on a dedicated VLAN, firewalled from all corporate and management networks. This is required for both security and PCI DSS compliance.
✓The ROI of the Purple integration extends well beyond connectivity: visitor analytics, GDPR-compliant data capture, CRM integration, and targeted marketing communications transform guest WiFi into a measurable business asset.
✓For returning users, Purple's PurpleConnex (Passpoint/IEEE 802.11u) feature provides a seamless, credential-free reconnection experience using RADIUS-based EAP-TTLS authentication, eliminating the need to re-authenticate via the captive portal on subsequent visits.