Adobe Analytics is Adobe’s paid platform for measuring how people use websites and apps, built for large organisations with dedicated analytics staff. It sits within Adobe Experience Cloud, alongside Adobe’s testing, personalisation and customer data products.
How Adobe Analytics works
Like GA4, Adobe Analytics collects data through code on each page or app screen, usually deployed with Adobe’s own tag manager (once called Adobe Launch, now part of Adobe Experience Platform Data Collection) and its Web SDK. The real difference is how the data is modelled. Instead of GA4’s events and parameters, a classic Adobe set-up uses three kinds of variable:
- Props Traffic variables that describe a single page or hit, such as the page type.
- eVars Conversion variables that persist for as long as you configure, so a campaign code or internal search term can take credit for an order placed later in the visit or on a later visit.
- Success events The actions you count, such as sign-ups, basket additions and orders.
Data lands in report suites, which are separate data sets for a site, brand or region. Analysts explore it in Analysis Workspace, a drag-and-drop space for building tables, segments and charts. Adobe also sells Customer Journey Analytics, a newer product built on Adobe Experience Platform that joins web data with other sources such as CRM and contact centre records.
There is no public price list. Licences are agreed through a contract with Adobe.
Why it matters
For a large UK retailer, bank or publisher, Adobe offers things GA4’s free version does not: detailed control over how long credit persists, processing rules that reshape data as it arrives, unsampled reporting in normal use, and close links to Adobe’s testing and personalisation tools. A negotiated contract covering data handling also suits compliance teams in regulated sectors working under UK GDPR.
For most small and medium UK businesses it is the wrong tool. The licence is only part of the cost: a useful Adobe set-up needs a documented design, a developer to implement it and an analyst to run it. A business without those people will usually get more from a well-configured GA4 property, or from a lighter privacy-focused tool such as Matomo, than from an Adobe contract nobody has time to use.
Common mistakes
- Buying Adobe to solve a measurement problem that is really about unclear goals or messy tagging. The same problems follow you to the new platform.
- Letting the solution design reference, the document that records what each eVar, prop and event holds, fall out of date, so nobody can trust what a variable means.
- Reusing a variable for a new purpose without a clean break, which mixes two meanings in the same historical reports.
- Expecting Adobe and GA4 to report matching visits. They define visits, visitors and credit differently, and often run under different consent and cookie set-ups.
- Letting personal data, such as email addresses in page URLs, flow into variables that many people can see.
How to act on it
If you are choosing an analytics platform, start with the questions you need answered and the people you have to answer them, then choose the tool. Write a measurement plan first; it will show whether you need Adobe’s depth or whether GA4 covers it.
If you already run Adobe, check the basics before adding anything. Confirm the solution design reference matches what the tags actually send, make sure your consent management platform passes the visitor’s choice to Adobe’s tags before they fire, and retire variables nobody has used in a year.
Choosing a measurement set-up that fits the size of the business, and the team that will use it, is part of the digital marketing strategy and consulting work I do.