dotdigital (anteriormente Dotmailer): Guía de integración, mejores prácticas y solución de problemas para usuarios de Purple AI

This guide provides Purple AI users — particularly IT managers, network architects, and CTOs at hotels, retail chains, stadiums, and conference centres — with a definitive technical reference for deploying and optimising the dotdigital (formerly Dotmailer) connector. It covers the end-to-end integration architecture, step-by-step configuration, GDPR-compliant data handling, automation programme design, and a structured troubleshooting framework. Organisations that implement this integration correctly convert guest WiFi logins into a high-value, consent-gated marketing database that drives measurable revenue outcomes.

📖 11 min read📝 2,662 words🔧 2 examples❓ 4 questions📚 10 key terms

🎧 Listen to this Guide

View Transcript

Welcome to the Purple Intelligence Briefing. I'm your host, and today we're getting into the practical detail of one of the most commonly deployed connectors in the Purple ecosystem — dotdigital, formerly known as Dotmailer. If you're an IT manager, a network architect, or a CTO responsible for a hotel group, a retail estate, a stadium, or a conference centre, this episode is built for you.

Over the next ten minutes, we're going to cover exactly what this integration does, how to set it up correctly, the best practices that separate a high-performing deployment from a mediocre one, and the troubleshooting scenarios that trip up even experienced teams. Let's get into it.

[SECTION: CONTEXT AND WHY THIS MATTERS]

First, let's establish what we're actually talking about. Purple is an enterprise guest WiFi intelligence platform. When a visitor connects to your WiFi — whether they're checking in at a hotel, browsing a retail floor, or arriving at a conference centre — Purple's captive portal captures their consent and profile data. That data is the raw material for everything that follows.

dotdigital is a cross-channel marketing automation platform. It handles email, SMS, push notifications, WhatsApp, and more. It's used by retailers, hospitality brands, and enterprise organisations to run sophisticated, personalised marketing programmes at scale.

The Purple-dotdigital connector bridges these two systems. The moment a guest authenticates on your WiFi and opts in to marketing communications, Purple pushes their profile data — name, email, mobile number, postcode, date of birth, gender — directly into a dotdigital address book. From there, dotdigital's automation engine takes over, triggering welcome journeys, re-engagement campaigns, loyalty programme invitations, and much more.

The commercial case is compelling. Harrods, the luxury London retailer, built a database of 3.6 million contacts through this kind of WiFi-driven data capture. In a single twelve-month period, 581,000 unique individuals logged on to their in-store WiFi. Of those, 38 percent — over 220,000 people — opted in to marketing. The downstream revenue from that opted-in cohort represented a 54 times return on their Purple investment. That's not a theoretical projection. That's a documented outcome.

[SECTION: TECHNICAL DEEP-DIVE]

Now let's talk architecture. The integration is a server-to-server API connection. Purple acts as the data producer; dotdigital acts as the consumer. Authentication uses dotdigital's standard Basic Auth mechanism — an API user account with a dedicated email address and password, paired with a region-specific API endpoint.

The endpoint matters. dotdigital operates across multiple regional data centres, and your API endpoint will be specific to your account's region. You retrieve this from Account Settings, then Access, within the dotdigital platform. Getting this wrong is the single most common cause of connector verification failures, so it's worth double-checking before you begin.

Within Purple, the connector is configured under Management, then Connectors. You can deploy it at two levels: customer level, which applies the connector across your entire Purple account, or venue level, which allows you to route different venues to different dotdigital address books. For a hotel group with multiple properties, venue-level configuration is almost always the right choice — it gives you clean segmentation from the outset.

The data payload that Purple sends to dotdigital on each new authenticated user includes eight fields: first name, last name, user ID, email address, mobile number, gender, postcode, and date of birth. Critically — and this is non-negotiable from a GDPR standpoint — data is only transmitted when the user has explicitly consented to receive marketing communications. Purple enforces this at the splash page level; no consent, no data push.

On the dotdigital side, contacts land in the address book you specify during connector setup. From there, you can enrol them in automation programmes — what dotdigital calls Programs. A well-designed welcome programme might send an immediate confirmation email, follow up with a venue guide or offer 24 hours later, and then trigger a re-engagement campaign if the contact hasn't returned within 30 days. All of this is configurable within dotdigital's Program Builder without any additional development work.

For organisations with more complex requirements, dotdigital's API supports custom data fields, contact scoring, event-based triggers, and webhook callbacks. If you're running a loyalty programme — as Harrods does — you can use the splash page's custom question feature to capture intent, then pass that signal through to dotdigital for segmentation. The contact's WiFi login data pre-populates your loyalty sign-up form, removing friction and significantly improving conversion rates.

From a compliance standpoint, both platforms carry strong credentials. Purple is GDPR and CCPA compliant by design. dotdigital operates as a data processor under GDPR, with documented technical and organisational measures in place. The integration supports double opt-in workflows, consent tracking, and suppression list management — all of which are essential for organisations operating across UK and EU jurisdictions.

[SECTION: IMPLEMENTATION RECOMMENDATIONS AND PITFALLS]

Let me give you the practical recommendations that make the difference between a deployment that delivers return on investment and one that sits idle.

First: plan your address book taxonomy before you connect anything. In dotdigital, address books are your primary segmentation layer. If you're operating multiple venues, create a dedicated address book per venue, or at minimum per venue category — hotels, restaurants, retail. Retrofitting this structure after thousands of contacts have been imported is painful and error-prone.

Second: configure your splash page marketing consent checkbox carefully. The wording matters both for conversion rates and for legal compliance. Under UK GDPR and the Privacy and Electronic Communications Regulations, consent must be freely given, specific, informed, and unambiguous. A pre-ticked checkbox does not meet this standard. Purple's splash page builder gives you full control over this language — use it deliberately.

Third: build your automation programmes before you go live with the connector. There's no value in collecting opted-in contacts if they sit in an address book with no programme attached. At minimum, deploy a three-step welcome journey: an immediate welcome email confirming their WiFi access, a follow-up with a relevant offer or content piece 48 hours later, and a re-engagement trigger at 30 days for contacts who haven't returned.

Fourth: monitor your deliverability metrics from day one. dotdigital provides detailed reporting on open rates, click-through rates, bounces, and unsubscribes. A bounce rate above two percent or an unsubscribe rate above 0.5 percent on a welcome series is a signal that either your consent language is misleading or your email content isn't meeting expectations. Address this early — inbox providers use engagement signals to determine whether your domain ends up in the inbox or the spam folder.

Fifth: implement the dotdigital unsubscribe webhook back to Purple. When a contact unsubscribes in dotdigital, that suppression should be reflected in Purple's records. Without this bidirectional sync, you risk re-adding a suppressed contact to dotdigital on their next WiFi login — a GDPR compliance risk and a fast route to deliverability problems.

Now, the pitfalls. The most common issue we see is connector verification failures caused by incorrect API endpoint URLs. Always retrieve the endpoint directly from your dotdigital account — do not guess or copy from documentation examples. The second most common issue is contacts not appearing in dotdigital despite successful connector setup. In almost every case, this traces back to the marketing consent checkbox not being enabled on the splash page. Check this first. The third issue is duplicate contacts, which occurs when the same email address is submitted across multiple WiFi sessions. dotdigital handles this through its deduplication logic, but you need to ensure that your address book settings are configured to merge on email address rather than create new records.

[SECTION: RAPID-FIRE Q&A]

Let me run through some of the questions we hear most frequently.

Can I connect multiple venues to different dotdigital address books? Yes. Configure the connector at venue level within Purple's Management section, and assign each venue to its own address book in dotdigital.

Does the integration support SMS as well as email? The data payload includes mobile number, so yes — once the contact is in dotdigital, you can use their mobile number for SMS campaigns through dotdigital's SMS channel. Ensure you have the appropriate consent language on your splash page to cover SMS marketing.

What happens if a guest connects but doesn't opt in to marketing? Purple captures the session data for analytics purposes, but does not push any personal data to dotdigital. The guest's visit contributes to your footfall and dwell time analytics within Purple, but they do not enter your marketing database.

Is the integration real-time? Yes. The data push to dotdigital occurs at the point of WiFi authentication, not in batches. This means a welcome email can be triggered within minutes of a guest connecting — which is a significant advantage for time-sensitive offers.

[SECTION: SUMMARY AND NEXT STEPS]

Let me close with the key points to take away from this briefing.

The Purple-dotdigital integration is a production-ready, consent-gated data pipeline that converts WiFi logins into addressable marketing contacts. The setup is straightforward — four configuration fields and a connector verification — but the value is determined entirely by what you build on top of it in dotdigital.

The organisations that extract the most value are those that invest in address book taxonomy, automation programme design, and deliverability management before they go live. The Harrods example — 54 times return on investment from a WiFi-driven email programme — is achievable, but it requires deliberate programme design, not just a connected API.

Your immediate next steps: audit your dotdigital account structure, define your address book taxonomy, draft your welcome automation programme, and review your splash page consent language. Then connect the integration, verify it, and go live.

If you need to go deeper on any of these areas, the Purple support documentation covers the connector configuration in detail, and dotdigital's developer hub provides full API reference documentation for teams building custom integrations.

Thank you for listening to the Purple Intelligence Briefing. We'll be back with more technical guidance for venue operators and IT teams shortly.

Resumen ejecutivo

La plataforma de Purple AI captura datos de origen de los invitados en el punto de autenticación WiFi en hoteles, propiedades comerciales, estadios y recintos del sector público. El conector de dotdigital (anteriormente conocido como Dotmailer) transforma esa captura de datos sin procesar en un flujo de automatización de marketing de nivel de producción. Cuando un invitado se conecta a su WiFi y da su consentimiento para recibir comunicaciones de marketing, Purple envía su perfil a una libreta de direcciones designada de dotdigital en tiempo real. A partir de ese momento, el motor de automatización de dotdigital puede activar recorridos de bienvenida, invitaciones a programas de lealtad, campañas de reactivación y comunicaciones omnicanal a través de correo electrónico, SMS y notificaciones push.

El caso comercial está bien documentado. Harrods construyó una base de datos de 3.6 millones de contactos a través de la captura de datos impulsada por WiFi y logró un retorno de 54 veces su inversión en Purple en un solo año. AGS Airports generó un ROI del 842 %. El Aeropuerto de Bruselas Sur Charleroi registró un ROI del 10,630 % utilizando las MicroSurveys de Purple en combinación con la automatización de marketing posterior. Estos resultados no son excepcionales; son el resultado esperado de una integración bien configurada e implementada con un diseño de programa deliberado.

Esta guía proporciona la profundidad técnica necesaria para implementar, optimizar y solucionar problemas de la integración de Purple y dotdigital a escala empresarial. Está estructurada para el profesional de TI que necesita implementar una solución este trimestre, no evaluar una el próximo año.

Análisis técnico detallado

Arquitectura de integración

El conector de Purple y dotdigital opera como una integración de API REST de servidor a servidor. Purple funciona como el productor de datos y dotdigital como el consumidor. La conexión se autentica mediante el mecanismo Basic Auth de dotdigital: una cuenta de usuario de API dedicada (dirección de correo electrónico y contraseña) creada dentro de la plataforma de dotdigital, combinada con una URL de endpoint de API específica de la región.

La arquitectura es unidireccional de forma predeterminada: Purple envía los registros de contactos a dotdigital en el punto de autenticación WiFi. Para las organizaciones que requieren sincronización bidireccional (por ejemplo, para reflejar las cancelaciones de suscripción o las actualizaciones de la lista de supresión en Purple), esto requiere una configuración adicional a través del marco de webhooks de dotdigital.

Componente	Función	Notas
Captive Portal de Purple	Autenticación de invitados y captura de consentimiento	Página de inicio (splash page) presentada en el inicio de sesión WiFi
Motor de conectores de Purple	Transformación de datos y envío de API	Configurado en Administración > Conectores
API REST de dotdigital	Ingesta de contactos y gestión de libretas de direcciones	Se requiere un endpoint específico de la región
Libreta de direcciones de dotdigital	Capa de almacenamiento y segmentación de contactos	Una o más libretas por recinto/propiedad
Program Builder de dotdigital	Ejecución de programas de automatización	Se activa al agregar un contacto a la libreta de direcciones

Carga útil de datos y mapeo de campos

Purple transmite ocho campos de datos a dotdigital por cada invitado que da su consentimiento. Estos campos se mapean directamente al modelo de datos de contacto estándar de dotdigital y no requieren configuración de campos personalizados para implementaciones básicas.

Nombre del campo	Tipo de datos	Descripción
`firstName`	Cadena (String)	Nombre del invitado
`lastName`	Cadena (String)	Apellido del invitado
`userID`	Entero (Integer)	Identificador de usuario interno de Purple
`email`	Cadena (String)	Dirección de contacto principal; utilizada como clave de deduplicación
`mobile`	Cadena (String)	Número de teléfono móvil (se recomienda el formato E.164)
`gender`	Cadena (String)	Género autodeclarado desde la página de inicio
`postcode`	Cadena (String)	Código postal; permite la segmentación geográfica
`dateOfBirth`	Cadena (String)	Formato: AAAA-MM-DD; permite la segmentación por rango de edad y activadores de cumpleaños

La transmisión de datos está restringida por el consentimiento a nivel de plataforma. Purple no enviará un registro de contacto a dotdigital a menos que el invitado haya optado explícitamente por recibir comunicaciones de marketing a través de la casilla de verificación de consentimiento en la página de inicio. Esta es una aplicación estricta (no una opción configurable) y es el mecanismo principal mediante el cual la integración mantiene el cumplimiento del GDPR del Reino Unido, el Reglamento General de Protección de Datos de la UE y la CCPA.

Autenticación y configuración del endpoint

dotdigital utiliza la autenticación básica HTTP para su API REST. Las credenciales consisten en una dirección de correo electrónico y una contraseña de usuario de la API, que deben crearse como un usuario dedicado dentro de la cuenta de dotdigital, no como el inicio de sesión de la cuenta principal. La URL del endpoint de la API es específica de la cuenta y depende de la región. Se obtiene en Configuración de la cuenta > Acceso (Account Settings > Access) dentro de la plataforma de dotdigital. Un endpoint típico tiene el formato https://r1-api.dotdigital.com para las cuentas de la región uno.

Esta especificidad del endpoint es la fuente más común de fallas en la verificación del conector. Los equipos que intenten usar una URL genérica o de ejemplo de la documentación encontrarán errores de autenticación. Recupere siempre el valor del endpoint directamente de la cuenta de dotdigital en uso.

Niveles de implementación del conector

Purple admite dos niveles de implementación para el conector de dotdigital:

El nivel de cliente aplica la configuración del conector en toda la cuenta de Purple, enrutando a todos los invitados que dan su consentimiento de todos los recintos a una única libreta de direcciones de dotdigital. Esto es adecuado para operadores de un solo recinto u organizaciones con un conjunto de recintos homogéneo.

El nivel de recinto permite mapear cada recinto individual a una libreta de direcciones de dotdigital distinta. Esta es la configuración recomendada para operadores de múltiples propiedades (grupos hoteleros, cadenas minoristas, operadores de estadios) donde se requiere segmentación a nivel de recinto para marketing dirigido, ofertas localizadas o identidades de marca separadas.

Guía de implementación

Paso 1: Prepare su cuenta de dotdigital

Antes de configurar el conector de Purple, complete lo siguiente en su cuenta de dotdigital. Navegue hasta Configuración de la cuenta (Account Settings) y cree un nuevo usuario de API con una dirección de correo electrónico dedicada y una contraseña segura. Registre la URL del endpoint de la API que se muestra en la parte superior de la página de Acceso (Access). Cree la libreta o libretas de direcciones que recibirán los contactos de Purple (se recomienda una por recinto para implementaciones de múltiples propiedades). Opcionalmente, cree campos de datos personalizados en dotdigital si tiene la intención de capturar atributos adicionales más allá de los ocho campos estándar de Purple.

Paso 2: Configure el conector de Purple

Dentro de la plataforma de Purple, navegue hasta Administración > Conectores (Management > Connectors). Localice el conector de dotdigital y seleccione Agregar (Add). Complete los cuatro campos obligatorios: el nombre del conector (una etiqueta descriptiva para su referencia), el correo electrónico de la API de dotdigital, la contraseña de la API de dotdigital y la URL del endpoint de la API de dotdigital. Seleccione Verificar (Verify). Tras una verificación exitosa, aparecerá un menú desplegable con las libretas de direcciones disponibles en su cuenta de dotdigital. Seleccione la libreta de direcciones de destino y guarde la configuración.

Para implementaciones en múltiples recintos, repita este proceso a nivel de recinto para cada propiedad, asignando cada una a su libreta de direcciones designada.

Paso 3: Configure el mecanismo de consentimiento de la página de inicio

La casilla de verificación de consentimiento de marketing en su página de inicio de Purple es la puerta de entrada a toda la integración. Navegue hasta la configuración de su página de inicio y asegúrese de que la casilla de verificación de suscripción de marketing esté habilitada y claramente etiquetada. El lenguaje de consentimiento debe ser explícito, específico e inequívoco según el Artículo 7 del GDPR del Reino Unido. Un ejemplo que cumple con la normativa: "Acepto recibir comunicaciones de marketing de [Nombre de la organización] sobre ofertas, eventos y noticias. Puede darse de baja en cualquier momento". No marque esta casilla previamente.

Si su programa de marketing incluye SMS, asegúrese de que el lenguaje de consentimiento cubra explícitamente las comunicaciones por SMS. Se permite una sola casilla de verificación que cubra tanto el correo electrónico como los SMS, siempre que el lenguaje sea claro.

Paso 4: Construya sus programas de automatización de dotdigital

Implemente programas de automatización en dotdigital antes de que el conector entre en funcionamiento. Como mínimo, configure un programa de bienvenida que se active al agregar un contacto a la libreta de direcciones. Un recorrido de bienvenida recomendado de tres etapas:

Inmediato (0 minutos): Correo electrónico de bienvenida confirmando el acceso WiFi, con una introducción de marca a su recinto o servicios.
Día 2 (48 horas): Correo electrónico de seguimiento con una oferta relevante, guía del recinto o pieza de contenido adaptada al contexto del invitado.
Día 30 (reactivación): Correo electrónico automatizado de reactivación para los contactos que no han regresado, con un incentivo para volver a visitar.

Para la integración de programas de lealtad, utilice el Program Builder de dotdigital para inscribir a los contactos que cumplan con criterios específicos (por ejemplo, contactos que respondieron afirmativamente a una pregunta personalizada en la página de inicio sobre su interés en el programa de lealtad).

Paso 5: Configure la sincronización de supresión bidireccional

Configure un webhook de dotdigital para notificar a Purple cuando un contacto se dé de baja. Esto garantiza que un contacto suprimido no se vuelva a agregar a dotdigital en su próximo inicio de sesión WiFi. Sin este paso, la integración está técnicamente incompleta desde el punto de vista del cumplimiento del GDPR.

Paso 6: Valide y ponga en marcha

Realice una prueba de extremo a extremo autenticando un dispositivo de prueba en el WiFi, completando la página de inicio con una dirección de correo electrónico de prueba y el consentimiento de marketing, y verificando que el contacto aparezca en la libreta de direcciones correcta de dotdigital en un plazo de dos a tres minutos. Confirme que el programa de automatización de bienvenida se active correctamente. Documente los resultados de la prueba y proceda a la implementación en producción.

Mejores prácticas

Arquitectura de consentimiento

La calidad de su base de datos de suscritos es una función directa de su arquitectura de consentimiento. Las organizaciones que invierten en un lenguaje de consentimiento claro y honesto (incluso si reduce marginalmente las tasas de suscripción) construyen listas de contactos más comprometidas y de mayor valor. Una tasa de suscripción del 30 % a partir de un mecanismo de consentimiento transparente superará consistentemente a una tasa de suscripción del 60 % de uno ambiguo o engañoso, porque la primera cohorte genuinamente quiere saber de usted. Harrods logró una tasa de suscripción del 38 % de 581,000 usuarios de WiFi, una tasa consistente con un lenguaje de consentimiento transparente y de intercambio de valor.

Taxonomía de la libreta de direcciones

Diseñe la estructura de su libreta de direcciones de dotdigital antes de conectar Purple. Para un grupo hotelero que opera 20 propiedades, esto podría significar 20 libretas de direcciones específicas del recinto, más una libreta consolidada maestra para campañas entre propiedades. Para una cadena minorista, podría significar libretas segmentadas por región o formato de tienda. El principio clave es que la estructura de la libreta de direcciones determina su capacidad de segmentación posterior; modificarla después de que se han recopilado los datos es costoso y perjudicial.

Profundidad del programa de automatización

Las implementaciones más efectivas de Purple y dotdigital utilizan toda la capacidad de programas de dotdigital: recorridos de bienvenida, campañas de cumpleaños activadas por el campo dateOfBirth, secuencias de reactivación para contactos inactivos y encuestas posteriores a la visita. El campo postcode permite la segmentación geográfica para ofertas localizadas. El campo gender permite la personalización demográfica. El campo dateOfBirth permite la segmentación por rango de edad y los activadores de cumpleaños. Utilice los ocho campos: representan una rica base de segmentación que la mayoría de las organizaciones subutilizan.

Gestión de la capacidad de entrega

Supervise el panel de capacidad de entrega de dotdigital semanalmente durante los primeros 90 días de implementación. Puntos de referencia clave: tasa de apertura superior al 20 %, tasa de clics superior al 2 %, tasa de rebote inferior al 2 %, tasa de cancelación de suscripción inferior al 0.5 %. Si las tasas de rebote son elevadas, implemente el flujo de trabajo de doble suscripción (double opt-in) de dotdigital para verificar las direcciones de correo electrónico antes de que ingresen a su base de datos activa. Esto es particularmente relevante para recintos con alto tráfico transitorio (aeropuertos, estaciones de tren, centros de conferencias) donde los invitados pueden ingresar direcciones de correo electrónico temporales o incorrectas.

Cumplimiento de GDPR y PECR

La integración está diseñada para cumplir con la normativa de forma predeterminada, pero el cumplimiento es una responsabilidad compartida. Purple aplica el consentimiento en la capa de captura de datos; dotdigital lo aplica en la capa de comunicaciones. Su organización es responsable del lenguaje de consentimiento en la página de inicio, el contenido de las comunicaciones de marketing y el mantenimiento de las listas de supresión. Realice una Evaluación de Impacto de Protección de Datos antes de implementar la integración en jurisdicciones cubiertas por el GDPR del Reino Unido o el GDPR de la UE, particularmente para organizaciones del sector público sujetas a obligaciones adicionales bajo la Ley de Protección de Datos de 2018.

Solución de problemas y mitigación de riesgos

Fallas en la verificación del conector

El problema de implementación más frecuente. Causado en la mayoría de los casos por una URL de endpoint de API incorrecta. Resolución: inicie sesión en dotdigital, navegue hasta Configuración de la cuenta > Acceso (Account Settings > Access) y copie la URL del endpoint exactamente como se muestra. Asegúrese de que no se incluya una barra diagonal final ni espacios en blanco. Verifique que las credenciales de usuario de la API sean para una cuenta de usuario de API dedicada, no para el inicio de sesión de la cuenta principal. Si la verificación sigue fallando, confirme que la cuenta de dotdigital tenga habilitado el acceso a la API (esta es una función que puede necesitar ser activada por el soporte de dotdigital para algunos niveles de cuenta).

Los contactos no aparecen en dotdigital

Si el conector se verifica correctamente pero los contactos no aparecen en la libreta de direcciones de destino, la causa principal es que la casilla de verificación de consentimiento de marketing no está habilitada en la página de inicio. Purple no transmitirá datos sin consentimiento explícito. Las causas secundarias incluyen que el conector esté configurado en el nivel incorrecto (cliente frente a recinto) o que el ID de la libreta de direcciones haya cambiado desde que se guardó el conector. Resolución: verifique la configuración de consentimiento de la página de inicio, confirme el nivel del conector y vuelva a verificar el conector para actualizar la selección de la libreta de direcciones.

Registros de contactos duplicados

Ocurre cuando se envía la misma dirección de correo electrónico en múltiples sesiones WiFi, generalmente en recintos de alto tráfico. Resolución: asegúrese de que la libreta de direcciones de dotdigital esté configurada para actualizar los contactos existentes cuando coincida la dirección de correo electrónico en lugar de crear nuevos registros. Esto se controla dentro de la configuración de importación de contactos de dotdigital. Además, revise si el conector de Purple está configurado tanto a nivel de cliente como de recinto para el mismo recinto (una configuración dual resultará en envíos duplicados).

Campos de datos faltantes

Si los contactos aparecen en dotdigital pero ciertos campos están vacíos, la causa más probable es que los invitados no completaron esos campos en la página de inicio. Purple solo transmite los campos que se proporcionaron durante la autenticación. Para campos opcionales como el número de teléfono móvil o la fecha de nacimiento, algunos invitados se negarán a proporcionarlos. Si la integridad de campos específicos es fundamental para su estrategia de segmentación, considere hacer que esos campos sean obligatorios en la página de inicio, pero tenga en cuenta que cada campo obligatorio adicional reducirá su tasa de conversión de suscripción general.

No se respeta la supresión de GDPR

Si los contactos dados de baja se vuelven a agregar a dotdigital en inicios de sesión WiFi posteriores, no se ha configurado el webhook de supresión bidireccional. Este es un riesgo de cumplimiento. Resolución: configure un webhook de dotdigital que se active en eventos de cancelación de suscripción y actualice el registro de contacto correspondiente en Purple. Consulte la documentación para desarrolladores de dotdigital para obtener orientación sobre la configuración de webhooks.

Marco de mitigación de riesgos

Riesgo	Probabilidad	Impacto	Mitigación
Endpoint de API incorrecto	Alta	Medio	Recuperar el endpoint directamente de la cuenta de dotdigital
Casilla de consentimiento deshabilitada	Media	Alto	Incluir en la lista de verificación previa al lanzamiento; probar con un dispositivo real
Contactos duplicados	Media	Bajo	Configurar la deduplicación basada en correo electrónico en dotdigital
Supresión no sincronizada	Baja	Alto	Implementar el webhook de cancelación de suscripción antes de la puesta en marcha
Integridad de los campos de datos	Alta	Bajo	Establecer los requisitos de los campos según las necesidades de segmentación
Exposición de credenciales de API	Baja	Alto	Usar un usuario de API dedicado; rotar las credenciales trimestralmente

ROI e impacto comercial

Medición del éxito

La integración de Purple y dotdigital ofrece valor en dos dimensiones distintas: crecimiento de la base de datos y atribución de ingresos. El crecimiento de la base de datos se mide por la cantidad de nuevos contactos suscritos agregados por mes, la tasa de suscripción como porcentaje del total de autenticaciones WiFi y la tasa de integridad de los datos de contacto (porcentaje de contactos con los ocho campos completados). La atribución de ingresos se mide mediante el seguimiento de compras, inscripciones a programas de lealtad u otros eventos de conversión que se pueden vincular a los contactos que ingresaron a la base de datos a través del inicio de sesión WiFi.

La suite de informes de dotdigital proporciona análisis a nivel de campaña (tasas de apertura, tasas de clics, tasas de conversión) que se pueden utilizar para calcular la contribución a los ingresos de cada programa de automatización. El panel de análisis de Purple proporciona los datos de tráfico y autenticación necesarios para calcular el costo por contacto adquirido.

Puntos de referencia y resultados esperados

Basado en implementaciones documentadas en todo el entorno de Purple:

Tipo de recinto	Tasa de suscripción típica	Plazo esperado de ROI	Impulsor clave de ingresos
Comercio minorista de lujo	35–45 %	6–12 meses	Conversión del programa de lealtad
Hotel (mercado medio)	25–35 %	12–18 meses	Reactivación de reservas directas
Aeropuerto / Centro de transporte	15–25 %	18–24 meses	Ventas adicionales de comercio minorista y alimentos y bebidas
Estadio / Recinto de eventos	20–30 %	12–18 meses	Ventas adicionales de mercancía y boletos
Centro de conferencias	30–40 %	6–12 meses	Nueva reserva de eventos y patrocinio

Consideraciones de costo-beneficio

El costo marginal del conector de dotdigital dentro de Purple es bajo en relación con el potencial de ingresos. La inversión principal se encuentra en el diseño del programa y la creación de contenido: los recorridos de automatización, las plantillas de correo electrónico y la lógica de segmentación que determinan la eficacia con la que se monetiza la base de datos de contactos. Las organizaciones que tratan la integración como un canal de datos de "configurar y olvidar" verán retornos modestos. Aquellas que invierten en la optimización continua del programa (pruebas A/B de líneas de asunto, refinamiento de la segmentación, ampliación de la profundidad de la automatización) verán retornos consistentes con los puntos de referencia de Harrods y AGS Airports documentados anteriormente.

Una regla general práctica: por cada 10,000 contactos suscritos adquiridos a través de WiFi, un programa de dotdigital bien configurado debería generar ingresos incrementales medibles dentro de los 90 días posteriores a la implementación, asumiendo una tasa de apertura mínima del 20 % y una tasa de clics del 2 % en la serie de bienvenida.

Key Terms & Definitions

Captive Portal

A web page presented to a guest before they are granted access to a WiFi network. Purple's captive portal — also called a splash page — is the interface through which guests authenticate, provide profile data, and give marketing consent. It is the entry point for all data flowing into the dotdigital integration.

IT teams encounter this during network configuration and splash page design. The captive portal's consent checkbox is the legal and technical gateway to the entire marketing automation pipeline.

Address Book (dotdigital)

A named list of contacts within dotdigital, analogous to a mailing list or CRM segment. Address books are the primary organisational unit in dotdigital and serve as the target destination for Purple's data push. Automation programmes are triggered by contact addition to a specific address book.

The address book taxonomy — how many books, how named, at what level — is the most consequential architectural decision in a multi-venue deployment. It determines segmentation capability for all downstream marketing activity.

Automation Programme (dotdigital)

A configured sequence of automated actions in dotdigital, triggered by a defined event such as a contact being added to an address book. Programmes can include email sends, SMS messages, wait periods, conditional branches, and contact scoring updates. They are the mechanism through which Purple's data capture is converted into marketing communications.

IT teams are responsible for ensuring the connector triggers programme enrolment correctly. Marketing teams design the programme content. The 'Include contacts added via API' setting is a common configuration oversight that prevents programme triggering.

API Endpoint (dotdigital)

The base URL for dotdigital's REST API, specific to the regional data centre assigned to each account. It takes the form `https://r{n}-api.dotdigital.com` where `{n}` is the region number. It is retrieved from Account Settings > Access within the dotdigital platform.

This is the single most common source of connector verification failures. It must be retrieved directly from the dotdigital account — it cannot be guessed or copied from generic documentation.

Consent-Gated Data Push

A data transmission mechanism that only activates when explicit user consent has been recorded. In the Purple-dotdigital integration, Purple will only push a contact record to dotdigital if the guest has ticked the marketing consent checkbox on the splash page. This is a platform-level enforcement, not a configurable option.

This mechanism is the primary GDPR compliance control in the integration. It ensures that only genuinely opted-in contacts enter the marketing database, protecting the organisation from regulatory risk and protecting deliverability from low-engagement contacts.

Double Opt-In

A two-stage consent verification process in which a contact, after initially opting in, receives a confirmation email and must click a link to verify their email address and confirm their subscription. dotdigital supports double opt-in natively. It converts contacts from 'Pending' to 'Subscribed' status and provides an additional layer of consent documentation.

Recommended for venues with high transient footfall — airports, conference centres, train stations — where guests may enter incorrect or temporary email addresses. Double opt-in reduces bounce rates and improves deliverability, at the cost of a lower initial conversion rate.

Suppression List

A list of email addresses or contacts that must not receive marketing communications, typically because they have unsubscribed, complained, or been identified as invalid. dotdigital maintains suppression lists automatically. The Purple-dotdigital integration requires a webhook to sync suppressions back to Purple, preventing re-addition of suppressed contacts on subsequent WiFi logins.

Failure to implement bidirectional suppression sync is a GDPR compliance risk and a deliverability risk. It is a mandatory configuration step in any production deployment.

Venue-Level Connector

A Purple connector configuration scoped to a single venue, as opposed to a customer-level configuration that applies across the entire Purple account. Venue-level connectors allow different venues to be routed to different dotdigital address books, enabling venue-specific segmentation and personalisation.

Essential for multi-property operators. Hotel groups, retail chains, and stadium operators should always use venue-level configuration to maintain clean data segmentation across their estate.

First-Party Data

Data collected directly from individuals by the organisation that will use it for marketing, with the individual's knowledge and consent. WiFi login data captured through Purple's captive portal is first-party data. It is distinct from third-party data (purchased lists) and second-party data (data shared by partners). First-party data is the most valuable and most compliant form of marketing data in the post-cookie, post-GDPR landscape.

The strategic value of the Purple-dotdigital integration is that it generates high-quality first-party data at scale, from physical venue visits. This data is not available through any digital marketing channel and represents a genuine competitive advantage for venue operators.

PECR (Privacy and Electronic Communications Regulations)

UK regulations that govern direct marketing by electronic means, including email and SMS. PECR requires prior consent for marketing emails to individuals (as opposed to businesses). It works in conjunction with UK GDPR to define the legal basis for marketing communications triggered by the Purple-dotdigital integration.

IT and marketing teams must ensure that the splash page consent language covers all channels used for marketing — email, SMS, and push — and that the consent is specific to each channel where required.

Case Studies

A 450-room city-centre hotel group with 12 properties across the UK wants to use Purple's dotdigital connector to build a direct booking re-engagement programme. Each property has its own Purple venue configuration. The marketing team wants to send property-specific offers to guests who have stayed at a particular hotel, while also being able to run group-wide campaigns. How should the integration be architected?

The correct architecture uses venue-level connector configuration in Purple, with each of the 12 properties mapped to a dedicated dotdigital address book. This gives the marketing team clean, venue-specific contact lists for property-level targeting. In parallel, a dotdigital segment is created that aggregates contacts across all 12 address books — this segment is used for group-wide campaigns without duplicating contact records.

Step 1: In dotdigital, create 12 address books named by property (e.g., 'Purple - Manchester City Centre', 'Purple - Edinburgh Royal Mile'). Create a master segment using the 'Contact is in any of these address books' condition covering all 12 books.

Step 2: In Purple, navigate to each venue's settings under Management > Venues. For each venue, add a dotdigital connector at venue level, using the same API credentials but selecting the property-specific address book.

Step 3: Build a welcome automation programme in dotdigital triggered by contact addition to any of the 12 address books. Use dynamic content blocks in the email template to personalise the message based on the address book (property) the contact was added to — for example, featuring the specific hotel's amenities and a direct booking link.

Step 4: Build a re-engagement programme that fires 30 days after the last WiFi login, with a property-specific offer. Use dotdigital's contact scoring to identify high-value guests (multiple visits, high data completeness) for premium re-engagement campaigns.

Step 5: For group-wide campaigns — seasonal promotions, loyalty programme launches — use the master segment to reach the full opted-in database without duplicating sends to contacts who appear in multiple property address books.

Implementation Notes: This architecture correctly separates venue-level segmentation from group-level reach. The key decision point is using venue-level connector configuration rather than customer-level, which would route all 12 properties into a single address book and lose venue attribution. The master segment approach avoids the operational complexity of managing 12 separate campaign sends for group-wide communications. The dynamic content approach in the welcome email is a best practice that significantly improves engagement rates — guests respond to communications that reference their specific experience, not generic brand messaging. The re-engagement trigger at 30 days is based on documented industry benchmarks for hotel guest return frequency in city-centre properties.

A national retail chain with 85 stores has deployed Purple WiFi across its estate. After six months, the marketing team reports that contacts are appearing in dotdigital but the welcome automation programme is not triggering for approximately 15% of new contacts. The IT team has confirmed the connector is verified and contacts are being added to the correct address book. What is the most likely cause and how should it be resolved?

The most likely cause is a race condition between contact creation and programme enrolment in dotdigital, combined with contacts being added via the API rather than through dotdigital's native import. When contacts are added to an address book via the API — as Purple does — dotdigital's programme trigger logic may not fire if the programme is configured to trigger on 'contact added to address book via import' rather than 'contact added via API'.

Resolution Step 1: In dotdigital's Program Builder, open the welcome programme and inspect the enrolment trigger. Verify that the trigger condition is set to 'Contact added to address book' and that the 'Include contacts added via API' option is enabled. This option is not enabled by default in all dotdigital account configurations.

Resolution Step 2: If the trigger condition is correct, check whether the affected contacts have an opt-in status of 'Unknown' rather than 'Subscribed' in dotdigital. Contacts with 'Unknown' status may be excluded from programme enrolment depending on programme settings. Resolution: configure the programme to include contacts with 'Unknown' opt-in status, or implement dotdigital's double opt-in workflow to convert contacts to 'Subscribed' status on confirmation.

Resolution Step 3: Review the programme's enrolment frequency setting. If set to 'Enrol once only', contacts who have previously been enrolled — for example, from a prior WiFi session at a different store — will not be re-enrolled. For a retail chain where guests may visit multiple stores, consider whether re-enrolment on each new store visit is appropriate, and configure accordingly.

Resolution Step 4: Check for programme enrolment limits. Some dotdigital account configurations impose a maximum daily enrolment rate. If the retail chain's WiFi generates a high volume of new contacts on peak trading days, this limit may be causing the 15% gap.

Implementation Notes: This scenario illustrates a common class of integration issue that is not immediately visible from the connector configuration — it requires understanding of how dotdigital's programme trigger logic interacts with API-sourced contacts. The 'Include contacts added via API' setting is a frequent oversight in initial deployments. The opt-in status issue is equally common in multi-venue retail deployments where guests may have previously interacted with the brand through a different channel. The enrolment frequency question is a genuine architectural decision — for a retail chain, re-enrolment on each store visit may be appropriate to deliver store-specific content, but requires careful programme design to avoid over-communication.

Scenario Analysis

Q1. A conference centre operator runs a single Purple account covering three venues: a main auditorium, a breakout suite, and an exhibition hall. They want to use dotdigital to send post-event follow-up emails to attendees, with content specific to which space they visited. Their current connector is configured at customer level, routing all three venues into a single dotdigital address book. What change should they make, and what are the implications?

💡 Hint:Consider how venue-level configuration changes the address book structure, and what additional steps are required in dotdigital to support venue-specific content.

Show Recommended Approach

The operator should reconfigure the connector at venue level, creating three separate dotdigital address books — one per venue. This allows dotdigital to identify which venue a contact was added from, enabling venue-specific content in automation programmes. The implications are: (1) existing contacts in the single customer-level address book will need to be migrated or re-segmented; (2) three separate automation programmes will need to be created or a single programme with dynamic content blocks will need to be configured; (3) for group-wide communications, a dotdigital segment aggregating all three address books should be created. The migration of existing contacts is the most operationally complex step — it requires identifying which venue each existing contact was associated with, which may require cross-referencing Purple's analytics data with the dotdigital contact records.

Q2. A hotel group's IT team has deployed the Purple-dotdigital connector across 8 properties. Three months after go-live, the marketing team reports that the welcome email open rate is 12% — significantly below the 25% benchmark for hospitality welcome emails. Bounce rates are at 4.2%. What are the most likely causes and what remediation steps should the IT team recommend?

💡 Hint:A 4.2% bounce rate is a strong signal about data quality at the point of collection. Consider what happens to email deliverability when bounce rates are elevated, and how the consent mechanism may be contributing.

Show Recommended Approach

The 4.2% bounce rate is the primary issue and is almost certainly causing the low open rate. When bounce rates exceed 2%, inbox providers begin to treat the sending domain as a source of low-quality email, reducing inbox placement rates across the entire database — including valid, engaged contacts. The root cause of the high bounce rate is likely guests entering incorrect or temporary email addresses at the splash page, which is common in transient hospitality environments. Remediation: implement dotdigital's double opt-in workflow to verify email addresses before they enter the active database. This will reduce the volume of new contacts but will significantly improve data quality. Additionally, review whether the splash page requires email address confirmation (entering the address twice) — this simple UX change reduces typo-based bounces. For the open rate, review the welcome email send timing — if the email is sent hours after check-in rather than within minutes of WiFi connection, the contextual relevance is reduced. Also review the subject line and sender name for relevance and trust signals.

Q3. A large retail chain's data protection officer has raised a concern that the Purple-dotdigital integration may be re-adding previously unsubscribed contacts to the marketing database when they visit a store and connect to WiFi. The IT team needs to confirm whether this is happening and, if so, implement a fix. What steps should they take?

💡 Hint:This is a GDPR compliance issue, not just a technical one. Consider the data flow in both directions and what configuration is required to prevent re-addition of suppressed contacts.

Show Recommended Approach

This is a genuine GDPR risk. The scenario occurs when: (1) a contact unsubscribes from dotdigital marketing; (2) the unsubscribe is not synced back to Purple; (3) the contact subsequently visits a store and connects to WiFi; (4) Purple, unaware of the suppression, pushes the contact record to dotdigital again; (5) dotdigital re-adds the contact to the address book. To confirm whether this is happening, cross-reference dotdigital's suppression list with recent address book additions — any email address appearing in both lists indicates the problem is occurring. The fix requires two steps: (1) configure a dotdigital webhook that fires on unsubscribe events and updates the corresponding contact record in Purple to mark them as suppressed; (2) implement a pre-push check in the connector configuration to verify that the contact's email address is not on the dotdigital suppression list before transmitting. The DPO should also be advised that a Data Protection Impact Assessment should be conducted if one has not already been completed for this integration, given the cross-system personal data processing involved.

Q4. A stadium operator wants to use the Purple-dotdigital integration to send personalised post-match emails to fans who connected to the stadium WiFi during an event. They want to include the match result, a link to match highlights, and a personalised merchandise offer based on the fan's team affiliation. The current integration only captures the eight standard Purple data fields. What additional configuration is required to support this use case?

💡 Hint:Consider how event-specific data (match date, teams, result) can be associated with contacts in dotdigital, and how team affiliation can be captured at the splash page level.

Show Recommended Approach

This use case requires two enhancements beyond the standard integration. First, team affiliation must be captured at the splash page level using Purple's custom question feature on the splash page. A dropdown or radio button question — 'Which team are you supporting today?' — captures the affiliation at authentication time. This data can be passed to dotdigital as a custom contact data field, which must be created in dotdigital's account settings before the connector is configured. Second, event-specific data (match date, opponent, result) needs to be associated with the contact's session. This can be achieved by creating a separate dotdigital address book for each event, named with the match details, and configuring the Purple connector to route that event's WiFi logins to the event-specific address book. The post-match automation programme is then triggered by addition to that address book, with the match details embedded in the email template. For the merchandise offer, dotdigital's dynamic content feature can serve different product recommendations based on the team affiliation custom data field. This is a more complex deployment that benefits from Purple's Professional Services team involvement during the initial configuration.

Key Takeaways

✓The Purple-dotdigital connector is a real-time, consent-gated API integration that pushes eight guest profile fields to dotdigital at the point of WiFi authentication — but only when the guest has explicitly opted in to marketing communications.
✓Connector configuration requires four inputs: a connector name, a dotdigital API user email, the corresponding password, and the account-specific API endpoint URL retrieved from dotdigital's Account Settings > Access page. Incorrect endpoint URL is the leading cause of verification failures.
✓Deploy the connector at venue level for multi-property organisations to maintain clean address book segmentation per property; use customer level only for single-venue operators.
✓Build and test dotdigital automation programmes before activating the connector — the welcome email sent within minutes of WiFi login is the highest-engagement communication in the guest lifecycle and should not be missed.
✓Implement the dotdigital unsubscribe webhook to sync suppressions back to Purple; without this, the integration is non-compliant with UK GDPR and PECR and will generate deliverability problems over time.
✓Documented ROI benchmarks from the Purple estate include 54x return at Harrods, 842% at AGS Airports, and 10,630% at Brussels South Charleroi Airport — outcomes driven by deliberate programme design, not just a connected API.
✓Monitor deliverability metrics weekly during the first 90 days: target open rate above 20%, bounce rate below 2%, unsubscribe rate below 0.5%. Elevated bounce rates are the primary signal of data quality issues at the consent capture layer.