CDP (Customer Data Platform)
CDP (Customer Data Platform) is a system that ingests guest data from every operational and marketing source a hotel runs, resolves the records that belong to the same person into a single persistent profile, and makes those profiles available to other systems for segmentation, personalisation, and campaign activation. In hospitality the typical inputs are the PMS, the booking engine, the CRS, point of sale, spa and golf systems, Wi-Fi captive portals, email and SMS platforms, review data, and website behaviour.
What distinguishes it from a CRM
The distinction matters commercially and is frequently blurred by vendors. A hotel CRM manages known-guest communication — pre-arrival emails, post-stay surveys, loyalty messaging — and generally works from reservation records. A CDP sits a layer beneath: its defining function is identity resolution, stitching the anonymous website visitor, the OTA booking with a masked email, the walk-in who paid at the bar, and the loyalty member into one profile. A CRM consumes profiles; a CDP builds them. Many hospitality products sold as CDPs are in practice CRMs with an import feature, and the honest test is whether the system can merge records that share no common key.
Example
A guest browses the hotel site on mobile, books three weeks later through Booking.com using an aliased OTA email, spends €180 in the restaurant under a room charge, and returns eight months on through the brand site with a personal email address. Four systems hold four unrelated records. A CDP resolves them via device identifier, name and card token, and stay history into one profile showing a €740 lifetime value, a restaurant affinity, and a first-touch that was organic rather than OTA-originated — which changes both how that guest is marketed to and how the OTA booking is attributed.
Why it matters
Two forces have pushed CDPs up the hospitality technology agenda. The first is the collapse of third-party cookies and the resulting shift of paid acquisition toward first-party audiences, which a hotel can only build if its guest data is unified. The second is the economics of direct bookings: repeat business is the cheapest inventory a hotel sells, and improving the repeat guest ratio requires knowing who the repeat guests are across properties and channels — something fragmented systems structurally cannot answer. A CDP is also the practical prerequisite for meaningful multi-touch attribution, since attribution across sessions and devices is an identity problem before it is a modelling one.
Caveats
A CDP inherits the quality of its inputs; deploying one over inconsistent PMS profile hygiene produces confidently wrong merges. Identity resolution across households sharing a card or an address is a well-known source of error. And because a CDP concentrates personal data by design, it raises the stakes on GDPR lawful basis, retention limits, consent propagation to downstream tools, and the guest's right to erasure across every connected system — obligations that do not disappear because a vendor manages the platform.
Related
- Repeat Guest Ratio — the metric a CDP is most often bought to move
- Multi-Touch Attribution (MTA) — depends on the identity graph a CDP maintains
- Direct Bookings — the commercial objective behind most deployments
- Guest Sentiment Analysis — review and survey data commonly feeds the profile