dotdigital (formerly Dotmailer): Integration Guide, Best Practices, and Troubleshooting for Purple AI Users

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.

Executive Summary

The Purple AI platform captures first-party guest data at the point of WiFi authentication across hotels, retail estates, stadiums, and public-sector venues. The dotdigital connector — formerly branded as Dotmailer — transforms that raw data capture into a production-grade marketing automation pipeline. When a guest connects to your WiFi and consents to marketing communications, Purple pushes their profile to a designated dotdigital address book in real time. From that moment, dotdigital's automation engine can trigger welcome journeys, loyalty programme invitations, re-engagement campaigns, and omnichannel communications across email, SMS, and push.

The commercial case is well-documented. Harrods built a 3.6 million-contact database through WiFi-driven data capture and achieved a 54x return on their Purple investment within a single year. AGS Airports delivered an 842% ROI. Brussels South Charleroi Airport recorded a 10,630% ROI using Purple's MicroSurveys in combination with downstream marketing automation. These outcomes are not exceptional — they are the expected result of a well-configured integration deployed with deliberate programme design.

This guide provides the technical depth required to deploy, optimise, and troubleshoot the Purple-dotdigital integration at enterprise scale. It is structured for the IT professional who needs to implement a solution this quarter, not evaluate one next year.

Technical Deep-Dive

Integration Architecture

The Purple-dotdigital connector operates as a server-to-server REST API integration. Purple functions as the data producer, and dotdigital functions as the consumer. The connection is authenticated using dotdigital's Basic Auth mechanism: a dedicated API user account (email address and password) created within the dotdigital platform, combined with a region-specific API endpoint URL.

The architecture is unidirectional by default — Purple pushes contact records to dotdigital at the point of WiFi authentication. For organisations requiring bidirectional synchronisation (for example, to reflect unsubscribes or suppression list updates back into Purple), this requires additional configuration via dotdigital's webhook framework.

Component	Role	Notes
Purple Captive Portal	Guest authentication and consent capture	Splash page presented at WiFi login
Purple Connector Engine	Data transformation and API dispatch	Configured under Management > Connectors
dotdigital REST API	Contact ingestion and address book management	Region-specific endpoint required
dotdigital Address Book	Contact storage and segmentation layer	One or more books per venue/property
dotdigital Program Builder	Automation programme execution	Triggered on contact addition to address book

Data Payload and Field Mapping

Purple transmits eight data fields to dotdigital for each consenting guest. These fields map directly to dotdigital's standard contact data model and do not require custom field configuration for basic deployments.

Field Name	Data Type	Description
`firstName`	String	Guest's forename
`lastName`	String	Guest's surname
`userID`	Integer	Purple's internal user identifier
`email`	String	Primary contact address; used as deduplication key
`mobile`	String	Mobile telephone number (E.164 format recommended)
`gender`	String	Self-declared gender from splash page
`postcode`	String	Postal code; enables geographic segmentation
`dateOfBirth`	String	Format: YYYY-MM-DD; enables age-band segmentation and birthday triggers

Data transmission is consent-gated at the platform level. Purple will not dispatch a contact record to dotdigital unless the guest has explicitly opted in to marketing communications via the splash page consent checkbox. This is a hard enforcement — not a configurable option — and is the primary mechanism by which the integration maintains compliance with UK GDPR, the EU General Data Protection Regulation, and CCPA.

Authentication and Endpoint Configuration

dotdigital uses HTTP Basic Authentication for its REST API. The credentials consist of an API user email address and password, which must be created as a dedicated user within the dotdigital account — not the primary account login. The API endpoint URL is account-specific and region-dependent. It is retrieved from Account Settings > Access within the dotdigital platform. A typical endpoint takes the form https://r1-api.dotdigital.com for region one accounts.

This endpoint specificity is the most common source of connector verification failures. Teams that attempt to use a generic or documentation-example URL will encounter authentication errors. Always retrieve the endpoint value directly from the dotdigital account in use.

Connector Deployment Levels

Purple supports two deployment levels for the dotdigital connector:

Customer level applies the connector configuration across the entire Purple account, routing all consenting guests from all venues into a single dotdigital address book. This is appropriate for single-venue operators or organisations with a homogeneous venue estate.

Venue level allows each individual venue to be mapped to a distinct dotdigital address book. This is the recommended configuration for multi-property operators — hotel groups, retail chains, stadium operators — where venue-level segmentation is required for targeted marketing, localised offers, or separate brand identities.

Implementation Guide

Step 1: Prepare Your dotdigital Account

Before configuring the Purple connector, complete the following in your dotdigital account. Navigate to Account Settings and create a new API user with a dedicated email address and a strong password. Record the API endpoint URL displayed at the top of the Access page. Create the address book or books that will receive Purple contacts — one per venue is recommended for multi-property deployments. Optionally, create custom data fields in dotdigital if you intend to capture additional attributes beyond the eight standard Purple fields.

Step 2: Configure the Purple Connector

Within the Purple platform, navigate to Management > Connectors. Locate the dotdigital connector and select Add. Complete the four required fields: the connector name (a descriptive label for your reference), the dotdigital API email, the dotdigital API password, and the dotdigital API endpoint URL. Select Verify. On successful verification, a dropdown will appear listing the available address books in your dotdigital account. Select the target address book and save the configuration.

For multi-venue deployments, repeat this process at venue level for each property, assigning each to its designated address book.

Step 3: Configure the Splash Page Consent Mechanism

The marketing consent checkbox on your Purple splash page is the gateway to the entire integration. Navigate to your splash page configuration and ensure the marketing opt-in checkbox is enabled and clearly labelled. The consent language must be explicit, specific, and unambiguous under UK GDPR Article 7. A compliant example: "I agree to receive marketing communications from [Organisation Name] about offers, events, and news. You can unsubscribe at any time." Do not pre-tick this checkbox.

If your marketing programme includes SMS, ensure the consent language explicitly covers SMS communications. A single checkbox covering both email and SMS is permissible provided the language is clear.

Step 4: Build Your dotdigital Automation Programmes

Deploy automation programmes in dotdigital before the connector goes live. At minimum, configure a welcome programme triggered by contact addition to the address book. A recommended three-stage welcome journey:

Immediate (0 minutes): Welcome email confirming WiFi access, with a branded introduction to your venue or services.
Day 2 (48 hours): Follow-up email with a relevant offer, venue guide, or content piece tailored to the guest's context.
Day 30 (re-engagement): Automated re-engagement email for contacts who have not returned, with an incentive to revisit.

For loyalty programme integration, use dotdigital's Program Builder to enrol contacts who meet specific criteria — for example, contacts who answered affirmatively to a custom splash page question about loyalty programme interest.

Step 5: Configure Bidirectional Suppression Sync

Configure a dotdigital webhook to notify Purple when a contact unsubscribes. This ensures that a suppressed contact is not re-added to dotdigital on their next WiFi login. Without this step, the integration is technically incomplete from a GDPR compliance standpoint.

Step 6: Validate and Go Live

Conduct an end-to-end test by authenticating a test device on the WiFi, completing the splash page with a test email address and marketing consent, and verifying that the contact appears in the correct dotdigital address book within two to three minutes. Confirm that the welcome automation programme triggers correctly. Document the test results and proceed to production deployment.

Best Practices

Consent Architecture

The quality of your opted-in database is a direct function of your consent architecture. Organisations that invest in clear, honest consent language — even if it reduces opt-in rates marginally — build more engaged, higher-value contact lists. A 30% opt-in rate from a transparent consent mechanism will consistently outperform a 60% opt-in rate from an ambiguous or misleading one, because the former cohort genuinely wants to hear from you. Harrods achieved a 38% opt-in rate from 581,000 WiFi users — a rate consistent with transparent, value-exchange consent language.

Address Book Taxonomy

Design your dotdigital address book structure before connecting Purple. For a hotel group operating 20 properties, this might mean 20 venue-specific address books, plus a master consolidated book for cross-property campaigns. For a retail chain, it might mean books segmented by region or store format. The key principle is that address book structure determines your segmentation capability downstream — retrofitting it after data has been collected is costly and disruptive.

Automation Programme Depth

The most effective Purple-dotdigital deployments use dotdigital's full programme capability: welcome journeys, birthday campaigns triggered by the dateOfBirth field, re-engagement sequences for lapsed contacts, and post-visit surveys. The postcode field enables geographic targeting for localised offers. The gender field enables demographic personalisation. The dateOfBirth field enables age-band segmentation and birthday triggers. Use all eight fields — they represent a rich segmentation foundation that most organisations underutilise.

Deliverability Management

Monitor dotdigital's deliverability dashboard weekly during the first 90 days of deployment. Key benchmarks: open rate above 20%, click-through rate above 2%, bounce rate below 2%, unsubscribe rate below 0.5%. If bounce rates are elevated, implement dotdigital's double opt-in workflow to verify email addresses before they enter your active database. This is particularly relevant for venues with high transient footfall — airports, train stations, conference centres — where guests may enter temporary or incorrect email addresses.

GDPR and PECR Compliance

The integration is designed to be compliant by default, but compliance is a shared responsibility. Purple enforces consent at the data capture layer; dotdigital enforces it at the communications layer. Your organisation is responsible for the consent language on the splash page, the content of marketing communications, and the maintenance of suppression lists. Conduct a Data Protection Impact Assessment before deploying the integration in jurisdictions covered by UK GDPR or EU GDPR, particularly for public-sector organisations subject to additional obligations under the Data Protection Act 2018.

Troubleshooting and Risk Mitigation

Connector Verification Failures

The most frequent deployment issue. Caused in the majority of cases by an incorrect API endpoint URL. Resolution: log in to dotdigital, navigate to Account Settings > Access, and copy the endpoint URL exactly as displayed. Ensure no trailing slash or whitespace is included. Verify that the API user credentials are for a dedicated API user account, not the primary account login. If verification still fails, confirm that the dotdigital account has API access enabled — this is a feature that may need to be activated by dotdigital support for some account tiers.

Contacts Not Appearing in dotdigital

If the connector verifies successfully but contacts are not appearing in the target address book, the primary cause is the marketing consent checkbox not being enabled on the splash page. Purple will not transmit data without explicit consent. Secondary causes include the connector being configured at the wrong level (customer vs. venue), or the address book ID having changed since the connector was saved. Resolution: verify the splash page consent configuration, confirm the connector level, and re-verify the connector to refresh the address book selection.

Duplicate Contact Records

Occurs when the same email address is submitted across multiple WiFi sessions, typically in high-footfall venues. Resolution: ensure dotdigital's address book is configured to update existing contacts on email address match rather than creating new records. This is controlled within dotdigital's contact import settings. Additionally, review whether the Purple connector is configured at both customer and venue level for the same venue — a dual configuration will result in duplicate pushes.

Missing Data Fields

If contacts appear in dotdigital but certain fields are empty, the most likely cause is that guests did not complete those fields on the splash page. Purple only transmits fields that were provided during authentication. For optional fields such as mobile number or date of birth, some guests will decline to provide them. If completeness of specific fields is critical to your segmentation strategy, consider making those fields required on the splash page — but note that each additional required field will reduce your overall opt-in conversion rate.

GDPR Suppression Not Honoured

If unsubscribed contacts are being re-added to dotdigital on subsequent WiFi logins, the bidirectional suppression webhook has not been configured. This is a compliance risk. Resolution: configure a dotdigital webhook that fires on unsubscribe events and updates the corresponding contact record in Purple. Consult the dotdigital developer documentation for webhook configuration guidance.

Risk Mitigation Framework

Risk	Likelihood	Impact	Mitigation
Incorrect API endpoint	High	Medium	Retrieve endpoint directly from dotdigital account
Consent checkbox disabled	Medium	High	Include in pre-launch checklist; test with real device
Duplicate contacts	Medium	Low	Configure email-based deduplication in dotdigital
Suppression not synced	Low	High	Implement unsubscribe webhook before go-live
Data field completeness	High	Low	Set field requirements based on segmentation needs
API credential exposure	Low	High	Use dedicated API user; rotate credentials quarterly

ROI and Business Impact

Measuring Success

The Purple-dotdigital integration delivers value across two distinct dimensions: database growth and revenue attribution. Database growth is measured by the number of new opted-in contacts added per month, the opt-in rate as a percentage of total WiFi authentications, and the rate of contact data completeness (percentage of contacts with all eight fields populated). Revenue attribution is measured by tracking purchases, loyalty programme sign-ups, or other conversion events that can be linked to contacts who entered the database via WiFi login.

dotdigital's reporting suite provides campaign-level analytics — open rates, click-through rates, conversion rates — that can be used to calculate the revenue contribution of each automation programme. Purple's analytics dashboard provides the footfall and authentication data required to calculate the cost per acquired contact.

Benchmarks and Expected Outcomes

Based on documented deployments across the Purple estate:

Venue Type	Typical Opt-In Rate	Expected ROI Timeline	Key Revenue Driver
Luxury Retail	35–45%	6–12 months	Loyalty programme conversion
Hotel (mid-market)	25–35%	12–18 months	Direct booking re-engagement
Airport / Transport Hub	15–25%	18–24 months	Retail and F&B upsell
Stadium / Events Venue	20–30%	12–18 months	Merchandise and ticket upsell
Conference Centre	30–40%	6–12 months	Event re-booking and sponsorship

Cost-Benefit Considerations

The marginal cost of the dotdigital connector within Purple is low relative to the revenue potential. The primary investment is in programme design and content creation — the automation journeys, email templates, and segmentation logic that determine how effectively the contact database is monetised. Organisations that treat the integration as a set-and-forget data pipe will see modest returns. Those that invest in continuous programme optimisation — A/B testing subject lines, refining segmentation, extending automation depth — will see returns consistent with the Harrods and AGS Airports benchmarks documented above.

A practical rule of thumb: for every 10,000 opted-in contacts acquired through WiFi, a well-configured dotdigital programme should generate measurable incremental revenue within 90 days of deployment, assuming a minimum open rate of 20% and a click-through rate of 2% on the welcome series.

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.