CDP Pricing Explained: MTU, Events, Credits, and Flat Licences — What a Customer Data Platform Costs at Scale (2026)

Customer data platforms (CDPs) are priced in four ways: per monthly tracked user (MTU), per event or data volume, per consumption credit, or as a flat licence per deployment. The model matters more than the list price, because it decides what makes your bill grow — anonymous visitors, identity resolution, extra destinations, or nothing at all. Public price points in October 2026: Twilio Segment starts free at 1,000 MTUs and $120 per month for 10,000 MTUs; Salesforce Data 360 sells Flex Credits at $500 per 100,000 and profiles at $240 per 1,000 per year; Adobe Real-Time CDP is quote-only and priced by profile volume. Below we normalise each model to 1, 10 and 50 million profiles and show where the hidden costs sit.

Every price in this guide was read on the vendor's own pricing page on the date shown. Enterprise contracts are negotiated and usually land well below list; the point of list-price arithmetic is to see the shape of each curve, not to predict your invoice. For the spreadsheet behind the numbers, see the 3-year TCO model; for a vendor-by-vendor dataset, the CDP Pricing Index.

The four pricing models

Two models appear in one vendor more often than buyers expect: Salesforce sells Data 360 both by profile and by credit; profile SKUs include one or two Flex Credits per profile, and operations beyond that allowance still consume Flex Credits 2. Segment's MTU model is accompanied by a custom Business tier whose price is not public 1. Adobe publishes no prices at all 3.

Public price points, vendor by vendor

Twilio Segment — Checked on 2026-10-17

• Free: the Twilio page lists 1,000 visitors per month and 10 seats.
• Team: starts at $120/month for 10,000 visitors. Its rate table lists $12, $11 and $10 per additional 1,000 across the 10K–25K, 25K–100K and 100K+ bands. The FAQ instead says $10 beyond 10,000. Confirm the applicable billing interpretation with Twilio.
• Business: custom pricing, including HIPAA eligibility with a BAA required; the comparison also calls HIPAA an add-on.

Official Twilio pricing, checked 17 October 2026. These are pipeline plan prices; full CDP features and enterprise scope may cost more.

MTUs count anonymous visitors. A content site with heavy unauthenticated traffic can have ten times more MTUs than customers, which is the single most common reason Segment bills surprise finance teams. A Hacker News thread from the 2019 price change captured the mood: one team reported paying about $30,000 every six months and others rebuilt event routing in-house for a few hundred dollars a month in cloud cost 5.

The following arithmetic assumes marginal bands: each rate applies only to users inside that band. This is an explicit modelling assumption, not a vendor-confirmed interpretation. Use the calculator to change rates and compare the result with a current quote. Twilio source.

The upper rows extrapolate public pipeline rates. Business pricing is custom and the applicable product, feature coverage and volume terms require a vendor quote. The table illustrates a slope; it is not an offer. See Segment pricing and alternatives.

Salesforce Data 360, formerly Data Cloud — Checked on 2026-10-17

Salesforce renamed Data Cloud to Data 360 at Dreamforce 2025, the product's sixth name in a decade, and positions it as the context layer for Agentforce 6. Two public models 2:

• Flex Credits: $500 per 100,000 credits; pre-purchase, pay-as-you-go and pre-commit options. Data ingestion is free; credits are consumed by queries, data preparation, identity resolution, segmentation, activation, streaming and other operations. Each operation has a multiplier set in the rate card, and Salesforce publishes two: the current Flex Credits rate card (31 August 2026) lists data queries at 3 credits per million rows and profile unification — identity resolution — at 75,000 credits per million rows, with ingestion free and four monthly volume tiers; the legacy Data Services rate card (August 2025) had queries at 2 and unification at 100,000 [2b]. Confirm which card your order form references. At $500 per 100,000 credits, unifying 10 million rows once costs 750,000 credits on the current card, or $3,750 at list, before re-runs.
• Profiles: $240 per 1,000 profiles per year, including one Flex Credit per profile; Enterprise Profiles at $420 per 1,000 per year with two credits per profile.
• Storage is billed separately: Salesforce's own worked example prices it at $23 per terabyte per month, a figure that does not appear on the main pricing page [2c]. The official calculator also shows a Starter package at $60,000 per year including 10 million credits and 5 TB of storage [2d].

List-price arithmetic on the Profiles SKU is simple: 1 million profiles is $240,000 per year, 10 million is $2.4 million, 50 million is $12 million — before any negotiation, and before credits consumed above the included allowance. Salesforce's own numbers show the scale of the business: Agentforce plus Data 360 annual recurring revenue was about $3.9 billion in the quarter ended 31 July 2026, up 210 % year on year under a widened definition 7. Detail: Salesforce Data 360 pricing explained.

Adobe Real-Time CDP — Checked on 2026-10-17

Adobe publishes no prices. The pricing page describes three editions, B2C, B2B and B2P, each "dictated by profile volume", with a request-pricing button 3. Licensing consultancies quote typical annual bands of roughly $300,000 to $2.5 million for Real-Time CDP depending on profiles and audiences; these are estimates, not Adobe figures 8. One widely copied blog attributes "$240 per 1,000 profiles" to Adobe; that is Salesforce's published rate, not Adobe's — a useful reminder to read vendor pages, not round-ups. The Healthcare Shield add-on positions the platform for HIPAA-regulated customers with PHI controls; confirm BAA terms in the order form 9. Detail: Adobe Real-Time CDP pricing and licensing.

Other vendors

The CDP Pricing Index separates public prices, partial free/from prices and quote-only vendors. Its dated sources prevent a free connector tier being mistaken for a full enterprise CDP price. Compare included features, billable units and contract scope before comparing totals. Open-source and source-available licences also differ; check the actual licence and operating costs.

PrivyCDP

PrivyCDP uses a flat licence per deployment tier, annual or perpetual with an annual version-extension and update entitlement. There is no per-profile, per-event or per-destination metering; infrastructure, cloud, hardware and DevOps are scoped as separate line items so that procurement sees them 11. We do not publish a list price in this guide; the licensing page describes the structure and the architecture review produces a three-year worksheet for a specific environment.

Cost curves at 1M, 10M and 50M profiles

The table applies list prices and explicit assumptions. Change any assumption and the numbers move; the spreadsheet in the TCO model lets you do that.

Assumptions: MTUs equal 60 % of profiles (many customers inactive in a given month, but anonymous visitors add back); Segment list bands applied marginally with no negotiated discount; Salesforce Profiles SKU at list with no extra credits; flat licence shown as L (licence) + I (infrastructure) + O (operations), because licence prices are deal-specific and we will not invent one.

Three honest readings of this table:

1. At around 1 million profiles, metered SaaS is usually cheaper. A flat licence plus the people to run infrastructure costs more than a Team-tier bill, and SaaS removes operational work.
2. Around 10 million profiles the curves cross — for profile- and credit-priced platforms. Our three-year model puts the crossover for a profile-priced platform such as Salesforce Data 360 at roughly 10 million profiles. For an MTU-priced event pipeline at list rates the picture is different: SaaS can stay slightly cheaper even at 50 million profiles until you add the identity, audience and journey modules that turn a pipeline into a CDP, which are custom-priced. Banks and insurers with regulator-mandated retention feel the crossover earliest, because they cannot shrink the profile base to save money.
3. Above 50 million, everything is a negotiation, but the negotiation starts from very different places. Metered vendors discount from a list that grows with you; a flat licence starts from capacity you own. This is also where perpetual licensing becomes a capital-expenditure conversation rather than a subscription; see perpetual licence vs SaaS subscription.

Hidden costs checklist

The list price is rarely the problem. These items are.

• Anonymous MTUs. Unauthenticated web traffic, bots and QA tools inflate MTU counts. Ask how anonymous users are counted and whether you can exclude them.
• Activation fees. Per-destination or per-connector charges ("activation tax") on top of the platform fee. Ask for the destination price list.
• Identity resolution and compute credits. In credit models, identity resolution and segmentation can dominate consumption. Ask for the multiplier table and a consumption report from a comparable customer.
• Storage and retention. Long retention (seven years is common in finance) multiplies storage lines. Ask what counts as storage and whether archived data is cheaper.
• Sandboxes and non-production environments. Often metered separately or capped.
• Premium support and SLAs. Ask for support prices, scope and response commitments in the quote.
• Overage and true-up. Some contracts true up annually at list rates; ask for caps and advance notice.
• Cloud egress. For warehouse-native and BYOC designs, data movement between clouds is billed by your cloud provider, not the vendor.
• Professional services. Implementation, connectors, identity-rule tuning. Stable Kernel's category estimate for a full CDP programme is "several hundred thousand dollars to several million dollars" over three years, with worked scenarios around $1.1 million, $2.5 million and $3 million 12.
• Exit. Exporting an identity graph, merge history and consent state is rarely a button. In the EU, switching charges for data processing services are capped at cost now and abolished from 12 January 2027 under the Data Act 13; the engineering cost of migration remains yours. See migrating off a SaaS CDP.

Twelve questions to ask before signing

1. Which unit drives the bill, and can you show me a monthly consumption report for a customer of my size?
2. How are anonymous users, bots and internal traffic counted?
3. What is the full multiplier or rate card, and is it fixed for the term?
4. What is included in the base price, and what is an add-on (identity resolution, consent, governance, HIPAA, private connectivity)?
5. Are destinations priced separately? Which ones?
6. What happens at the end of the included volume — overage at list, true-up, or throttling?
7. What is the storage rate, and how is retention beyond two years billed?
8. Is there a cap on annual price increases at renewal?
9. What are the exit terms: export formats, assistance, timelines, fees?
10. Can the deployment move to a single-tenant or customer-owned environment later, at what price?
11. Which compliance features are gated behind the top tier?
12. What does a three-year total look like with 30 % growth per year, in writing?

The right answer to question 12 is a worksheet, not a slide.

Flat licence vs metered: a CFO's view

Neither model is morally superior. Metered pricing lets a small team start for $120 a month; a flat licence lets a bank sign a five-year budget. Problems start when an organisation with the second profile buys on the first model.