dotdigital (anteriormente Dotmailer): Guia de Integração, Melhores Práticas e Solução de Problemas para Usuários da 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.

Resumo Executivo

A plataforma Purple AI captura dados primários (first-party) de visitantes no momento da autenticação do WiFi em hotéis, propriedades de varejo, estádios e locais do setor público. O conector da dotdigital — anteriormente conhecido como Dotmailer — transforma essa captura de dados brutos em um pipeline de automação de marketing de nível de produção. Quando um visitante se conecta ao seu WiFi e consente com as comunicações de marketing, a Purple envia seu perfil para um catálogo de endereços (address book) designado da dotdigital em tempo real. A partir desse momento, o mecanismo de automação da dotdigital pode acionar jornadas de boas-vindas, convites para programas de fidelidade, campanhas de reengajamento e comunicações omnichannel por e-mail, SMS e push.

O caso comercial é bem documentado. A Harrods construiu um banco de dados de 3,6 milhões de contatos por meio da captura de dados via WiFi e alcançou um retorno de 54x sobre o investimento na Purple em um único ano. A AGS Airports entregou um ROI de 842%. O Brussels South Charleroi Airport registrou um ROI de 10.630% usando as MicroSurveys da Purple em combinação com a automação de marketing downstream. Esses resultados não são excepcionais — eles são o resultado esperado de uma integração bem configurada e implementada com um design de programa intencional.

Este guia fornece a profundidade técnica necessária para implementar, otimizar e solucionar problemas da integração Purple-dotdigital em escala corporativa. Ele é estruturado para o profissional de TI que precisa implementar uma solução neste trimestre, e não avaliar uma no próximo ano.

Aprofundamento Técnico

Arquitetura de Integração

O conector Purple-dotdigital opera como uma integração de API REST de servidor para servidor. A Purple atua como produtora de dados e a dotdigital atua como consumidora. A conexão é autenticada usando o mecanismo Basic Auth da dotdigital: uma conta de usuário de API dedicada (endereço de e-mail e senha) criada dentro da plataforma dotdigital, combinada com um URL de endpoint de API específico da região.

A arquitetura é unidirecional por padrão — a Purple envia registros de contatos para a dotdigital no momento da autenticação do WiFi. Para organizações que exigem sincronização bidirecional (por exemplo, para refletir cancelamentos de assinatura ou atualizações de listas de supressão de volta na Purple), isso requer configuração adicional por meio do framework de webhooks da dotdigital.

Componente	Função	Notas
Captive Portal da Purple	Autenticação de visitantes e captura de consentimento	Splash page apresentada no login do WiFi
Mecanismo de Conector da Purple	Transformação de dados e envio de API	Configurado em Management > Connectors
API REST da dotdigital	Ingestão de contatos e gerenciamento de catálogo de endereços	Endpoint específico da região necessário
Catálogo de Endereços da dotdigital	Armazenamento de contatos e camada de segmentação	Um ou mais catálogos por local/propriedade
Construtor de Programas da dotdigital	Execução de programas de automação	Acionado na adição de contatos ao catálogo de endereços

Payload de Dados e Mapeamento de Campos

A Purple transmite oito campos de dados para a dotdigital para cada visitante que fornece consentimento. Esses campos são mapeados diretamente para o modelo de dados de contato padrão da dotdigital e não exigem configuração de campos personalizados para implementações básicas.

Nome do Campo	Tipo de Dado	Descrição
`firstName`	String	Nome do visitante
`lastName`	String	Sobrenome do visitante
`userID`	Integer	Identificador interno de usuário da Purple
`email`	String	Endereço de contato principal; usado como chave de desduplicação
`mobile`	String	Número de telefone celular (formato E.164 recomendado)
`gender`	String	Gênero autodeclarado na splash page
`postcode`	String	Código postal (CEP); permite segmentação geográfica
`dateOfBirth`	String	Formato: AAAA-MM-DD; permite segmentação por faixa etária e gatilhos de aniversário

A transmissão de dados é controlada por consentimento no nível da plataforma. A Purple não enviará um registro de contato para a dotdigital a menos que o visitante tenha optado explicitamente por receber comunicações de marketing por meio da caixa de seleção de consentimento na splash page. Esta é uma imposição estrita — não uma opção configurável — e é o mecanismo principal pelo qual a integração mantém a conformidade com o GDPR do Reino Unido, o Regulamento Geral sobre a Proteção de Dados da UE e a CCPA.

Autenticação e Configuração de Endpoint

A dotdigital usa Autenticação Básica HTTP para sua API REST. As credenciais consistem em um endereço de e-mail e senha de usuário da API, que devem ser criados como um usuário dedicado dentro da conta dotdigital — não o login da conta principal. O URL do endpoint da API é específico da conta e dependente da região. Ele é obtido em Account Settings > Access na plataforma dotdigital. Um endpoint típico tem o formato https://r1-api.dotdigital.com para contas da região um.

Essa especificidade do endpoint é a fonte mais comum de falhas de verificação do conector. Equipes que tentam usar um URL genérico ou de exemplo de documentação encontrarão erros de autenticação. Sempre obtenha o valor do endpoint diretamente da conta dotdigital em uso.

Níveis de Implementação do Conector

A Purple suporta dois níveis de implementação para o conector da dotdigital:

Nível de cliente (Customer level) aplica a configuração do conector em toda a conta Purple, roteando todos os visitantes que deram consentimento de todos os locais para um único catálogo de endereços da dotdigital. Isso é apropriado para operadores de um único local ou organizações com um conjunto homogêneo de locais.

Nível de local (Venue level) permite que cada local individual seja mapeado para um catálogo de endereços distinto da dotdigital. Esta é a configuração recomendada para operadores de múltiplas propriedades — grupos hoteleiros, redes de varejo, operadores de estádios — onde a segmentação no nível do local é necessária para marketing direcionado, ofertas localizadas ou identidades de marca separadas.

Guia de Implementação

Passo 1: Prepare sua Conta dotdigital

Antes de configurar o conector da Purple, conclua o seguinte em sua conta dotdigital. Navegue até Account Settings e crie um novo usuário de API com um endereço de e-mail dedicado e uma senha forte. Anote o URL do endpoint da API exibido na parte superior da página Access. Crie o catálogo de endereços (ou catálogos) que receberá os contatos da Purple — recomenda-se um por local para implementações em múltiplas propriedades. Opcionalmente, crie campos de dados personalizados na dotdigital se pretender capturar atributos adicionais além dos oito campos padrão da Purple.

Passo 2: Configure o Conector da Purple

Na plataforma Purple, navegue até Management > Connectors. Localize o conector da dotdigital e selecione Add. Preencha os quatro campos obrigatórios: o nome do conector (um rótulo descritivo para sua referência), o e-mail da API da dotdigital, a senha da API da dotdigital e o URL do endpoint da API da dotdigital. Selecione Verify. Após a verificação bem-sucedida, um menu suspenso aparecerá listando os catálogos de endereços disponíveis em sua conta dotdigital. Selecione o catálogo de endereços de destino e salve a configuração.

Para implementações em vários locais, repita esse processo no nível do local para cada propriedade, atribuindo cada uma ao seu catálogo de endereços designado.

Passo 3: Configure o Mecanismo de Consentimento da Splash Page

A caixa de seleção de consentimento de marketing na sua splash page da Purple é a porta de entrada para toda a integração. Navegue até a configuração da sua splash page e certifique-se de que a caixa de seleção de opt-in de marketing esteja ativada e claramente rotulada. A linguagem de consentimento deve ser explícita, específica e inequívoca de acordo com o Artigo 7 do GDPR do Reino Unido. Um exemplo em conformidade: "Concordo em receber comunicações de marketing de [Nome da Organização] sobre ofertas, eventos e notícias. Você pode cancelar a assinatura a qualquer momento." Não marque esta caixa de seleção previamente.

Se o seu programa de marketing incluir SMS, certifique-se de que a linguagem de consentimento cubra explicitamente as comunicações por SMS. Uma única caixa de seleção cobrindo tanto e-mail quanto SMS é permitida, desde que a linguagem seja clara.

Passo 4: Crie Seus Programas de Automação na dotdigital

Implemente programas de automação na dotdigital antes que o conector entre em operação. No mínimo, configure um programa de boas-vindas acionado pela adição de contatos ao catálogo de endereços. Uma jornada de boas-vindas recomendada em três estágios:

Imediato (0 minutos): E-mail de boas-vindas confirmando o acesso ao WiFi, com uma introdução da marca ao seu local ou serviços.
Dia 2 (48 horas): E-mail de acompanhamento com uma oferta relevante, guia do local ou peça de conteúdo adaptada ao contexto do visitante.
Dia 30 (reengajamento): E-mail automatizado de reengajamento para contatos que não retornaram, com um incentivo para uma nova visita.

Para integração de programas de fidelidade, use o Program Builder da dotdigital para inscrever contatos que atendam a critérios específicos — por exemplo, contatos que responderam afirmativamente a uma pergunta personalizada na splash page sobre o interesse no programa de fidelidade.

Passo 5: Configure a Sincronização de Supressão Bidirecional

Configure um webhook da dotdigital para notificar a Purple quando um contato cancelar a assinatura. Isso garante que um contato suprimido não seja adicionado novamente à dotdigital em seu próximo login no WiFi. Sem este passo, a integração está tecnicamente incompleta do ponto de vista da conformidade com o GDPR.

Passo 6: Valide e Entre em Operação (Go Live)

Realize um teste de ponta a ponta autenticando um dispositivo de teste no WiFi, preenchendo a splash page com um endereço de e-mail de teste e consentimento de marketing, e verificando se o contato aparece no catálogo de endereços correto da dotdigital dentro de dois a três minutos. Confirme se o programa de automação de boas-vindas é acionado corretamente. Documente os resultados do teste e prossiga para a implementação em produção.

Melhores Práticas

Arquitetura de Consentimento

A qualidade do seu banco de dados com opt-in é uma função direta da sua arquitetura de consentimento. Organizações que investem em uma linguagem de consentimento clara e honesta — mesmo que isso reduza marginalmente as taxas de opt-in — constroem listas de contatos mais engajadas e de maior valor. Uma taxa de opt-in de 30% de um mecanismo de consentimento transparente superará consistentemente uma taxa de opt-in de 60% de um mecanismo ambíguo ou enganoso, porque o primeiro grupo genuinamente deseja ouvir de você. A Harrods alcançou uma taxa de opt-in de 38% de 581.000 usuários de WiFi — uma taxa consistente com uma linguagem de consentimento transparente e de troca de valor.

Taxonomia do Catálogo de Endereços

Projete a estrutura do seu catálogo de endereços da dotdigital antes de conectar a Purple. Para um grupo hoteleiro operando 20 propriedades, isso pode significar 20 catálogos de endereços específicos por local, além de um catálogo consolidado mestre para campanhas entre propriedades. Para uma rede de varejo, pode significar catálogos segmentados por região ou formato de loja. O princípio fundamental é que a estrutura do catálogo de endereços determina sua capacidade de segmentação downstream — reestruturá-la após a coleta de dados é custoso e disruptivo.

Profundidade do Programa de Automação

As implementações mais eficazes da Purple-dotdigital usam a capacidade total do programa da dotdigital: jornadas de boas-vindas, campanhas de aniversário acionadas pelo campo dateOfBirth, sequências de reengajamento para contatos inativos e pesquisas pós-visita. O campo postcode permite direcionamento geográfico para ofertas localizadas. O campo gender permite personalização demográfica. O campo dateOfBirth permite segmentação por faixa etária e gatilhos de aniversário. Use todos os oito campos — eles representam uma base rica de segmentação que a maioria das organizações subutiliza.

Gerenciamento de Entregabilidade

Monitore o painel de entregabilidade da dotdigital semanalmente durante os primeiros 90 dias de implementação. Benchmarks principais: taxa de abertura acima de 20%, taxa de cliques acima de 2%, taxa de rejeição (bounce rate) abaixo de 2%, taxa de cancelamento de assinatura abaixo de 0,5%. Se as taxas de rejeição estiverem elevadas, implemente o fluxo de trabalho de double opt-in da dotdigital para verificar os endereços de e-mail antes que eles entrem no seu banco de dados ativo. Isso é particularmente relevante para locais com alto tráfego transitório — aeroportos, estações de trem, centros de conferências — onde os visitantes podem inserir endereços de e-mail temporários ou incorretos.

Conformidade com GDPR e PECR

A integração é projetada para estar em conformidade por padrão, mas a conformidade é uma responsabilidade compartilhada. A Purple impõe o consentimento na camada de captura de dados; a dotdigital o impõe na camada de comunicações. Sua organização é responsável pela linguagem de consentimento na splash page, pelo conteúdo das comunicações de marketing e pela manutenção das listas de supressão. Realize uma Avaliação de Impacto sobre a Proteção de Dados antes de implementar a integração em jurisdições cobertas pelo GDPR do Reino Unido ou GDPR da UE, particularmente para organizações do setor público sujeitas a obrigações adicionais sob o Data Protection Act 2018.

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

Falhas de Verificação do Conector

O problema de implementação mais frequente. Causado na maioria dos casos por um URL de endpoint de API incorreto. Resolução: faça login na dotdigital, navegue até Account Settings > Access e copie o URL do endpoint exatamente como exibido. Certifique-se de que nenhuma barra final ou espaço em branco seja incluído. Verifique se as credenciais de usuário da API são para uma conta de usuário de API dedicada, não o login da conta principal. Se a verificação ainda falhar, confirme se a conta dotdigital tem o acesso à API ativado — este é um recurso que pode precisar ser ativado pelo suporte da dotdigital para alguns níveis de conta.

Contatos Não Aparecem na dotdigital

Se o conector for verificado com sucesso, mas os contatos não estiverem aparecendo no catálogo de endereços de destino, a causa principal é a caixa de seleção de consentimento de marketing não estar ativada na splash page. A Purple não transmitirá dados sem consentimento explícito. Causas secundárias incluem o conector estar configurado no nível errado (cliente vs. local) ou o ID do catálogo de endereços ter mudado desde que o conector foi salvo. Resolução: verifique a configuração de consentimento da splash page, confirme o nível do conector e verifique novamente o conector para atualizar a seleção do catálogo de endereços.

Registros de Contato Duplicados

Ocorre quando o mesmo endereço de e-mail é enviado em várias sessões de WiFi, normalmente em locais de alto tráfego. Resolução: certifique-se de que o catálogo de endereços da dotdigital esteja configurado para atualizar contatos existentes na correspondência de endereço de e-mail, em vez de criar novos registros. Isso é controlado nas configurações de importação de contatos da dotdigital. Além disso, revise se o conector da Purple está configurado tanto no nível do cliente quanto no nível do local para o mesmo local — uma configuração dupla resultará em envios duplicados.

Campos de Dados Ausentes

Se os contatos aparecerem na dotdigital, mas determinados campos estiverem vazios, a causa mais provável é que os visitantes não preencheram esses campos na splash page. A Purple transmite apenas os campos que foram fornecidos durante a autenticação. Para campos opcionais, como número de celular ou data de nascimento, alguns visitantes se recusarão a fornecê-los. Se a integridade de campos específicos for crítica para sua estratégia de segmentação, considere tornar esses campos obrigatórios na splash page — mas observe que cada campo obrigatório adicional reduzirá sua taxa geral de conversão de opt-in.

Supressão do GDPR Não Respeitada

Se contatos que cancelaram a assinatura estiverem sendo adicionados novamente à dotdigital em logins de WiFi subsequentes, o webhook de supressão bidirecional não foi configurado. Este é um risco de conformidade. Resolução: configure um webhook da dotdigital que seja acionado em eventos de cancelamento de assinatura e atualize o registro de contato correspondente na Purple. Consulte a documentação do desenvolvedor da dotdigital para obter orientações sobre a configuração de webhooks.

Estrutura de Mitigação de Riscos

Risco	Probabilidade	Impacto	Mitigação
Endpoint de API incorreto	Alta	Médio	Obter endpoint diretamente da conta dotdigital
Caixa de seleção de consentimento desativada	Média	Alto	Incluir no checklist de pré-lançamento; testar com dispositivo real
Contatos duplicados	Média	Baixo	Configurar desduplicação baseada em e-mail na dotdigital
Supressão não sincronizada	Baixa	Alto	Implementar webhook de cancelamento de assinatura antes do go-live
Integridade do campo de dados	Alta	Baixo	Definir requisitos de campo com base nas necessidades de segmentação
Exposição de credenciais de API	Baixa	Alto	Usar usuário de API dedicado; rotacionar credenciais trimestralmente

ROI e Impacto nos Negócios

Medindo o Sucesso

A integração Purple-dotdigital entrega valor em duas dimensões distintas: crescimento do banco de dados e atribuição de receita. O crescimento do banco de dados é medido pelo número de novos contatos com opt-in adicionados por mês, a taxa de opt-in como uma porcentagem do total de autenticações de WiFi e a taxa de integridade dos dados de contato (porcentagem de contatos com todos os oito campos preenchidos). A atribuição de receita é medida rastreando compras, inscrições em programas de fidelidade ou outros eventos de conversão que podem ser vinculados a contatos que entraram no banco de dados via login no WiFi.

O pacote de relatórios da dotdigital fornece análises no nível da campanha — taxas de abertura, taxas de cliques, taxas de conversão — que podem ser usadas para calcular a contribuição de receita de cada programa de automação. O painel de análises da Purple fornece os dados de tráfego (footfall) e autenticação necessários para calcular o custo por contato adquirido.

Benchmarks e Resultados Esperados

Com base em implementações documentadas em todo o ecossistema da Purple:

Tipo de Local	Taxa Típica de Opt-In	Cronograma Esperado de ROI	Principal Impulsionador de Receita
Varejo de Luxo	35–45%	6–12 meses	Conversão de programa de fidelidade
Hotel (mid-market)	25–35%	12–18 meses	Reengajamento de reserva direta
Aeroporto / Hub de Transporte	15–25%	18–24 meses	Upsell de varejo e A&B (Alimentos e Bebidas)
Estádio / Local de Eventos	20–30%	12–18 meses	Upsell de mercadorias e ingressos
Centro de Conferências	30–40%	6–12 meses	Remarcação de eventos e patrocínio

Considerações de Custo-Benefício

O custo marginal do conector da dotdigital dentro da Purple é baixo em relação ao potencial de receita. O investimento principal é no design do programa e na criação de conteúdo — as jornadas de automação, modelos de e-mail e lógica de segmentação que determinam a eficácia com que o banco de dados de contatos é monetizado. Organizações que tratam a integração como um canal de dados do tipo 'configure e esqueça' (set-and-forget) verão retornos modestos. Aquelas que investem na otimização contínua do programa — testes A/B de linhas de assunto, refinamento da segmentação, extensão da profundidade da automação — verão retornos consistentes com os benchmarks da Harrods e da AGS Airports documentados acima.

Uma regra prática: para cada 10.000 contatos com opt-in adquiridos via WiFi, um programa da dotdigital bem configurado deve gerar receita incremental mensurável dentro de 90 dias após a implementação, assumindo uma taxa de abertura mínima de 20% e uma taxa de cliques de 2% na série de boas-vindas.

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.