What Adobe Analytics and Customer Journey Analytics actually cost
Adobe publishes no list prices for Adobe Analytics or Customer Journey Analytics. Both are sold by custom contract, negotiated on volume and packaging - which is why every "Adobe Analytics pricing" page you find is either a guess, an outdated leak, or bait for a sales call. We will not pretend to quote Adobe's prices. What we can do, as a boutique data engineering studio that implements these products, is explain what the contracts are actually made of, so the quote you eventually get from Adobe is one you can interrogate.
How the contracts are structured
Adobe Analytics has historically been packaged in tiers (Select, Prime, Ultimate) that gate features, with the commercial meter running on server-call volume and overages when traffic outruns the commitment. Customer Journey Analytics meters on rows of data - specifically the daily average rows available for analysis in CJA, not the volume you ingest, with a separate annual ingestion allowance set as a multiple of the licensed figure; packaging has changed more than once and should be confirmed against Adobe's current terms at negotiation time. Two consequences follow. First, implementation quality is a pricing lever: a tag plan that fires redundant calls, or datasets that ingest unfiltered noise, inflates the meter you pay on. Second, nobody should sign a volume commitment without measuring current volume first - which is, not coincidentally, something an audit produces.
The costs that are not on Adobe's invoice
License is one line of the total. The others: implementation engineering (schema design, tagging, identity, validation - once, done properly, or repeatedly, done cheaply); the analyst capability to turn Workspace access into decisions; governance time to keep components and data views from sprawling; and for CJA, the platform disciplines - data engineering and identity hygiene - that Adobe Analytics never demanded. The teams unhappiest with their Adobe spend are rarely overpaying Adobe; they are underspending on the implementation that would make the license earn its keep.
Questions to bring to the negotiation
What exactly meters the price, and what happens at overage? Which features in the demo are in which tier? What is our measured current volume, and who verified it? What does adding CJA to an existing Adobe Analytics contract change - and what does running both in parallel during migration cost? Adobe's sales team answers all of these; the leverage is in arriving with your own numbers.
FAQ
How much does Adobe Analytics cost?
Adobe publishes no list prices; Adobe Analytics is licensed by custom annual contract, typically metered on server-call volume and feature tier. Any specific figure you read online is unofficial. The reliable way to estimate is to measure your current volume and request a quote against it.
Is there a free version of Adobe Analytics or CJA?
No. Unlike Google Analytics 4, neither Adobe Analytics nor Customer Journey Analytics has a free tier; both are enterprise contracts. Trial and sandbox access exists through Adobe sales channels, not self-service signup.
What drives the cost of a CJA implementation?
Scope drives it: the number and messiness of data sources, identity complexity across channels, how much Adobe Analytics history and reporting must be rebuilt, and how much validation rigor the organization requires. That is why scoping starts with a fixed-scope audit - it converts an open-ended question into a costed plan before you commit to either Adobe or an implementation partner.