Segment is the CDP buyers in our corpus rate most often, and opinion on it is split. Complexity is the complaint that most clearly separates its lower raters from its higher ones; several lower raters describe Segment as difficult to operate without substantial technical support. Cost comes up about equally at both ends of the scale — yet cost relative to how much of the platform they used is the theme that recurs most among the buyers who actually leave. Where they take the job is the useful part. For the wider picture of buyers weighing the warehouse against a packaged CDP, see what is a CDP.
The alternatives, by where the job goes
Every destination buyers name, grouped by where the CDP job ended up. Two more buyers have left without a replacement.
What lower-rating Segment buyers complain about
That it is complex, and hard to run without technical support. It is the complaint that most clearly separates lower raters from higher ones, and several describe Segment as difficult to operate without substantial technical help. “Everything feels extremely complicated with Segment,” says one buyer rating it 4. Another, at 6, calls it “very heavyweight, and it's kind of difficult to manage by business people.”
That it goes underused. “It is great if you have the time and bodies to support it, but otherwise you are buying a very complex tool and probably only ever going to scratch the surface of what you can get out of it,” says a buyer rating it 5. One at 4 is blunter: “We had a Segment set up, but we haven't really gotten much usage out of it.”
And that it costs a lot for what a team gets from it. “Segment is very expensive for the value it provides,” says one rating it 6. Cost is the complaint buyers carry at every rating — high raters raise it about as often as low ones — which is why it shows up in the departures below even from buyers who still rate the product well.
Where buyers go
Fourteen buyers here have left Segment or are leaving it. The most consistent exit theme is cost relative to how much of Segment the buyer actually uses, though it is not the only one: one left over a missing capability, one in an acquisition. The destinations split by what they did with the job.
Toward the warehouse
A national insurer is already migrating: “Snowflake is already our data warehouse, so we would like to make it a Customer Data Platform as well.” It is “looking to decommission Segment in a year or so.”
No head-to-head published yet
A buyer on Segment for more than seven years ran a full RFP against Adobe and RudderStack and chose Hightouch as the closest fit, so the people building audiences would not “notice anything different.” The trigger was cost: “as the company grows, that user count gets up there, and the cost could kind of balloon.”
A buyer is “replacing Segment as a connector with a bunch of different, more direct integrations and consolidating everything into the warehouse.” It still credits Segment on identity resolution, but with the warehouse as the source of truth “it made no sense to pay Segment for the cost that they have.”
No head-to-head published yet
Into a platform already owned
One moved its RFM-style segments into Klaviyo: “Segment was technically a CDP, but we were only using it to create segments.” Another is moving “to leverage Klaviyo as a pseudo-Customer Data Platform and marketing orchestration platform,” and will pare back Segment after.
No head-to-head published yet
A buyer already running Bloomreach for site personalization will consolidate the CDP into it when the Segment contract ends. The reason is simple: “We already pay for it. I think that's the big one.”
No head-to-head published yet
One moved off Segment and Mixpanel to Google Analytics and the analytics built into its ad platforms. An earlier departure found it did not need a separate layer at all — “we really could find it elsewhere with a combination of Google Analytics or even Bluecore.”
No head-to-head published yet
A team running several Braze instances had to “turnoff Segment and switch to GTM because Segment couldn't support the filtration needed” to route data correctly.
No head-to-head published yet
Another tool
A buyer who moved from Segment to mParticle years ago is now leaving mParticle too, for an in-house build its engineers think will be “more powerful and less costly.”
A team that lost Segment when it was acquired is using Amplitude’s CDP features to “plug in some gaps” the acquiring company’s stack leaves.
No head-to-head published yet
A brand whose ads had stopped reaching the right customers uses Converge “to basically replace Segment for data sharing” with Meta. Too few buyers rate it to publish a figure.
No head-to-head published yet
The three warehouse-oriented moves preserve customer-data functions while changing the architecture: one treats Snowflake as the CDP, one replaces Segment’s connector role with direct integrations around Redshift, and one moves to warehouse-native Hightouch. All three were described in interviews from the past year. The moves into a platform already owned give the job to something the buyer pays for anyway; the two Klaviyo moves both describe using only part of Segment. Two more buyers left with nothing in its place: one offboarded it for “high cost and not full use of the functions,” and another, at a previous company, concluded “We just don't need that layer.”
Want this read against your own stack?
Get my read →When does staying on Segment make sense?
Most of its buyers stay, and the ones who rate it highly describe what they use it for.
Event collection and routing. High raters describe Segment as the backbone of their event data: “All the events have to flow through Segment,” says one rating it 9; another, also at 9, calls it “that main data collection point, and then we can set it out to wherever that particular data needs to go.” Even the buyer moving to Hightouch says “It's great with event collection, integrations, routing.”
Audience activation into paid media. “It's allowed us to create and automate audience creation from Segment CDP to paid media platforms like Google and Meta,” says a buyer rating it 8.
And how deeply it is wired into the stack. Current and departing buyers describe the migration burden: the buyer moving to Hightouch calls it “a bit of a pain point in terms of ripping Segment out of everything that we do,” and another, renewing for now, expects migration to be “a heavy lift since all our emails pretty much run on the signals that go through Segment.”
Our read — ours, not a buyer’s — is that the amount of Segment a team actually uses may matter as much as the platform’s capabilities. Several departures describe paying for more platform than the team needed, while some of the strongest positive commentary comes from buyers using Segment deeply for event collection, routing and activation.
Common questions
Why do buyers leave Segment?
The most consistent exit theme is cost relative to how much of the platform the buyer uses: one replaced it after per-user pricing grew with the company, another offboarded it for high cost and not using its full functionality, and others were only using it to build segments. It is not the only reason: one left over a missing capability, one in an acquisition. Among buyers who stay, complexity is the complaint that most clearly separates lower raters from higher ones, while cost comes up about equally at both ends of the scale.
What do buyers replace Segment with?
Of fourteen departures here, six moved the job into a platform already owned, three moved toward the data warehouse, three moved to another tool, and two have no replacement. The owned platforms are Klaviyo twice, Bloomreach, Google Analytics 4 twice and Google Tag Manager. The warehouse moves are one to Snowflake, one in-house on Redshift, and one to Hightouch, a warehouse-native CDP, after a full RFP. The other tools are mParticle, Amplitude and Converge.
Is Hightouch better than Segment?
The interviews do not establish one as universally better, though Hightouch rates higher: 7.9/10 against Segment's 7.0/10. The buyer here who chose Hightouch after an RFP picked it as the closest like-for-like replacement, so the people building audiences would notice as little change as possible, and still credits Segment for event collection, integrations and routing.
Can the data warehouse replace Segment?
For some buyers it already is. The three recent warehouse moves here are a national insurer migrating to Snowflake, a buyer consolidating onto Redshift with direct integrations instead of Segment as the connector, and a buyer moving to Hightouch, which runs on top of the warehouse. The three preserve customer-data functions in different architectures; what they share is an existing data warehouse, and they do not establish a single organizational prerequisite for making the move.
Can Klaviyo replace Segment?
For part of the job, two buyers here think so. One moved the RFM-style segments it was building in Segment into Klaviyo; another is moving to Klaviyo as a pseudo-CDP and will pare back Segment afterwards. Both describe using only part of Segment.
Get this research made for your stack
Weighing a move off Segment, or whether your warehouse or an existing platform could take the job? Do a 15-minute interview about your data, your stack and your team, and get a personalized read.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.