Integración de Cisco Meraki con Purple WiFi

This guide provides a definitive technical reference for deploying Purple WiFi on Cisco Meraki infrastructure, covering the dual-layer integration architecture — Dashboard API provisioning and Captive Portal API authentication — alongside step-by-step RADIUS and splash page configuration. It is designed for network engineers and IT managers who need to move from a functional guest WiFi deployment to a strategic guest intelligence platform, with measurable ROI outcomes drawn from live enterprise deployments including McDonald's Belgium, Harrods, and AGS Airports.

📖 10 min de lectura📝 2,309 palabras🔧 2 ejemplos❓ 3 preguntas📚 10 términos clave

🎧 Escucha esta guía

Ver transcripción

Cisco Meraki Integration with Purple WiFi — A Senior Consultant Briefing
Running time: approximately 10 minutes

INTRODUCTION AND CONTEXT (approximately 1 minute)

Welcome. If you are responsible for a Cisco Meraki deployment and you are trying to decide whether Purple WiFi is the right guest intelligence layer to sit on top of it, this briefing is for you. I am going to take you through exactly how the integration works, what you need to configure, where the common pitfalls are, and what kind of return you should realistically expect.

Let me set the scene. Cisco Meraki is, by a significant margin, the most widely deployed cloud-managed wireless infrastructure in the enterprise hospitality, retail, and public-sector space. It is reliable, scalable, and its cloud dashboard is genuinely excellent. But here is the thing — Meraki's native guest WiFi capabilities are functional, not strategic. You can get a guest online, but you cannot capture meaningful first-party data, you cannot build a marketing funnel from it, and you certainly cannot demonstrate ROI to your board. That is precisely the gap that Purple fills.

TECHNICAL DEEP-DIVE (approximately 5 minutes)

Let us talk architecture. The Purple and Meraki integration operates across two distinct technical layers, and understanding both is essential before you touch a single configuration setting.

The first layer is the Meraki Dashboard API — this is the provisioning layer. Purple uses Meraki's REST API to import your entire access point estate into the Purple Portal in a single batch operation. You authenticate with your Meraki API key, which you generate from the Organisation section of the Meraki dashboard under API and Webhooks. Once Purple has that key, it can pull every access point, every network, every SSID configuration directly from your Meraki cloud. For an estate of, say, three hundred access points across a hotel group, this reduces what would be a multi-day manual configuration exercise to something you can complete in under an hour. That is not a trivial operational saving.

The second layer is the authentication and captive portal layer — this is where the guest experience actually lives. Purple operates as an external splash page provider, using Meraki's Captive Portal API. When a guest connects to your guest SSID, Meraki intercepts their HTTP traffic and redirects them to Purple's hosted splash page — your branded captive portal. The guest authenticates through whatever method you have configured: social login, email form, SMS verification, or a combination. Purple then communicates back to Meraki via RADIUS — Remote Authentication Dial-In User Service — operating on port 1812 for authentication and port 1813 for accounting. Once RADIUS confirms the authentication, Meraki grants the guest full network access.

Now, let me walk you through the specific Meraki dashboard configuration, because the details matter here.

In the Meraki dashboard, navigate to Wireless, then Access Control. Select your guest SSID from the dropdown. Set the security to Open — yes, open, because the authentication is handled by the RADIUS and captive portal layer, not at the 802.11 association level. Set the splash page type to Sign-on with my RADIUS server. This is the critical selection — it tells Meraki to use an external RADIUS server for authentication rather than its own built-in options.

Under Advanced Splash Settings, set the captive portal strength to Block all access until sign-on is complete. Enable the walled garden — this is the list of domains that guests can reach before they have authenticated, which must include Purple's platform domains so the splash page itself can load. Purple provides a maintained whitelist of these domains in their support documentation.

For the RADIUS server configuration, you will need to add two servers — Purple provides primary and secondary endpoints for redundancy. The authentication port is 1812, and you will use the RADIUS secret provided in your Purple Portal. Add corresponding entries for RADIUS accounting on port 1813. Set the accounting interim interval to four minutes — this is important for accurate session tracking and analytics. Set the server timeout to five seconds with a retry count of three.

Under Advanced RADIUS Settings, configure the Called-Station-ID and NAS-ID to use the AP MAC address. This is critical for Purple's location analytics — without it, Purple cannot accurately attribute sessions to specific access points and therefore cannot generate meaningful floor-level analytics.

Then navigate to Wireless, Splash Page. Enter the custom splash URL provided by your Purple Portal — this is the URL of your branded captive portal. Configure the post-authentication redirect URL — typically your venue's website or a specific landing page.

Now, there is a second component worth discussing in detail: PurpleConnex, which is Purple's SecurePass solution. This creates a second SSID — typically named PurpleConnex — configured as a WPA2 Enterprise network using Purple's RadSec RADIUS servers. RadSec is RADIUS over TLS, which provides encrypted transport for authentication traffic. This SSID, combined with Hotspot 2.0 configuration — also known as Passpoint, the IEEE 802.11u standard — allows returning guests to reconnect automatically without seeing the captive portal again. Their device recognises the Passpoint profile and connects seamlessly. This is particularly valuable in environments where you want to eliminate the friction of repeat authentication, such as a hotel where a guest is staying for three nights, or a retail loyalty member who visits weekly.

The Hotspot 2.0 configuration in Meraki requires you to set the operator name to PURPLE colon GB, configure the domain list to securewifi.purple.ai, and add the Roaming Consortium OIs that Purple specifies. The NAI Realm is configured with EAP-TTLS and PAP authentication method. This is all documented in Purple's support portal, and it is straightforward once you understand what each field is doing.

IMPLEMENTATION RECOMMENDATIONS AND PITFALLS (approximately 2 minutes)

Let me give you the three most common failure modes I see in Meraki and Purple deployments, and how to avoid them.

First: walled garden misconfiguration. If your walled garden list is incomplete, guests will see a broken splash page — the CSS will not load, images will not render, and authentication will fail silently. Purple maintains a current whitelist of required domains. Treat this list as a living document and review it whenever Purple releases a platform update. I recommend testing the captive portal experience from a guest device on a separate network segment before go-live.

Second: RADIUS timeout settings. The default Meraki RADIUS timeout is often set too low for cloud-hosted RADIUS servers. Five seconds with three retries is the correct configuration. If you leave it at the default two seconds, you will see intermittent authentication failures during peak load — exactly the worst time for your guest experience to degrade.

Third: NAS-ID and Called-Station-ID misconfiguration. This is the one that catches engineers out most often. If you configure these fields incorrectly — or leave them as defaults — Purple's analytics engine cannot map sessions to specific access points. You will get aggregate data but no floor-level intelligence. The value must be set to AP MAC address, not SSID name or any other option.

On the compliance side: Purple's data capture is GDPR and CCPA compliant by design. The captive portal presents a consent mechanism that meets the requirements of both regulations. If you are operating in a PCI DSS scope environment — a hotel with a payment terminal on the same network segment, for example — ensure your guest SSID is on a separate VLAN with appropriate firewall rules. Meraki's NAT mode for client IP assignment, which is the recommended setting, provides a degree of isolation, but your network segmentation architecture needs to be reviewed by your security team independently.

RAPID-FIRE Q AND A (approximately 1 minute)

Question: Can Purple integrate with Meraki MX security appliances as well as wireless APs?

Answer: Yes. The configuration process is essentially identical — the MX supports the same splash page and RADIUS configuration as the wireless APs. The support article covers AP, MX, and Z1 teleworker gateway configurations.

Question: How long does a full deployment take for a 50-site hotel group?

Answer: With the automated provisioning via the Meraki API, the access point import is a single operation per organisation. The SSID and RADIUS configuration can be templated across networks. A 50-site deployment with a competent network engineer should be achievable in two to three days of configuration work, plus testing time.

Question: Does Purple support Meraki's newer Wi-Fi 6 and Wi-Fi 6E access points?

Answer: Yes. The integration operates at the application layer — RADIUS and HTTP redirect — so it is hardware-generation agnostic. Purple works with any Meraki AP that supports the splash page and RADIUS configuration described.

SUMMARY AND NEXT STEPS (approximately 1 minute)

To summarise: the Cisco Meraki and Purple WiFi integration is a mature, well-documented deployment that combines Meraki's excellent cloud-managed infrastructure with Purple's guest intelligence and data capture capabilities. The integration uses two primary mechanisms — the Meraki Dashboard API for automated provisioning, and the Captive Portal API with RADIUS authentication for the guest experience layer.

The three things to get right are: your walled garden configuration, your RADIUS timeout and retry settings, and your NAS-ID configuration for accurate location analytics.

The business case is compelling. McDonald's Belgium, Walmart Canada, and Harrods are all live Purple and Cisco deployments. AGS Airports achieved an 842 percent return on investment. Harrods turned 600,000 WiFi logins into a 57 times return on investment.

If you are ready to move forward, the next step is to generate your Meraki API key, log into the Purple Portal, and use the Hardware Import Wizard to pull in your access point estate. From there, your Purple account team can walk you through the SSID and RADIUS configuration in a single session.

Thank you for your time.

Resumen ejecutivo

Cisco Meraki es la infraestructura principal preferida por miles de recintos empresariales: hoteles, cadenas minoristas, estadios e instalaciones del sector público. Su arquitectura gestionada en la nube ofrece simplicidad operativa a gran escala, pero sus capacidades nativas de WiFi para invitados se quedan muy cortas respecto a lo que requiere un operador de recintos moderno: captura de datos de origen (first-party data), gestión de consentimientos conforme al GDPR, analítica de afluencia en tiempo real e integración con la automatización de marketing. Purple WiFi cierra esa brecha de manera decisiva.

La integración de Purple y Meraki opera en dos capas técnicas. La Meraki Dashboard API permite el aprovisionamiento masivo automatizado, importando cientos de puntos de acceso de una organización de Meraki al portal de Purple en una sola operación. La Meraki Captive Portal API, combinada con la autenticación RADIUS, ofrece la experiencia de cara al invitado: una página de inicio (splash page) totalmente personalizada con la marca, opciones de autenticación flexibles y un registro de sesiones que alimenta el motor de analítica de Purple. Para los invitados recurrentes, el SSID PurpleConnex (SecurePass) aprovecha Hotspot 2.0 (Passpoint, IEEE 802.11u) para una reconexión automática y fluida, eliminando la fricción de tener que autenticarse repetidamente.

Las implementaciones de esta integración están activas a gran escala: McDonald's Bélgica, Walmart Canadá, Harrods (ROI de 57x en 600,000 inicios de sesión) y AGS Airports (ROI del 842%). Para cualquier equipo de TI que gestione una infraestructura de Meraki y busque demostrar un valor comercial medible a partir del WiFi para invitados, esta integración es el camino más eficiente a nivel operativo para lograr ese resultado.

Análisis técnico detallado

Arquitectura de integración

La integración de Purple y Meraki se entiende mejor como dos relaciones de API paralelas que operan en diferentes capas de la pila de red. La primera es una integración en el plano de gestión a través de la REST API del panel de control de Meraki (Meraki Dashboard REST API), utilizada exclusivamente para el aprovisionamiento y la configuración. La segunda es una integración en el plano de datos a través de la Meraki Captive Portal API y el protocolo RADIUS, que rige el flujo de autenticación en vivo de los invitados.

Plano de gestión: Aprovisionamiento de la Dashboard API

Meraki expone una REST API integral en api.meraki.com/api/v1. El asistente de importación de hardware de Purple se autentica en esta API utilizando una clave de API a nivel de organización, y luego enumera todas las redes, SSID y puntos de acceso dentro de la organización de Meraki. Esto permite a un ingeniero de redes importar una infraestructura de más de 300 puntos de acceso en 50 sitios en una sola operación por lotes, un proceso que de otro modo requeriría la entrada manual para cada dispositivo. La capacidad de integración bidireccional de Purple también permite a la plataforma enviar la configuración del Captive Portal, el walled garden y RADIUS de vuelta a Meraki, reduciendo aún más la carga de configuración manual.

Para generar la clave de API requerida, navegue a Organización > API y webhooks > Claves de API (Organisation > API & Webhooks > API Keys) en el panel de control de Meraki y seleccione Generar clave de API (Generate API Key). Esta clave debe tratarse como una credencial privilegiada: guárdela en un sistema de gestión de secretos y rótela según el ciclo de vida de credenciales estándar de su organización.

Plano de datos: Captive Portal API y RADIUS

El flujo de autenticación de invitados utiliza la Meraki Captive Portal API en modo de inicio de sesión (Sign-on). Cuando un invitado se asocia con el SSID de invitados, el motor de control de acceso de Meraki intercepta la primera solicitud HTTP y emite una redirección 302 a la URL de la página de inicio alojada por Purple. La página de inicio se sirve desde la infraestructura CDN de Purple; la configuración del walled garden garantiza que los dominios de Purple sean accesibles antes de que se complete la autenticación.

Una vez que el invitado completa la autenticación en la página de inicio, la plataforma de Purple emite un mensaje RADIUS Access-Accept al punto de acceso de Meraki en el puerto 1812. A continuación, Meraki otorga al dispositivo acceso completo a la red. Los mensajes de contabilidad RADIUS en el puerto 1813 proporcionan eventos de inicio de sesión, actualización provisional (cada 4 minutos) y finalización de sesión al motor de analítica de Purple, lo que permite realizar cálculos precisos del tiempo de permanencia, la duración de la sesión y las visitas recurrentes.

Métodos de autenticación

El Captive Portal de Purple admite múltiples mecanismos de autenticación, cada uno con diferentes implicaciones en la captura de datos:

Método	Datos capturados	Consentimiento GDPR	Caso de uso recomendado
Inicio de sesión social (Facebook, Google)	Nombre, correo electrónico, datos de perfil	Casilla de consentimiento en línea	Hospitalidad, lealtad en retail
Formulario por correo electrónico	Correo electrónico, campos personalizados	Casilla de consentimiento en línea	Cualquier recinto, máximo control de datos
Verificación por SMS	Número de teléfono móvil	Casilla de consentimiento en línea	Recintos de alta seguridad o con restricción de edad
Clic directo (solo Términos de servicio)	MAC del dispositivo, datos de sesión	Aceptación de términos	Acceso público de baja fricción

PurpleConnex: SecurePass y Hotspot 2.0

PurpleConnex es un segundo SSID implementado junto con el SSID principal para invitados. Está configurado como una red WPA2 Enterprise, con los servidores RADIUS RadSec de Purple (rad1-secure.purple.ai y rad2-secure.purple.ai) en el puerto 2083 con transporte TLS. Hotspot 2.0 (Passpoint) está habilitado en este SSID, anunciando el dominio securewifi.purple.ai y los OI del Consorcio de Roaming de Purple. Cuando el dispositivo de un invitado recurrente ha descargado previamente un perfil Passpoint de Purple, se asociará automáticamente con PurpleConnex y se autenticará de forma silenciosa: sin página de inicio ni inicio de sesión manual. Esto es particularmente impactante en entornos hoteleros, donde a un huésped que se registra para una estadía de varias noches no se le debe exigir que se vuelva a autenticar en cada reconexión del dispositivo.

La configuración de Hotspot 2.0 también aborda el desafío de la aleatorización de direcciones MAC introducido por iOS 14 y Android 10+. Debido a que la autenticación de PurpleConnex se basa en credenciales en lugar de en la dirección MAC, Purple puede mantener un registro de identidad de invitado consistente incluso cuando el dispositivo presenta una dirección MAC aleatoria diferente en cada intento de conexión.

Guía de implementación

Lista de verificación previa a la implementación

Antes de comenzar la configuración, confirme que se cumplen los siguientes requisitos previos. Su organización de Meraki debe tener habilitado el acceso a la API; esta es una configuración a nivel de organización en Organización > Configuración > Acceso a la API del panel de control (Organisation > Settings > Dashboard API Access). Necesitará una cuenta en el portal de Purple con sus recintos creados y sus SSID configurados. Obtenga los siguientes valores del portal de Purple antes de modificar el panel de control de Meraki: los nombres de host del servidor RADIUS y el secreto compartido, la URL personalizada de la página de inicio, la URL de redirección posterior a la autenticación y la lista blanca actual de dominios del walled garden.

Paso 1: Generar la clave de API de Meraki e importar puntos de acceso

En el panel de control de Meraki, navegue a Organización > API y webhooks > Claves de API (Organisation > API & Webhooks > API Keys) y genere una nueva clave de API. Copie esta clave inmediatamente, ya que solo se muestra una vez. En el portal de Purple, navegue a Gestión de recintos > Importar hardware > API de terceros (Venue Management > Import Hardware > Third Party API), seleccione Cisco Meraki y pegue su clave de API. Purple enumerará toda su infraestructura de puntos de acceso. Seleccione los puntos de acceso que desea asociar con cada recinto de Purple y confirme la importación.

Paso 2: Configurar el SSID de invitados — Control de acceso

En el panel de control de Meraki, navegue a Inalámbrico > Control de acceso (Wireless > Access Control). Seleccione su SSID de invitados en el menú desplegable y aplique la siguiente configuración:

Parámetro	Valor
Estado del SSID	Habilitado (Enabled)
Seguridad	Abierta (Open)
Página de inicio (Splash Page)	Iniciar sesión con mi servidor RADIUS (Sign-on with my RADIUS server)
Fuerza del Captive Portal	Bloquear todo el acceso hasta que se complete el inicio de sesión (Block all access until sign-on is complete)
Walled Garden	Habilitado (agregue todas las entradas de dominio de Purple)
Inicios de sesión simultáneos	Permitir (Allow)
Comportamiento de desconexión del controlador	Predeterminado (Default)
IP del cliente y VLAN	Meraki DHCP (modo NAT)
Detección de portadora de datos	Deshabilitado (Disabled)

En Servidores RADIUS (RADIUS Servers), agregue dos servidores de autenticación (primario y secundario) en el puerto 1812 con el secreto compartido de su portal de Purple. Agregue los servidores de contabilidad correspondientes en el puerto 1813. Establezca el intervalo provisional de contabilidad en 4 minutos, el tiempo de espera del servidor en 5 segundos y el recuento de reintentos en 3.

En Configuración avanzada de RADIUS (Advanced RADIUS Settings), establezca tanto Called-Station-ID como NAS-ID en Dirección MAC del AP (AP MAC address). Elimine cualquier otro valor de estos campos.

Paso 3: Configurar la página de inicio

Navegue a Inalámbrico > Página de inicio (Wireless > Splash Page). Ingrese la URL personalizada de la página de inicio (Custom Splash URL) desde su portal de Purple. Establezca el destino de redirección posterior a la página de inicio en la URL de su elección, generalmente el sitio web de su recinto o una página de destino promocional específica. Guarde los cambios.

Paso 4: Configurar PurpleConnex (SSID SecurePass)

Cree un nuevo SSID llamado PurpleConnex. Establezca la seguridad en WPA2 Enterprise. Deshabilite la red personal Wi-Fi (WPN). En servidores RADIUS, agregue rad1-secure.purple.ai y rad2-secure.purple.ai en el puerto 2083 con RadSec (RADIUS sobre TLS) habilitado y el secreto compartido radsec. Establezca el tiempo de inactividad de RADSec TLS en 15 minutos. Deshabilite el soporte de RADIUS CoA. Habilite el proxy RADIUS.

Navegue a Inalámbrico > Hotspot 2.0 (Wireless > Hotspot 2.0). Seleccione el SSID PurpleConnex y configúrelo de la siguiente manera:

Parámetro	Valor
Hotspot 2.0	Habilitado (Enabled)
Nombre del operador	PURPLE:GB
Tipo de red	Red pública gratuita (Free public network)
Lista de dominios	securewifi.purple.ai
OI del Consorcio de Roaming	5A03BA0000, 004096
Dominio NAI (NAI Realm)	securewifi.purple.ai (EAP-TTLS / PAP)

Paso 5: Validar y probar

Antes de declarar la implementación como completa, pruebe todo el recorrido del invitado desde un dispositivo de consumidor en un segmento de red separado. Verifique que la página de inicio se cargue correctamente, que todos los métodos de autenticación funcionen, que el acceso a la red posterior a la autenticación se otorgue en un plazo de 3 a 5 segundos y que los datos de la sesión aparezcan en el panel de analítica de Purple en un plazo de 5 minutos. Pruebe el flujo de reconexión automática de PurpleConnex descargando el perfil Passpoint y confirmando una reconexión fluida en una segunda visita.

Mejores prácticas

Segmentación de red y cumplimiento de PCI DSS. El tráfico de WiFi para invitados debe estar aislado en una VLAN dedicada, con reglas de firewall que eviten el movimiento lateral hacia los segmentos de la red corporativa. Si su recinto procesa datos de tarjetas de pago en la misma infraestructura de red física, se requiere un ejercicio formal de alcance de PCI DSS. El modo NAT de Meraki proporciona aislamiento de clientes a nivel de AP, pero la segmentación de VLAN en la capa de conmutación es el control adecuado para la gestión del alcance de PCI.

Gobernanza de datos de GDPR y CCPA. El Captive Portal de Purple presenta un mecanismo de consentimiento en el punto de autenticación, capturando la aceptación explícita (opt-in) para comunicaciones de marketing. Asegúrese de que la configuración de retención de datos de su portal de Purple se alinee con la política de gobernanza de datos de su organización. La plataforma de Purple admite de forma nativa las solicitudes de acceso de los interesados y los flujos de trabajo del derecho al olvido, lo cual es una ventaja de cumplimiento material sobre las soluciones de Captive Portal a medida.

Mantenimiento del Walled Garden. La lista de dominios del walled garden es un elemento de configuración vivo. La infraestructura de la plataforma y CDN de Purple puede cambiar con el tiempo, y un walled garden desactualizado dará como resultado una experiencia de página de inicio defectuosa. Suscríbase a las notas de la versión de Purple y revise la lista del walled garden como parte de su proceso estándar de gestión de cambios.

Redundancia y conmutación por error. Purple proporciona dos endpoints de servidor RADIUS tanto para el SSID de invitados como para PurpleConnex. Ambos deben estar siempre configurados. En caso de una interrupción de la plataforma de Purple, configure el comportamiento de desconexión del controlador de Meraki en Predeterminado (Default); esto permite que las sesiones autenticadas previamente continúen mientras las nuevas autenticaciones se ponen en cola para reintentar.

Wi-Fi 6 y optimización del rendimiento. Para recintos de alta densidad, como estadios y centros de conferencias, los puntos de acceso Wi-Fi 6 (802.11ax) de Meraki proporcionan el margen de rendimiento necesario para las sesiones simultáneas de invitados. La integración de Purple es independiente de la generación de hardware: la configuración de RADIUS y del Captive Portal es idéntica en todas las generaciones de productos de AP de Meraki.

Solución de problemas y mitigación de riesgos

La siguiente tabla resume los modos de fallo más comunes encontrados en las implementaciones de Meraki y Purple, sus causas raíz y la solución recomendada.

Síntoma	Causa raíz	Solución
La página de inicio no se carga (en blanco o rota)	Walled garden incompleto	Agregue todas las entradas de dominio de Purple a la lista blanca del walled garden
La autenticación se realiza correctamente pero no se otorga acceso a la red	Tiempo de espera de RADIUS demasiado bajo	Establezca el tiempo de espera del servidor en 5s y el recuento de reintentos en 3
La analítica no muestra datos por AP	NAS-ID / Called-Station-ID mal configurados	Establezca ambos campos en la dirección MAC del AP en la Configuración avanzada de RADIUS
Fallos de autenticación intermitentes en picos de carga	Un solo servidor RADIUS configurado	Agregue los endpoints RADIUS primario y secundario de Purple
PurpleConnex no se conecta automáticamente	Hotspot 2.0 mal configurado	Verifique la configuración de los OI del Consorcio de Roaming y el Dominio NAI
A los invitados recurrentes se les pide que se vuelvan a autenticar	SSID PurpleConnex no implementado	Implemente el SSID PurpleConnex con la configuración de Passpoint
No se captura el consentimiento de GDPR	Campos de consentimiento de la página de inicio deshabilitados	Habilite los campos de aceptación de marketing en el editor de la página de inicio del portal de Purple

Aleatorización de direcciones MAC. Los dispositivos iOS y Android modernos presentan direcciones MAC aleatorias de forma predeterminada. Esto afecta la capacidad de Purple para identificar a los visitantes recurrentes en el SSID de invitados. La solución PurpleConnex / SecurePass resuelve esto utilizando autenticación basada en credenciales en lugar de identificación basada en MAC. Para los recintos donde no es factible implementar PurpleConnex, la plataforma de Purple aplica coincidencias probabilísticas utilizando metadatos de sesión para mitigar parcialmente el impacto.

Compatibilidad de firmware de Meraki. Asegúrese de que sus AP de Meraki estén ejecutando una versión de firmware que admita las funciones Hotspot 2.0 y RadSec requeridas para PurpleConnex. Se recomienda el canal de firmware estable de Meraki para implementaciones de producción; el firmware beta no debe utilizarse en entornos de WiFi para invitados en vivo.

ROI e impacto comercial

El caso de negocio para implementar Purple en una infraestructura de Meraki está bien evidenciado por implementaciones en vivo en múltiples sectores verticales. Los siguientes resultados se extraen de estudios de caso publicados por Purple.

Organización	Sector	Resultado
Harrods	Retail de lujo	ROI de 57x en 600,000 inicios de sesión WiFi
AGS Airports	Viajes y transporte	ROI del 842% a través de ingresos por ancho de banda escalonado
McDonald's Bélgica	Restaurante de servicio rápido	Implementación en vivo de Purple + Cisco Meraki + Socialspot
Walmart Canadá	Retail de gran formato	WiFi para invitados a escala empresarial con Purple y Cisco
Miami HEAT (Kaseya Center)	Deportes y entretenimiento	290,000 conexiones, promedio de 28,000 por mes
c2c Rail	Transporte	81,601 usuarios de WiFi → ROI del 151%

El mecanismo de ROI es sencillo. Purple convierte los eventos de autenticación de WiFi para invitados en perfiles de datos de origen (first-party data): direcciones de correo electrónico, información demográfica, frecuencia de visitas, tiempo de permanencia y patrones de comportamiento. Estos datos se integran directamente en plataformas de CRM y automatización de marketing a través de los conectores de API de Purple, lo que permite campañas dirigidas que superan de manera demostrable a los datos de audiencia de terceros tanto en tasa de conversión como en costo por adquisición.

Para un hotel de 200 habitaciones que opera al 70% de ocupación con un promedio de 1.8 huéspedes por habitación, una implementación de Purple en una infraestructura de Meraki generalmente capturará entre 250 y 300 nuevos perfiles de datos de origen por día. Con una tasa de conversión de marketing por correo electrónico estándar de la industria del 3 al 5%, y un valor de reserva incremental promedio de £150, la atribución de ingresos anuales solo por la reactivación por correo electrónico generalmente supera el costo total de la licencia de la plataforma de Purple dentro del primer año operativo.

Las ganancias de eficiencia operativa derivadas del aprovisionamiento automatizado de Meraki son un beneficio secundario pero significativo. Para un operador de múltiples sitios que gestiona 50 ubicaciones, la reducción en el tiempo de configuración manual, de un estimado de 3 a 4 horas por sitio a menos de 30 minutos, representa un ahorro material en los costos de recursos de ingeniería.

Términos clave y definiciones

Captive Portal

A web-based authentication gateway that intercepts a guest device's initial HTTP request and redirects it to a login or terms-acceptance page before granting network access. In the Meraki-Purple integration, the captive portal is hosted by Purple and delivered via a custom splash URL configured in the Meraki dashboard.

IT teams encounter this when configuring the Splash Page settings in the Meraki dashboard. The choice between Click-through (terms acceptance only) and Sign-on (RADIUS authentication) determines the level of data capture and security the deployment provides.

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol (RFC 2865) that provides centralised authentication, authorisation, and accounting (AAA) for network access. In the Meraki-Purple integration, Purple operates RADIUS servers that receive authentication requests from Meraki APs on port 1812 and return Access-Accept or Access-Reject responses. Accounting data is sent to port 1813.

RADIUS is the backbone of the guest authentication flow. Network engineers need to configure the RADIUS server IP addresses, shared secret, and port numbers in the Meraki Access Control settings. Incorrect RADIUS configuration is the most common cause of guest authentication failure.

Walled Garden

A list of network destinations (IP addresses, domain names, or CIDR blocks) that a guest device is permitted to reach before completing captive portal authentication. In the Meraki-Purple integration, the walled garden must include all domains required by Purple's splash page — CDN assets, authentication provider endpoints, and the Purple platform itself.

IT teams must maintain this list as a living configuration item. An incomplete walled garden results in a broken splash page experience for guests. Purple publishes and maintains a current whitelist of required domains in their support documentation.

RadSec (RADIUS over TLS)

An extension to the RADIUS protocol (RFC 6614) that transports RADIUS messages over a TLS-encrypted TCP connection, providing confidentiality and integrity for authentication traffic. Purple's PurpleConnex SSID uses RadSec on port 2083, replacing the standard UDP transport used by the guest SSID RADIUS configuration.

RadSec is required for the PurpleConnex SecurePass SSID. Network engineers must enable the RadSec toggle in Meraki's RADIUS server configuration and use port 2083 rather than the standard 1812/1813. Failure to enable RadSec will prevent PurpleConnex authentication from functioning.

Hotspot 2.0 / Passpoint (IEEE 802.11u)

A Wi-Fi Alliance certification programme based on the IEEE 802.11u standard that enables automatic, secure network discovery and association. A device with a Passpoint profile will automatically connect to a compatible network without user intervention, using EAP-based authentication rather than a captive portal.

In the Meraki-Purple integration, Hotspot 2.0 is configured on the PurpleConnex SSID to enable seamless auto-reconnection for returning guests. This is particularly valuable in hospitality and retail environments where repeat authentication friction reduces guest satisfaction.

NAS-ID (Network Access Server Identifier)

A RADIUS attribute (Attribute 32) that identifies the network access server — in this context, the Meraki access point — that is sending the authentication request. Purple uses the NAS-ID to attribute guest sessions to specific physical access points, enabling floor-level location analytics.

This is one of the most commonly misconfigured parameters in Meraki-Purple deployments. It must be set to AP MAC address in the Meraki Advanced RADIUS Settings. Any other value (such as SSID name or a static string) will prevent Purple from generating per-AP analytics.

Meraki Dashboard API

A RESTful API provided by Cisco Meraki that allows programmatic access to the Meraki cloud management platform. It supports read and write operations across organisations, networks, devices, and configuration objects. Purple uses this API to import access point data and push SSID/RADIUS configuration during the provisioning phase.

IT teams need to generate an API key from the Meraki dashboard (Organisation > API & Webhooks) and provide it to the Purple Portal's Hardware Import Wizard. This key should be treated as a privileged credential and stored securely.

GDPR (General Data Protection Regulation)

EU Regulation 2016/679, which governs the collection, processing, and storage of personal data of EU residents. In the context of guest WiFi, GDPR requires that venues obtain explicit, informed consent before collecting personal data (such as email addresses) through a captive portal, and provide mechanisms for data subjects to access, correct, or delete their data.

Purple was among the first WiFi providers to achieve GDPR compliance. The Purple captive portal presents a consent mechanism at the point of authentication, and the platform supports data subject access requests and right-to-erasure workflows natively. IT teams should ensure that the Purple Portal's data retention settings align with their organisation's data governance policy.

PurpleConnex (SecurePass)

Purple's seamless reconnection solution, implemented as a second SSID configured with WPA2 Enterprise security, RadSec RADIUS transport, and Hotspot 2.0 (Passpoint) advertisement. Returning guests whose devices have downloaded a Purple Passpoint profile will automatically associate with PurpleConnex without seeing a captive portal.

PurpleConnex is deployed alongside the primary guest SSID and is invisible to first-time visitors. It resolves two key challenges: repeat authentication friction for returning guests, and MAC address randomisation (iOS 14+, Android 10+) which breaks MAC-based guest identification on the primary SSID.

Called-Station-ID (RADIUS Attribute 30)

A RADIUS attribute that identifies the access point or network access server that the client connected to, typically expressed as the AP's MAC address. Purple uses this attribute in conjunction with NAS-ID to map guest sessions to specific physical access points for location analytics.

Must be set to AP MAC address in Meraki's Advanced RADIUS Settings. This attribute works in tandem with NAS-ID — both must be correctly configured for Purple's floor-level analytics to function accurately.

Casos de éxito

A 250-room four-star hotel group with 12 properties across the UK has a fully deployed Cisco Meraki estate (MR46 and MR57 APs, MX68 security appliances). They currently offer open guest WiFi with no captive portal. The IT Director wants to implement Purple WiFi to capture guest email addresses for the hotel's CRM, comply with GDPR, and generate analytics on peak-hour network usage. The deployment must be completed with minimal disruption to existing guests and must not require on-site engineer visits to any of the 12 properties. How should this deployment be structured?

The deployment should proceed in three phases, leveraging the Meraki Dashboard API for remote, zero-touch provisioning across all 12 properties.

Phase 1: Provisioning (Day 1, remote) Generate a Meraki API key scoped to the hotel group's Meraki organisation. In the Purple Portal, use the Hardware Import Wizard with the Third Party API option to import all access points across all 12 networks in a single batch. Assign each network to the corresponding Purple venue. This operation typically completes in under 20 minutes for an estate of this size.

Phase 2: SSID and RADIUS Configuration (Days 1–2, remote via Meraki dashboard) For each of the 12 Meraki networks, configure the existing guest SSID with the Sign-on with my RADIUS server splash page type. Add Purple's primary and secondary RADIUS servers on ports 1812 and 1813 with the shared secret from the Purple Portal. Set captive portal strength to Block all access, enable the walled garden with Purple's domain whitelist, and configure the custom splash URL. Set NAS-ID and Called-Station-ID to AP MAC address. Because Meraki's dashboard supports configuration templates, a single template can be applied across all 12 networks simultaneously, reducing per-site configuration time to near zero.

Phase 3: PurpleConnex Deployment (Days 2–3, remote) Create the PurpleConnex SSID on each network with WPA2 Enterprise and RadSec RADIUS configuration. Enable Hotspot 2.0 with the Purple operator name and domain settings. This SSID is invisible to guests who have not previously authenticated — it will auto-connect returning guests silently on subsequent visits.

Validation: Test the full guest journey remotely using a 4G-connected mobile device at one property before rolling the configuration live across all 12. Monitor the Purple analytics dashboard for session data ingestion within the first 24 hours of go-live.

The entire deployment is achievable in 2–3 days of engineering time with zero on-site visits, leveraging Meraki's cloud management and Purple's API provisioning.

Notas de implementación: This approach is optimal because it exploits the core operational advantage of the Meraki and Purple integration: the ability to provision and configure an entire multi-site estate remotely via API. The use of Meraki configuration templates is the key efficiency multiplier — without templates, a 12-site deployment would require 12 separate manual configuration sessions. The phased approach (provisioning, then guest SSID, then PurpleConnex) is correct because it allows the team to validate the primary guest journey before adding the complexity of the Passpoint/SecurePass layer. An alternative approach — deploying both SSIDs simultaneously — is technically feasible but increases the blast radius of any misconfiguration. The zero-on-site-visit constraint is fully achievable with this architecture, which is a significant operational and cost advantage over competing solutions that require local controller access.

A 60,000-capacity football stadium uses Cisco Meraki MR45 access points throughout the concourse, seating bowl, and hospitality suites. They want to deploy Purple WiFi to capture fan data, run in-venue surveys during matches, and integrate with their existing Salesforce CRM. The primary concern is scale: on match days, up to 35,000 concurrent WiFi sessions are expected. The stadium's IT team is concerned about RADIUS authentication performance under peak load. How should the RADIUS configuration be optimised for high-concurrency environments?

For a high-concurrency stadium deployment, the RADIUS configuration requires specific attention to redundancy, timeout parameters, and session management.

RADIUS Server Configuration for Scale: Configure both Purple RADIUS endpoints (primary and secondary) on every Meraki AP and MX in the estate. This is non-negotiable for a stadium deployment — a single RADIUS server configuration will create a single point of failure that will manifest as authentication failures precisely at kick-off, when concurrent connection attempts peak.

Set the RADIUS server timeout to 5 seconds and retry count to 3. This gives each authentication attempt up to 15 seconds before failing over to the secondary server, which is sufficient for a cloud-hosted RADIUS service under normal conditions. Do not reduce the timeout below 5 seconds in a stadium environment — the additional latency from concurrent load means that aggressive timeout values will cause false failures.

Set the accounting interim interval to 4 minutes. This generates a RADIUS Accounting-Interim-Update message every 4 minutes per active session, which Purple uses to calculate dwell time. In a stadium with 35,000 concurrent sessions, this generates approximately 145 accounting messages per second — well within Purple's platform capacity.

SSID and Network Segmentation: Deploy the guest SSID on a dedicated VLAN with a sufficiently large DHCP scope. A /16 subnet (65,534 addresses) is recommended for a 60,000-capacity venue. Ensure the DHCP lease time is set to match the expected session duration — for a 2-hour match, a 3-hour lease is appropriate. Short lease times will cause unnecessary DHCP churn and add load to the authentication infrastructure.

Salesforce CRM Integration: Purple's platform supports native Salesforce connector integration. Configure the CRM connector in the Purple Portal to push new guest profiles and session events to Salesforce in real time. Map Purple's data fields (email, visit count, dwell time, authentication method) to the corresponding Salesforce Contact and Campaign Member objects. This enables the stadium's marketing team to trigger automated post-match email campaigns within minutes of the final whistle.

In-Venue Surveys: Purple's MicroSurvey feature can be triggered post-authentication, presenting a 1–3 question survey on the splash page redirect. For a stadium deployment, configure the survey to trigger for a random 20% sample of authenticated guests to avoid survey fatigue while maintaining statistical significance.

Notas de implementación: The stadium scenario tests understanding of RADIUS at scale, which is the most technically demanding aspect of the Purple-Meraki integration. The critical insight is that RADIUS authentication is a synchronous, per-session operation — at 35,000 concurrent sessions, even a small percentage of authentication failures or timeouts creates a visible guest experience degradation. The dual-server configuration and correct timeout settings are the primary risk mitigations. The DHCP scope sizing and lease time recommendation demonstrates network architecture depth that goes beyond the Purple-specific configuration — this is the kind of holistic thinking that distinguishes a senior network architect from a configuration technician. The Salesforce integration and survey sampling recommendations address the business requirements (CRM integration, fan data capture) with practical implementation detail.

Análisis de escenarios

Q1. A retail chain with 80 stores has deployed Cisco Meraki MR33 access points throughout their estate. They want to implement Purple WiFi but their security team has raised concerns about deploying an Open SSID for guest access. The security team argues that all SSIDs should use WPA2 encryption at minimum. How do you address this concern, and what is the correct security architecture for the guest WiFi deployment?

💡 Sugerencia:Consider the difference between link-layer encryption (WPA2) and application-layer authentication (captive portal + RADIUS). Also consider what the PurpleConnex SSID provides.

Mostrar enfoque recomendado

The security team's concern is valid in principle but reflects a conflation of two different security objectives. WPA2 encryption protects the radio link between the client device and the access point — it prevents eavesdropping on the wireless medium. However, for a public guest network, WPA2 Personal (PSK) provides minimal practical security because the pre-shared key is, by definition, publicly known to all guests. Any guest who knows the PSK can decrypt other guests' traffic using a passive capture attack.

The correct architecture is: deploy the guest SSID as Open (no WPA2) with a captive portal for authentication. This is the industry-standard approach for public guest WiFi because it allows the captive portal to function without requiring guests to know a password before they can reach the splash page. The security model relies on application-layer controls (HTTPS on the splash page, RADIUS authentication, VLAN isolation) rather than link-layer encryption.

For guests who require encrypted transport, the PurpleConnex SSID provides WPA2 Enterprise security with RadSec RADIUS — this is genuinely secure because each client receives a unique encryption key derived from their EAP credentials. Returning guests who have the PurpleConnex Passpoint profile will automatically connect to this encrypted SSID.

The complete security architecture is therefore: Open SSID for first-time guest onboarding (captive portal + RADIUS authentication + VLAN isolation) + WPA2 Enterprise PurpleConnex SSID for returning guests (RadSec + Passpoint). This satisfies both the guest experience requirement and the security team's encryption requirement for repeat visitors.

Q2. A conference centre is deploying Purple WiFi on their Meraki estate for the first time. Three weeks after go-live, the marketing team reports that the Purple analytics dashboard shows total session counts but no per-room or per-zone data — all sessions appear to be attributed to a single location. The network engineer who performed the configuration has left the organisation. What is the most likely cause, and how do you diagnose and resolve it?

💡 Sugerencia:Think about which RADIUS attribute Purple uses to map sessions to physical locations, and what the default Meraki configuration for that attribute is.

Mostrar enfoque recomendado

The most likely cause is that the NAS-ID and/or Called-Station-ID RADIUS attributes are not configured to use AP MAC address. When these fields are set to a static string, SSID name, or left at default, every access point in the estate sends the same identifier in its RADIUS messages. Purple's analytics engine receives identical location identifiers from all APs and cannot distinguish between them, resulting in all sessions being attributed to a single (or unknown) location.

Diagnosis: In the Meraki dashboard, navigate to Wireless > Access Control for the guest SSID. Scroll to Advanced RADIUS Settings. Check the values for Called-Station-ID and NAS-ID. If either field shows anything other than AP MAC address — such as SSID name, a static string, or multiple values — this is the root cause.

Resolution: Set both Called-Station-ID and NAS-ID to AP MAC address only. Remove any other values from these fields. Save the configuration. Note that this change takes effect for new sessions — existing active sessions will not be retroactively re-attributed. Within 5–10 minutes of the configuration change, new session data in the Purple analytics dashboard should begin showing per-AP attribution.

If the issue persists after correcting the RADIUS attribute configuration, verify that the Purple Portal has the correct AP MAC addresses imported and associated with the correct floor plan zones. If APs were imported before floor plans were configured, the MAC-to-zone mapping may need to be updated in the Purple Portal's venue management settings.

Q3. A 500-bed NHS hospital trust wants to deploy Purple WiFi on their existing Cisco Meraki infrastructure to provide patient and visitor WiFi. Key requirements are: GDPR compliance for data collection, content filtering to block inappropriate content on the patient network, seamless connectivity for long-stay patients (multi-day admissions), and integration with their existing patient engagement platform via API. What Purple features and Meraki configuration elements address each requirement?

💡 Sugerencia:Consider Purple's compliance features, Purple Shield DNS filtering, PurpleConnex for long-stay patients, and Purple's API/connector capabilities for the patient engagement platform integration.

Mostrar enfoque recomendado

Each requirement maps to a specific combination of Purple features and Meraki configuration:

GDPR Compliance: Purple's captive portal presents a consent mechanism at authentication, capturing explicit opt-in for data processing. The Purple Portal's data governance settings allow configuration of data retention periods aligned with NHS data governance policies. Purple supports data subject access requests and right-to-erasure natively. The splash page should be configured to present clear, plain-language consent language — not buried in terms and conditions — to meet the GDPR requirement for informed, unambiguous consent.

Content Filtering: Purple Shield is Purple's cloud-native DNS filtering service. It operates at the infrastructure level, filtering DNS queries before they resolve, and can be configured with category-based blocking (adult content, gambling, malware, etc.) appropriate for a patient environment. This is configured within the Purple Portal and applies to all authenticated sessions on the guest SSID without requiring additional hardware.

Seamless Connectivity for Long-Stay Patients: Deploy PurpleConnex with Hotspot 2.0 (Passpoint) configuration. Once a patient has authenticated once and downloaded the Passpoint profile, their device will auto-connect on subsequent associations — including after the device wakes from sleep, moves between wards, or reconnects after a brief disconnection. This eliminates the daily re-authentication friction that is a common complaint in hospital WiFi deployments.

Patient Engagement Platform Integration: Purple's platform exposes a REST API and supports pre-built connectors for major CRM and engagement platforms. Configure the Purple Portal's API connector to push authenticated session events (patient ID if captured at login, session start/end, ward-level location data) to the patient engagement platform in real time. If the engagement platform is not in Purple's pre-built connector library, the REST API allows custom integration development.

Conclusiones clave

✓The Purple and Meraki integration operates across two distinct layers: the Meraki Dashboard REST API for automated bulk provisioning of access points, and the Captive Portal API with RADIUS authentication (ports 1812/1813) for the live guest experience — understanding this separation is essential for both deployment planning and troubleshooting.
✓The three most critical configuration parameters are: NAS-ID and Called-Station-ID set to AP MAC address (required for per-zone analytics), RADIUS server timeout of 5 seconds with retry count of 3 (required for reliability under load), and a complete walled garden domain whitelist (required for the splash page to load correctly).
✓PurpleConnex (SecurePass) deploys a second WPA2 Enterprise SSID with RadSec RADIUS and Hotspot 2.0 (Passpoint/IEEE 802.11u), enabling returning guests to auto-reconnect without a captive portal — this also resolves the MAC address randomisation challenge introduced by iOS 14+ and Android 10+.
✓GDPR and CCPA compliance is built into Purple's captive portal by design, with explicit consent capture at authentication, data subject access request workflows, and configurable data retention — making Purple a materially lower compliance risk than bespoke captive portal solutions.
✓The business case is well-evidenced: Harrods achieved 57× ROI on 600,000 WiFi logins, AGS Airports achieved 842% ROI, and McDonald's Belgium, Walmart Canada, and the Miami HEAT are all live Cisco Meraki and Purple deployments at enterprise scale.
✓For multi-site deployments, the Meraki Dashboard API enables batch import of entire access point estates into the Purple Portal in a single operation, reducing a multi-day manual configuration exercise to under an hour — the operational efficiency gain is a significant secondary benefit beyond the guest intelligence value.
✓Network segmentation is a non-negotiable prerequisite: guest WiFi traffic must be isolated on a dedicated VLAN with firewall rules preventing lateral movement to corporate segments, and any PCI DSS scoping implications of shared physical infrastructure must be formally assessed before go-live.