AI & analytics

Customer data platform (CDP)

A customer data platform (CDP) is software that collects your customer data from every source, unifies it into lasting profiles and shares them with your tools.

Updated November 3, 202611 min read

Customer data platform (CDP) at a glance
Also calledCDP, guest data platform (in restaurants)
What it isSoftware that builds one lasting, unified customer database your other systems can use
Core componentsIngestion, identity resolution, unified profiles, segmentation, activation
Typical restaurant sourcesPOS, online ordering, loyalty, reservations, Wi-Fi, surveys, reviews
Category namedApril 2013, by analyst David Raab
Industry bodyCDP Institute, launched in 2016 by David Raab
Related systemsCRM, data warehouse, loyalty platform, marketing automation
Rules to knowGDPR, CCPA as amended by the CPRA, TCPA for US marketing texts

Key takeaways

  • A customer data platform pulls in data from every system your guests touch, builds one profile per guest and makes those profiles available to the tools your teams use.
  • Its five building blocks are ingestion, identity resolution, unified profiles, segmentation and activation, and you only see the value once activation changes what guests experience.
  • A CDP sits between your data sources and your engagement tools, so in most setups it works alongside your CRM and data warehouse.
  • Restaurant CDPs come with connectors for POS, ordering, loyalty and reservations, and a general-purpose CDP usually needs engineering work to match them.
  • You'll keep a CDP project focused on measurable results by picking clear use cases, recording consent with each profile and using a holdout group for every campaign.

What is customer data platform (CDP)?

A customer data platform (CDP) collects your customer data from every source, links the records that belong to the same person and keeps them as persistent, unified profiles. Your other systems, like your email and SMS tools, loyalty program and support inbox, can then put those profiles to work.

The CDP Institute has long defined it as "packaged software that creates a persistent, unified customer database that is accessible to other systems." Every part of that sentence counts. The software comes ready-made, the profiles are kept over time, and your other tools can reach them.

If you run a restaurant brand, you'll know this problem. The same guest shows up as a card token in your POS, an email in online ordering, a phone number in loyalty and a name on a review site. A CDP brings those records together so your teams can see the whole relationship and act on it.

How a customer data platform works

Every customer data platform does five jobs, roughly in this order:

Component What it does Restaurant example
Ingestion Collects data from source systems through connectors, APIs or files Orders from the POS and app, bookings, survey answers
Identity resolution Decides which records belong to the same guest Linking an app account and a loyalty member by phone number
Unified profile Stores one persistent record per guest with history and traits Visits, spend, favorite items, last survey score
Segmentation Groups guests by rules or models Regulars who haven't visited in 45 days
Activation Sends audiences and traits to the tools that act on them An SMS campaign, a loyalty offer or a support view

Identity resolution is the hardest of the five. Our entry on the unified guest profile walks through how deterministic and probabilistic matching work, with a full example.

Real-time and batch data in a CDP

Some of your sources stream events within seconds, like an app order or a survey response. Others arrive in hourly or daily batches, like POS exports from older systems.

That difference shapes what you can do with the data. A recovery message after a poor survey score works best when the data arrives quickly, while a monthly lapsed-guest campaign is fine with daily updates.

Customer data platform example

Here's a worked example with illustrative numbers, focused on activation. Say you run a 30-location quick service brand that sends a weekly promotional email to 50,000 guests who've opted in to email marketing.

Your CDP connects online ordering, loyalty, surveys and reviews. In the past 14 days, 380 of those guests gave a 1- or 2-star survey score or have an open complaint.

Audience Guests What happens
Opted-in email list 50,000 Starting audience
Recent low score or open complaint 380 Removed from the promotion and sent to the guest care queue
Promotional email 50,000 − 380 = 49,620 Receives the weekly offer

Without the CDP, those 380 guests would get a cheerful discount while their complaint sat unanswered. With it, your guest care team sees each guest's orders and survey comments and can reply with context, which is where good service recovery starts.

Restaurant vs. general customer data platform

Restaurant CDP General-purpose CDP
Data model Visits, checks, menu items, locations, channels Events, page views, accounts, products
Prebuilt connectors POS, online ordering, delivery, loyalty, reservations Websites, apps, ad platforms, email tools
Multi-location views Built in, by store, region and franchisee Usually set up by the customer
Typical owner Marketing, guest experience and operations teams Data, product and marketing teams
Main trade-off Faster to launch, less flexible Flexible, needs more engineering

Restaurant CDPs, sometimes called guest data platforms, already understand that a guest visits a location and orders items on a check. General-purpose CDPs are built for digital events. They can model the same things, though it usually takes more setup.

Many large brands use both: a general-purpose stack for web and app data, and a restaurant platform for in-store and loyalty data.

Customer data platform vs. CRM vs. data warehouse

Customer data platform CRM Data warehouse
Main job Unify customer data and share profiles Manage relationships and interactions Store business data for analysis
Main users Marketing, guest and data teams Marketing, hosts, guest care Analysts and data engineers
Data scope Customer data from every source Records needed for its own workflows All business data
Output Profiles and audiences for other tools Campaigns, bookings, cases Reports, models, dashboards

Your restaurant CRM is often one of the tools a CDP feeds, and many restaurant products combine the two.

Our guide to the CDP in Momos puts the difference simply: a CRM tracks relationships, while the CDP unifies behavioral and transactional data so you can segment, personalize and measure.

Your data warehouse can hold unified customer profiles too. Composable, or warehouse-native, CDPs keep the data in your warehouse and add identity resolution, segmentation and activation on top. That setup suits brands with a strong data team.

Customer data platform use cases for restaurants

  • Win-back campaigns. Visit history makes lapsed regulars easy to find, and a win-back campaign reaches them while they still remember you.
  • Personalized offers. When you know a guest's favorite items, preferred channel and home location, your offer feels relevant to them.
  • Recovery with context. A low survey score or a complaint arrives with the guest's history attached, so you can answer a regular differently from a first-time guest.
  • Suppression. You can leave guests with an open complaint, or who just redeemed an offer, out of the next promotion.
  • Loyalty growth. Identified guests who aren't members yet are natural candidates for an invitation to your restaurant loyalty program.
  • Location insight. Grouping profiles by store shows you which locations keep their regulars and how guests move between channels.
  • Value analysis. Visit frequency and spend feed into guest lifetime value, which tells you where your marketing effort pays back.

How to implement a customer data platform

A CDP project goes more smoothly when you start from the decisions you want to change. This sequence works for most restaurant brands:

  1. Choose two or three use cases. Lapsed-guest win-back and recovery with context are common first picks.
  2. Map your sources. List each system, the identifiers it holds and how it records consent.
  3. Connect the strongest sources first. Online ordering and loyalty usually carry the best phone and email data.
  4. Set matching rules. Agree on how records get linked and who reviews uncertain matches.
  5. Build and test audiences. Spot-checking a few profiles in each audience confirms the filters do what you meant.
  6. Activate and measure. Give every campaign a holdout group, so you can see the visits it actually added.
  7. Expand. Add feedback, Wi-Fi and other channels once your first use cases show results.

Connectors drive most of the effort, since every source needs a reliable feed before its records can be matched. Our integrations page lists the kinds of sources a restaurant setup usually covers, from POS and ordering to review platforms.

A CDP brings personal data together, which raises the stakes for privacy. Each profile should carry its consent status and source for every channel. That way, a guest who opted in to email never gets a text they didn't agree to.

Two laws shape most programs. The EU's GDPR, which has applied since May 2018, requires a lawful basis for each use of personal data. California's CCPA, in effect since 2020 and expanded by the CPRA, gives consumers the right to know, delete and correct their information. It also lets them opt out of its sale or sharing.

In practice, a privacy-ready CDP can find and delete everything about one guest on request. It limits who can see sensitive fields like allergy notes and keeps only the data your teams use. This page is general information, so check any specific program with your own lawyer.

Best customer data platform tools

The right customer data platform depends on your sources and your team. Restaurant brands usually look for prebuilt connectors for their POS, ordering, loyalty and reservation systems, reporting by location, and a way to bring guest feedback into each profile.

ToolBest known for
MomosBest pickOur Guest AI Platform for multi-location restaurants. Our customer data platform unifies POS, loyalty, online ordering, survey, review and message data into guest profiles. You can build audiences by filter or by describing them to our Rosie agent, then run SMS and email campaigns across locations.
BikkyRestaurant guest data platform that unifies POS, ordering and loyalty data for analytics
OloDigital ordering platform with guest data and marketing tools, including the former Wisely
SevenRoomsReservations, table management and guest CRM with marketing automation for hospitality
SegmentGeneral-purpose customer data platform from Twilio for collecting and routing event data

Our roundup of the best restaurant customer data platforms compares a wider set of options in more detail. To narrow your list quickly, compare tools against your own systems, channels and locations, and check which connectors already exist for your stack.

Common customer data platform mistakes

  • Starting with technology. If you pick a CDP before your use cases are clear, it often ends up as an expensive copy of data you already have elsewhere.
  • Connecting every source at once. Long integration projects delay your first result, and weak sources add noise to the profiles.
  • Merging too aggressively. One wrong merge can show a guest someone else's history, which is far worse than a missed match.
  • Forgetting consent. Profiles without recorded opt-ins give you audiences you can't safely message.
  • Leaving out feedback. Spend and visits tell you what guests did, and first-party guest data from surveys and reviews tells you why.
  • Skipping the holdout. Without a control group, every campaign looks like a success and you can't compare any of them.

History of the customer data platform

The idea behind the customer data platform goes back to database marketing in the 1980s and customer relationship management software in the 1990s. Both aimed to keep one record per customer.

Analyst David Raab named the customer data platform category in a blog post in April 2013. He'd noticed that several new marketing systems could assemble a unified customer database from many sources. Later that year, Raab Associates published a report profiling the first group of CDP vendors.

Raab launched the CDP Institute in 2016 to define and track the category. As the label caught on and many vendors adopted it, the Institute published its RealCDP checklist in 2019 to give buyers more specific criteria.

The category consolidated in the years that followed. Twilio completed its acquisition of Segment in November 2020 in a deal valued at about $3.2 billion. In restaurants, Olo acquired the guest data platform Wisely in 2021.

Frequently asked questions

What is a customer data platform?

It's software that collects customer data from many sources, links the records that belong to the same person and stores them as persistent, unified profiles. Your other systems, like email, SMS, loyalty and support tools, can then use those profiles.

How does the CDP Institute define a CDP?

The CDP Institute's long-standing definition calls a CDP packaged software that creates a persistent, unified customer database that is accessible to other systems. The Institute has refined the wording over the years, so its website is the place to check the current version.

What is the difference between a CDP and a CRM?

A CRM is built for your teams to manage relationships and interactions, like campaigns, bookings and service cases. A CDP focuses on collecting and unifying data from every source and sharing it, and a CRM is often one of the tools that receives its profiles.

What is the difference between a CDP and a data warehouse?

A data warehouse stores data from across your business for reporting and analysis, and data engineers usually build and run it. A CDP is a ready-made system built around customer profiles that your marketing and guest teams can use directly. Some CDPs now run on top of a warehouse.

Do restaurants need a CDP?

A CDP tends to pay off if you have several ordering channels, many locations and guest data spread across POS, loyalty, ordering, reservations and feedback tools. If you run a single restaurant, you can often start with the guest features in your POS, reservation or loyalty system.

What is a composable CDP?

A composable or warehouse-native CDP keeps customer data in your own data warehouse and adds identity resolution, segmentation and activation on top. It suits brands with a strong data team. If you'd like a ready-made system, a packaged CDP is the usual choice.

How long does it take to implement a CDP?

It depends on how many sources you connect, how good their identifiers are and how much custom work they need. If you start with two or three well-connected sources and one or two use cases, your first campaign will usually run much sooner than it would with a full rollout.