Customer data platform cost for hospitality groups: build, buy or use your WiFi data

A customer data platform costs a hospitality group recurring licence fees alongside integration expenses for POS and property management systems. Building or buying unifies existing profiles, but using consented guest WiFi data under GDPR standards provides a cost-effective alternative. With 80,000+ venues, guest WiFi directly captures anonymous walk-in visitors without complex engineering projects.

Which option should you choose: build, buy or use your WiFi data?

You have three routes to a single view of your guests:

• Build your own stack on a cloud data warehouse.
• Buy a packaged CDP.
• Use the consented first-party data your guest WiFi already collects, through Purple Engage.

The right choice depends on one question. Do you need to unify data you already hold, or do you need to capture identities you have never had?

A CDP is a system that collects data from your other systems, matches records to the same person, and passes segments to your marketing tools. It joins up what already exists. It does not create a guest record for someone who never gave you their details.

That distinction matters more in hospitality than in most sectors. Your table booking platform usually holds the lead booker only, so a table of four gives you one known guest. Your point of sale (POS) system records transactions, not marketing consent. Walk-in diners and bar guests often leave no identity at all.

If most of your guests are anonymous, a CDP gives you a well-organised view of a minority. Guest WiFi fills the gap at the source: every guest who logs in and opts in becomes a consented profile, tied to a venue and a visit.

Where the three options genuinely differ

The table below compares the three routes on the axes that decide cost and outcome for a multi-site group.

	Build your own	Buy a packaged CDP	Use guest WiFi data with Purple Engage
What you pay for	Data warehouse consumption, connector fees, engineering salaries	Annual platform licence priced on profiles, events or credits, plus an implementation partner	Purple subscription on the Connect, Capture or Engage plan
New guest identities it creates	None: it unifies systems you already run	None: it unifies systems you already run	One for every guest who logs in to your WiFi and opts in
Where marketing consent is captured	You design and build consent capture yourself	Inherited from source systems as consent flags	At WiFi login, through a conscious-choice opt-in
In-house skills needed	Data engineers, an analytics engineer and a CRM manager	A CRM or data lead, plus an integration partner	A marketing or CRM manager
New hardware needed	None	None	None: runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme or Fortinet access points
Online browsing behaviour	Yes, if you build web and app collection	Yes, a core strength	No: it records on-site visits
Visit frequency by venue	Only if a source system records visits	Only if a source system records visits	Yes: every login records the venue and time
Best suited to	Groups with a data team and unusual requirements	Groups with large direct digital channels, an app or a loyalty scheme	Groups whose biggest gap is the anonymous walk-in guest

Read the "new guest identities" row twice. It is the row most CDP business cases skip.

What does a customer data platform cost a hospitality group to run?

CDP vendors publish pricing models, not universal prices, so your quote will depend on volume and modules. What you can predict is the shape of the bill. Plan for five cost lines, not one.

1. The licence

Packaged CDPs price on one of three bases:

• The number of profiles stored.
• The volume of events processed.
• Consumption credits that cover both.

In hospitality, profile counts grow fast once you load every booking, receipt and app install. Ask each vendor how duplicate and anonymous records count towards your tier. Many of the records you load will never resolve to a contactable guest, yet they can still count.

2. Integration work

This line usually surprises marketing teams. A typical group needs connectors to:

• A POS system.
• A property management system (PMS) for hotels.
• A table booking platform.
• A loyalty scheme or app.
• The email platform that sends the campaigns.

Each connector needs field mapping, identity-matching rules and testing. Each needs maintenance whenever a source system changes its data format. If you run different POS or booking systems across brands, multiply the work accordingly.

3. The build-your-own variant

Building swaps the licence for infrastructure and salaries. Cloud data warehouses such as Snowflake and Google BigQuery bill on storage and compute consumption. Managed connector services typically bill on the volume of rows synced. You then need engineers to model the data and push segments back out to your marketing tools. Those people are a permanent cost, not a project cost.

4. The people who run it

A CDP does not run itself after go-live. Someone owns:

• Identity rules.
• Data quality.
• Consent flags.
• The segment library.

In a packaged CDP that is usually a CRM or data lead. In a build, it is a small data team.

5. Time before your first useful campaign

Every month spent integrating is a month of campaigns you did not send. Count this as a cost when you compare options. A route that sends a targeted win-back email this quarter can beat a more complete route that sends one next year.

When building your own is the right call

Build when three conditions are true:

1. You already employ data engineers.
2. You have a cloud data warehouse in place for finance or operations reporting.
3. Your requirements are specific enough that packaged tools would need heavy customisation.

Large groups with in-house analytics often sit here. They already pay for the warehouse, so the extra cost is connectors and engineering time.

Building has a weakness that is easy to miss. A home-built stack is only as good as the data that flows into it. If your venues capture few identities, you will have built an expensive warehouse of anonymous transactions. The capture problem stays unsolved whichever way you store the data.

When buying a packaged CDP is the right call

Buy when a large share of your revenue comes through direct digital channels. That typically means hotel groups with a direct booking engine, groups with an ordering app, or brands with an active loyalty programme. In those cases, guests already identify themselves online. You have a genuine unification problem, and a CDP is built for exactly that.

A packaged CDP also makes sense when you send audiences to paid media at scale. Matching web behaviour, bookings and loyalty status into one profile gives you sharper suppression lists and better seed audiences. If paid social and search are a large line in your budget, read Lookalike audiences for hotels: a setup checklist using first-party guest data before you scope the project.

Even here, the CDP will not see guests who never book, order or join loyalty. Plan a capture source for them. Guest WiFi can feed the CDP as one more first-party input.

When guest WiFi data covers the need

Guest WiFi covers most of the need when your marketing goal is repeat visits from on-site guests. Most bars, pubs, restaurants, cafés and many hotels fit that description.

How the list builds itself

The mechanism is the login page guests see before they get online, known as a captive portal. A guest connects and logs in with email or a social account, then chooses whether to receive marketing. Purple records the opt-in, the venue and the visit.

Every return visit adds to the same profile, so visit frequency and recency build up without any integration project. You can then segment guests by venue, visit count and time since last visit, and send automated campaigns from Purple Engage.

This is where Purple Engage differs from Mailchimp, Klaviyo and HubSpot. Those tools send campaigns well, but they do not build the list. You still need a source of consented contacts at the venue, and in a walk-in business that source is usually missing. For a side-by-side view of the CRM option, see HubSpot vs Purple Engage for multi-site venues.

The proof behind the data source

Guest WiFi is not a niche data source. Purple's own data shows:

• 80,000+ live venues.
• 440 million logins in 2024.
• 99.999% platform uptime.

Purple holds ISO 27001 certification and GDPR compliance. Purple runs as a hardware-agnostic cloud overlay on the access points you already own, so there is no rip and replace. Hospitality groups run Purple across their estates.

Consent is the asset

Under GDPR Article 4(11), consent must be freely given, specific, informed and unambiguous. Article 7(4) adds that you should not make consent a condition of a service when processing is not necessary for that service. In practice, a guest must be able to get online without agreeing to marketing.

In the UK, the Privacy and Electronic Communications Regulations (PECR) also govern email marketing. Purple's conscious-choice opt-ins separate WiFi access from marketing consent. Every contact on your list has actively said yes, which protects deliverability as well as compliance.

Under GDPR Article 17, guests can also ask you to erase their data. Make sure whichever route you choose can honour that request across every system the data reaches.

What WiFi data does not replace

Be clear about the limits before you cancel a CDP evaluation.

• Spend. WiFi tells you who visited and how often, not what they spent. If revenue per guest drives your segmentation, you still need POS data joined to the profile.
• Online behaviour. WiFi does not see what a guest browsed on your website or in your app.
• Loyalty points. A points ledger lives in your loyalty platform, not in WiFi data.
• Guests who never connect. Some guests will not log in to WiFi on every visit, so the data shows a consented sample of your visitors, not a full census.

For many groups those limits are acceptable. Visit frequency and recency are the strongest signals for win-back and repeat-visit campaigns, and WiFi supplies both. For groups where spend or online behaviour drives the strategy, WiFi becomes a source for the CDP rather than a replacement.

Worked scenarios

The figures in these scenarios are planning assumptions, not customer results. Replace them with your own volumes.

A 30-site bar and restaurant group weighing a CDP

The situation. The group runs one table booking platform, two POS systems after an acquisition, and Mailchimp for email. The board asked for a CDP to "unify the guest". The CRM manager pulled booking data and found that most covers arrived as walk-ins or as unnamed members of a booked table.

What they did. Before signing a CDP contract, they switched on Purple Engage across their existing access points. Planning assumptions:

• 2,000 WiFi logins per site per month.
• An opt-in rate of 30%.

On those assumptions, the group adds 18,000 marketing-consented contacts a month across 30 sites, before deduplication of repeat visitors.

The measurable outcome. After 90 days, the group could report the share of opted-in guests who returned within 30 days at each site. Neither the booking platform nor the POS systems could produce that number. They ran an automated win-back email to guests with no visit in 45 days. They then measured return visits from that segment against a held-out control group.

The CDP decision moved from "buy now" to "revisit when we have joined POS spend to profiles". The integration budget went into one POS connection instead of five system connections.

A 12-hotel group with a direct booking engine

The situation. The group takes a meaningful share of room revenue through its own website and runs a loyalty scheme. It bought a packaged CDP to unify PMS, booking engine and loyalty data for paid media and email. Six months in, the marketing director noticed a gap. Restaurant, bar and spa guests who were not staying overnight barely appeared in the CDP.

What they did. The group added guest WiFi in its food and beverage outlets and spa as a first-party source. Non-resident guests who opted in at login became profiles alongside resident data. Assume each hotel's non-resident outlets generate 600 opted-in logins a month. That adds 7,200 non-resident contacts a month across the estate.

The measurable outcome. The group measured two numbers:

• The count of non-resident profiles added to the CDP each month.
• Conversion when those profiles were used to seed lookalike audiences for spa and dining campaigns.

The CDP licence stayed. WiFi made it worth more by filling the population it could not see.

A shopping centre with no transaction data

The situation. A regional shopping centre owner wanted a CDP to understand its shoppers. The problem was structural. Tenants own their own POS systems, so the centre holds no transaction data to unify.

What they did. The centre made guest WiFi its primary first-party source. Shoppers opted in at login, and the centre used visit frequency and dwell patterns to plan events and tenant promotions.

The measurable outcome. The centre measured monthly growth in consented shopper profiles and return-visit rates after each event campaign. A CDP would have had almost nothing to ingest. WiFi was the only route to a contactable audience.

How to decide for your venues

Map your situation to a recommendation with the matrix below.

Your situation	Recommendation
Most guests walk in, you run few direct digital channels, and the goal is repeat visits	Use guest WiFi data with Purple Engage now; review a CDP later
You run a direct booking engine, an app or a loyalty scheme, with a large paid media budget	Buy a packaged CDP and add guest WiFi as a first-party source
You employ data engineers and already pay for a cloud data warehouse	Build, and add guest WiFi as a source for on-site identity
You own the venue but not the transactions, such as a shopping centre or transport hub	Use guest WiFi as your primary first-party source
Your email tool sends well but your list has stopped growing	Add Purple Engage to build the list from guest WiFi logins

Before you issue a CDP request for proposal, answer four questions in writing:

1. What share of your guests can you identify today? Count consented, contactable profiles against covers, rooms or visits. If the share is low, capture comes before unification.
2. Which decision will the platform change? Name the campaign, such as win-back, birthday or venue launch, and the metric it moves, such as return visits, opt-in rate or revenue per send.
3. Which systems must connect in year one? List them by brand and by site, and get an integration estimate for each.
4. Who will run it? Name the person. If nobody has the time, a platform that needs a data team will stall.

If your answers point to capture rather than unification, start with guest WiFi. You can still buy or build a CDP later, and it will have more to work with when you do.

Frequently asked questions

How much does a customer data platform cost for a hospitality group?

There is no single price, because CDP vendors quote on profile volume, event volume or consumption credits. On top of the licence, budget for integration work with your POS, property management, booking and loyalty systems. You also need a CRM or data lead to run the platform after go-live. Ask every vendor how anonymous and duplicate records count towards your pricing tier, because hospitality data creates many of both.

Can guest WiFi data replace a customer data platform?

Yes, for many walk-in hospitality groups whose main goal is repeat visits. Guest WiFi captures consented identities, visit frequency and venue without an integration project. It does not capture spend, online browsing or loyalty points. If those drive your strategy, keep or buy a CDP and feed WiFi data into it as a first-party source for on-site guests.

Is marketing to guests from WiFi logins GDPR compliant?

Yes, provided marketing consent is separate from WiFi access and actively given. GDPR requires consent to be freely given, specific, informed and unambiguous, and Article 7(4) warns against making it a condition of a service. Purple's conscious-choice opt-ins let guests get online without agreeing to marketing. Purple holds ISO 27001 certification and GDPR compliance.

Does Purple work with the WiFi hardware we already have?

Yes, Purple is hardware-agnostic and runs as a cloud overlay on your existing access points. Supported vendors include Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. There is no rip and replace, so you can switch on guest data capture across a multi-site estate without a hardware project.

How is Purple Engage different from Mailchimp, Klaviyo or HubSpot?

Purple Engage builds the list as well as sending to it. Mailchimp, Klaviyo and HubSpot send campaigns to contacts you already hold, but they do not capture new contacts at the venue. Purple Engage creates a consented profile each time a guest logs in to your WiFi and opts in. It adds visit history to that profile, so you can segment and automate campaigns by venue and visit frequency.

Can we send WiFi data into a CDP or CRM we already use?

Yes, Purple integrates with CRM and marketing platforms, so WiFi profiles can feed the systems you already run. Hotel and multi-brand groups often do this to bring non-resident restaurant, bar and spa guests into a CDP. Those guests would otherwise never appear in property management or booking data.

How quickly can a hospitality group start building a list from guest WiFi?

You start building the list from the first login after go-live. Purple runs on your existing access points, so there is no hardware rollout or data warehouse build before capture begins. Most of the effort goes into designing your login page and opt-in wording, then setting up your first automated campaigns. That is a marketing task, not an engineering project.