A customer data platform is a system that collects a company's customer data from all its sources — website, app, transactions, CRM, support, marketing tools — unifies it into a persistent single profile per customer, and makes those profiles and the segments built from them available to other systems (CRM, advertising, personalisation, analytics) in real time.
Definition
A customer data platform is a system that collects a company's customer data from all its sources — website, app, transactions, CRM, support, marketing tools — unifies it into a persistent single profile per customer, and makes those profiles and the segments built from them available to other systems (CRM, advertising, personalisation, analytics) in real time. It is the operational counterpart of the single customer view: the SCV is the concept of one complete profile, the CDP is often the technology that builds and activates it.
A CDP's value is unified, actionable customer data — consistent segments across channels, real-time triggers, and a single place where profile and consent state live. Its risks are the concentration of a large amount of personal data in one activation-focused system, which raises the stakes on governance, consent handling and security.
In context
For iGaming operators, a CDP is often how the single customer view is made operational: unifying registration, deposit, betting, bonus, support and responsible-gambling-tool data into one profile, so that limits, self-exclusion and harm monitoring see the whole customer, and so CRM and (permitted) advertising work from consistent segments. Done well, it strengthens both personalisation and player protection, because a self-exclusion or an affordability flag on the unified profile propagates everywhere at once.
The governance requirements are heavy and specific. The CDP holds a large, sensitive personal-data aggregation, so it needs a lawful basis for each processing purpose, accurate per-channel and per-purpose consent state that governs what each downstream system can use, strict security, and retention limits.
Responsible-gambling suppression must be enforced at the CDP level so that self-excluded and at-risk players are excluded from every activation — marketing journeys, ad audiences, lookalike seeds — automatically. Regulators have penalised operators whose marketing continued to reach protected players because the suppression was not applied consistently across systems, which is exactly the failure a well-governed CDP prevents.
For affiliates, the CDP is operator-side infrastructure, but it explains why a properly run operator can apply limits, exclusions and monitoring account-wide and consistently. For affiliate-facing content, the framing is that a CDP unifies customer data into one activated profile and is often how the single customer view is implemented, that it strengthens both personalisation and player protection when governed well, and that it concentrates personal data so consent handling, responsible-gambling suppression and security are critical.
Worked example
An operator runs a CDP that unifies all customer data into one profile carrying consent state and responsible-gambling flags. A self-exclusion on the profile removes the player from every CRM journey and ad audience within minutes, an affordability flag routes them out of promotions, and each downstream system only uses data for the purposes the customer consented to.
Related terms
Frequently asked questions
Browse the full iGaming & affiliate glossary — hundreds of EN/RU terms with examples.
← Back to glossary