Ask buyers who run a CDP what frustrates them and six complaints come back, whatever the platform. The most common is about who can use it: platforms that need data engineers, specialists or a systems integrator before a marketer can build an audience. Below it sit paying for capability the team never adopts, pricing that is high or hard to forecast, integrations that stop short, features that were not ready when promised, and support that varies from excellent to absent. What differs is which platform draws which complaint, and whether buyers live with it or act on it. Mostly they live with it — pricing and support are the exceptions. For the ratings and the pre-purchase view, see what CDP buyers wish they'd known.
The six complaints — graded
Each complaint is classified by how buyers in these interviews typically respond: tolerating the issue, working to resolve it internally or with the vendor, or reconsidering the contract. These are observed responses, not fixed severity ratings; the same limitation may be manageable for one company and unacceptable for another. Every platform here draws complaints, and the question is which of them matter for your team.
It is built for engineers, not marketers
The most common complaint, and it lands on almost every platform. Buyers describe audiences that cannot be built without technical help: one says it “is taking five engineers on the data team to create lists or to create cohorts that the marketers could then create lists off of,” and an mParticle user calls it “really just an engineering tool mostly for us versus being a marketing tool.” On Adobe's platform, one buyer says “it requires a very specialist skillset to be able to operate it,” and a Salesforce Data Cloud user that it “requires significant Salesforce expertise to ensure it is configured properly.” Of Tealium: “there's hardly any way to get around having to know basic code to work in Tealium.” Buyers often tolerate this dependency: some rate their platforms highly despite needing specialist support — one Salesforce Data Cloud customer that does says “you definitely need specialists to use this tool” — and few describe switching because marketers cannot run the CDP on their own. That does not make the requirement trivial: its cost depends on whether the company has technical people available, and how much routine audience work has to go through them. BlueConic is the exception — its users here do not raise it.
Named for this: Adobe Real-Time CDP · Segment · Salesforce Data Cloud · Tealium · mParticle · ActionIQ
Paying for more than the team uses
The complaint about value. Buyers describe platforms adopted by a fraction of the people meant to use them — “It still hasn't been fully adopted across different teams. And so, I think we're not getting the full benefit of the tool yet,” says a Segment customer — and slow starts: one Hightouch customer says “It's taken six months to get one BU's data engineering fields in.” An Adobe customer finds “it's really hard to understand what pieces of the software we're really using versus what we're paying for.” At its sharpest it becomes a question about the whole category: “why are we paying for this?” Buyers mostly place the fix on their own side — “It's less about Segment as a CDP and more about our team and the lack of maturity on our team on how to use it,” one says.
Named for this: Segment · Tealium · BlueConic · Adobe Real-Time CDP · ActionIQ · Hightouch
Pricing is high, or hard to predict
The complaint buyers act on. Some find the price simply high: “We just did an evaluation of other Customer Data Platforms to see if we could replace Tealium because it is a very expensive tool,” one says, and an Adobe customer calls its platform “a very expensive platform for what it is.” Others describe pricing that is hard to forecast: on Salesforce Data Cloud, “the pricing model, which is based on credits, data volume, and feature tiers, makes it hard to predict from a budgeting perspective,” and “the cost can grow fast with high traffic digital channels.” On Segment, “any time you want to do something much more complex from a data perspective, you have to upgrade your plans.” This is the complaint behind most of the moves buyers describe: a Salesforce Data Cloud customer plans to look at alternatives at its next term, and the Tealium customer above ran a replacement evaluation before deciding to stay. Cost also cuts the other way — some Tealium and Segment customers praise the price.
Named for this: Salesforce Data Cloud · Adobe Real-Time CDP · Tealium · Segment · Simon Data · Amperity
Integrations and activation stop short
The complaint about connecting the platform to everything else. One Adobe customer describes a limitation in its own data architecture, saying that “Real-Time CDP requires all data to be ingested into Adobe Cloud rather than syncing directly from the warehouse.” A Segment customer reports difficulty connecting internal tools: “We've struggled to connect it at times with some of our internal tools.” Others describe needing extra tools to fill gaps — “it's unfortunate to need an additional tool just to capture those server-side events” — and slow data sharing. These accounts show how integration requirements can create extra work, depending on the platform's capabilities and the company's architecture. Buyers raise it across platforms but not as the reason they left; they work around it, often through the warehouse.
Named for this: Segment · Adobe Real-Time CDP · mParticle · Amperity · Tealium · BlueConic
Features that were not ready, or slow to arrive
The complaint about the product's maturity. A Tealium customer says “I don't think it was necessarily enterprise-ready when we purchased it originally”; a BlueConic customer has “encountered a number of bugs in the platform that have caused a lot of delays and speed to value.” A Salesforce Data Cloud customer describes features “that were promised from Salesforce that were either new at the time that we signed the original deal or were kind of coming down the pike. That's been slower.” Buyers mostly wait it out, and some describe the vendor fixing what they raised. It concentrates on BlueConic among the platforms here; elsewhere it is one or two buyers.
Named for this: BlueConic · Tealium · Salesforce Data Cloud · Adobe Real-Time CDP · Segment
Support and account management are uneven
Support splits buyers more than any other theme. On the complaint side, a Segment customer finds “the technical support and the CSMs with Segment have very limited understanding of complex issues,” a Tealium customer had to “buy additional office hours and meet weekly with a support team,” and a BlueConic customer counts account managers: “I've had three in eight months.” When weak support meets a buggy product, buyers start questioning the renewal — one weighing whether to stay with BlueConic asks “Can they provide the level of service and input that a Salesforce does?” On the praise side, Simon Data, Treasure Data, Tealium and Segment all draw compliments for their support from other customers.
Named for this: BlueConic · Segment · Tealium · Amperity · Hightouch
Want this checked against your own stack?
Start my checkup →The stories behind the complaints
The counter-current: what CDP users don't complain about
The notable silence is identity resolution — the matching and unifying of customer records that CDPs are bought for. Users praise it instead: one says Salesforce Data Cloud “provides strong capabilities to match and unify customer identities across our systems,” and an otherwise critical mParticle customer allows that “Identity resolution seems to be relatively good.” The one deduplication complaint came from a buyer who blamed “a fault of how we have set up Salesforce” rather than the CDP. Real-time speed is also rarely raised. And many buyers put the fault on their own side: “we don't have our data upstream sorted,” says one. Before you conclude the platform is the problem, separate what the vendor controls — pricing, support, product maturity — from what depends on your data and your team; the second is often fixable without a switch, though a lighter platform can still make sense when it better fits the team you have.
What this means — whether you run one or you're buying one
If you already run a CDP, sort your complaints with the grades above. Engineering dependency may be manageable when a team has the skills and capacity, but it becomes a significant operating cost when marketers rely on specialists for routine work; underuse is often an adoption problem before it is a product one, though not always; integration gaps are usually worked around. The ones buyers act on are pricing that outgrows the value and support that fails while the product is still maturing. If you're evaluating one, our recommendations — not practices buyers describe — are to decide first who on your team will run it day to day and whether they can without an engineer; to price it on the data volume and features you expect to need, not today's; and to ask existing customers about support and roadmap delivery, the two complaints that sour renewals. For where companies go when they do move, see why companies rip out or replace their CDP; for cost, what buyers actually pay for a CDP.
Common questions
What are the most common complaints about customer data platforms?
Six recur across Segment, Adobe Real-Time CDP, Tealium, BlueConic, Salesforce Data Cloud and others. The most common is that the platform needs engineers or specialists to run, so marketers cannot use it on their own. Next come paying for more than the team uses, pricing that is high or hard to predict, gaps in integrations and activation, features that were immature or slow to arrive, and uneven support and account management. Most buyers live with them; cost and support are the complaints that put a contract in play.
Are CDPs too technical for marketers?
Many buyers in these interviews say so. They describe platforms that need data engineers, specialist skills or a systems integrator to build audiences, and that most marketers cannot use day to day. It is the complaint raised most, yet buyers rarely leave over it; several rate their platform well while saying it needs specialists, and others put the gap down to their own team's staffing.
Why do companies leave their CDP?
In these interviews, cost and service are the complaints tied to leaving: one company plans to look at alternatives to Salesforce Data Cloud over its pricing and complexity, and a BlueConic renewal is in doubt over service and performance. Few go through with it. One company evaluated replacements for Tealium on cost and stayed because nothing matched its tag management. The one completed switch here, from Acquia to Amperity, was made for capability.
Is identity resolution a common CDP complaint?
Not among the users in these interviews. Identity resolution — matching and unifying customer records — is what CDPs are bought for, and users praise it on Amperity, Salesforce Data Cloud and mParticle rather than complain about it. The one deduplication complaint came from a buyer who blamed its own CRM setup rather than the CDP.
Are these complaints reasons to switch CDPs?
Mostly not. Buyers often treat needing engineers and underusing the platform as staffing and adoption problems on their own side, and several say so; integration gaps and immature features are usually waited out or worked around. That is how existing customers respond, not a judgment that these limitations are acceptable for a new buyer. The complaints that put a contract in play are pricing at renewal and support that fails while the product has bugs, and switching costs keep even those buyers in place more often than not.
Get a checkup on your tech stack
A physical for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.
Start my checkupFree · no password · your answers are anonymized before they inform research like this.