A Customer Data Platform is one of the most frequently purchased and least effectively deployed technologies in the B2B MarTech stack. The category has been marketed with use cases — unified customer profiles, real-time personalisation, cross-channel consistency — that are genuinely achievable, but almost always require more data infrastructure maturity than the purchasing organisation actually has. Most B2B companies that buy a CDP within the first three years of trying to solve a data problem get the wrong tool for their actual problem.
What is a CDP?
A Customer Data Platform is a system that collects data from multiple sources, unifies it around individual customer or account records, and makes it available to other marketing and sales systems in real time. The key distinction from other data tools is the unification layer — a CDP creates a single persistent profile that updates across channels and systems.
Data collection and unification
Ingests event data from web, app, email, CRM, and offline sources. Stitches identity across anonymous and known users. Creates a unified profile that persists across sessions and channels.
Audience activation
Sends unified segments to downstream tools — ad platforms, email systems, sales tools — based on real-time profile state. Enables dynamic segmentation that updates automatically as profiles change.
It is not a data warehouse
A CDP is optimised for marketing activation, not analytics. It processes and activates data — it doesn't replace your data warehouse (Snowflake, BigQuery, Redshift) for reporting and modelling.
It is not a MAP or CRM
A CDP feeds your marketing automation platform and CRM — it doesn't replace them. If you don't have a working MAP and CRM, a CDP will not fix that. It will amplify whatever is already broken.
Why B2B CDPs are different
The CDP category was built primarily for B2C use cases — e-commerce, media, financial services — where individual consumer behaviour drives personalisation at scale. B2B has fundamentally different data characteristics that create different requirements and different failure modes.
B2B buying decisions involve multiple contacts at the same account — often 6-10 in enterprise deals. A B2C CDP that unifies individual consumer profiles is insufficient for B2B, where you need to unify individual profiles AND roll them up to account-level views showing aggregate engagement by company. Not all CDPs support account-level unification natively.
B2B buying cycles can span 12-18 months. A visitor who anonymously downloads a report in January and books a demo in October needs to be resolved as the same person. B2C CDPs often have identity resolution windows of 30-90 days. B2B deployments need persistent, long-cycle identity resolution with cross-device and cross-session stitching.
B2B personalisation and segmentation depends on company-level attributes — industry, size, revenue, tech stack, funding stage — that don't exist in most B2C data models. A B2B CDP deployment requires enrichment integration (Clearbit, Cognism, ZoomInfo, or similar) to append firmographic data to profiles at ingestion or on-demand.
A B2C e-commerce site might generate millions of events per day. A B2B SaaS company generating 500 MQLs per month has far lower event volume — but each event (a pricing page visit, a case study download, a demo request) carries much higher commercial signal. B2B CDP deployment needs to be optimised for signal quality and enrichment, not raw event throughput.
When a B2B company actually needs a CDP
Most B2B companies that buy a CDP don't yet need one. The specific conditions that make a CDP genuinely useful — rather than expensive infrastructure for problems you don't have — are narrow.
CDP options for B2B
The CDP market has several distinct tiers, from enterprise platforms requiring significant implementation resource to composable CDPs that sit on top of your existing data warehouse.
Full-featured CDPs with native B2B capabilities, account-level unification, and broad integration libraries. Segment is the most common in B2B SaaS — particularly for companies with product-led growth motions where in-app event data drives marketing activation. Implementation typically requires 3-6 months and dedicated technical resource. Pricing: £2,000-£15,000+/month.
Purpose-built for B2B account-based use cases. 6sense includes intent data, account identification, and audience activation in a single platform — effectively combining CDP, intent data, and ABM orchestration. Better suited to mid-market B2B than pure-play CDP tools. Pricing: £3,000-£30,000+/month depending on account volume and features.
Reverse ETL tools that sit on top of your existing data warehouse (Snowflake, BigQuery), treating it as your source of truth and syncing data to downstream tools. Lower implementation cost than traditional CDPs, but require a functional data warehouse already in place. Best for organisations with existing data infrastructure who need activation, not storage.
For many B2B companies under £10M ARR, the data unification and activation capabilities built into HubSpot or Marketo are sufficient. Before evaluating a standalone CDP, exhaust the native capabilities of your MAP — the answer is often already in the tool you're paying for.
What to do before buying a CDP
The most common CDP implementation failure is buying before the prerequisite infrastructure exists. Complete these steps first.
A CDP ingests and unifies data from your existing systems. If your CRM has duplicate records, inconsistent field usage, missing company associations, or stale contact data, the CDP will create a unified mess. Spend 30 days cleaning your CRM before evaluating a CDP — you may find the data problem was the only problem.
Document every data source (website, CRM, MAP, product, events, enrichment tools) and every destination (ad platforms, email, sales tools). Map the current connections and identify specifically where data is not flowing, where it is conflicting, or where you cannot segment the way you need. This exercise often reveals that a point integration (not a CDP) would solve the problem.
A CDP without a use case is an expensive data sink. Before purchasing, define three specific activation scenarios: "When a contact visits the pricing page twice without converting, suppress them from top-of-funnel paid campaigns and trigger an SDR task." If you cannot define three concrete use cases, you are not ready for a CDP.
CDP implementation requires engineering time for event tracking setup, data model design, and integration configuration. A typical Segment implementation requires 60-120 engineering hours upfront and ongoing maintenance. If you don't have in-house data engineering resource or a committed RevOps function, budget for a specialist implementation partner before signing a CDP contract.
Implementation considerations
The CDPs that deliver value within the first 12 months share a common implementation pattern. Those that stall share common failure modes.
- Start with a single use case, not a platform migration: The temptation is to migrate all data sources to the CDP immediately. Resist it. Pick one use case — typically website behavioural data to MAP sync — implement it end-to-end, validate the data quality, and demonstrate a business outcome before expanding scope.
- Define your data taxonomy before implementation starts: What is an "account"? What is a "contact"? What constitutes an "engagement event"? These definitions need to be agreed between marketing, sales, and data before a single line of code is written. Retrofitting a taxonomy to an existing CDP implementation is extremely painful.
- Build a data governance process from day one: CDPs degrade without governance. New event types need to be tracked in a schema registry, new integrations need sign-off, and data quality needs to be monitored continuously. Without governance, CDPs accumulate technical debt that makes them less useful over time, not more.
- Measure activation outcomes, not data volume: CDP success is not measured by the number of events ingested or the size of the unified profile database. It is measured by outcomes: did the segment we activated convert at a higher rate? Did the personalisation we enabled improve engagement? Did sales accept more leads from CDP-enriched sequences?
Our RevOps programme audits your stack, fixes your data infrastructure, and builds the reporting and automation workflows that make your tools actually work together.