Analytics and Tracking

Adobe Analytics

Also called Adobe Experience Cloud analytics, Omniture

An enterprise measurement platform for organisations that model their own reporting structure, govern access and employ analysts to use it.

Quick facts: Adobe Analytics

Category
Analytics and Tracking
Also called
Adobe Experience Cloud analytics, Omniture
Level
Advanced
Affects
Enterprise reporting, data governance, analyst workload
Where to see it
Adobe Analytics (report suites, Analysis Workspace), Adobe Experience Platform
In this article4
  1. How Adobe Analytics works
  2. Why Adobe Analytics matters
  3. Common mistakes with Adobe Analytics
  4. What to do about it

How Adobe Analytics works

Adobe Analytics is an enterprise measurement platform and part of the wider Adobe Experience Cloud. Data is collected through a tag or a mobile SDK, shaped on the way in by rules you define, and stored against a report suite — the container that decides which sites, apps and regions are counted together and reported on as one.

Its distinctive parts are the variables. Traffic variables record what a page or screen is. Conversion variables carry a value that persists for a window you define, so a purchase made later can be credited back to the campaign, internal search or promotion that set it. Events count the things that happen. Analysis Workspace is the reporting area where analysts build their own tables, flow diagrams and fallout reports by dragging components together, rather than reading fixed screens somebody else designed.

Why Adobe Analytics matters

It matters where measurement is a job rather than a task. A large organisation with several brands, apps, regions and a call centre needs a tool that can be modelled to its own structure, governed with permissions and approvals, and queried freely by people whose role is analysis. Adobe’s persistence rules and segmentation are built for exactly that kind of question, and they answer it well when the modelling has been done properly.

For most businesses reading this page, its real usefulness is as a reference point. If a proposal quotes Adobe Analytics for a site with a handful of pages and one enquiry form, the tooling has been chosen for the name on it rather than for the question being asked, and that tells you something about the rest of the proposal.

Common mistakes with Adobe Analytics

Buying capability without staffing it is the classic failure. The platform is licensed commercially and it does very little on its own: the value sits in the variable design, the naming conventions, the documentation and the analysts who read it. Without those, an organisation pays enterprise prices for reports a free tool would have produced, and everyone quietly goes back to exporting spreadsheets.

The second is comparing its numbers with another tool’s and treating the gap as a bug. Adobe and Google define visits, attribution and persistence differently by design. Choose one system as the number the business quotes in its meetings, and use the other for what it is genuinely better at.

What to do about it

Ask what decision needs data your current tool cannot supply. If the honest answer involves several properties, offline systems, strict governance and people employed to analyse, then an enterprise platform is a defensible purchase and the implementation and training belong in the same budget line as the licence. If the answer is vaguer than that, the same money buys far more when it is spent on accurate conversion tracking and on fixing the website itself.

Whatever the platform, the same groundwork decides whether it works: a written measurement plan, consistent naming, one agreed definition for every metric the business quotes, and a named owner who keeps it current. None of that is specific to a vendor, all of it survives a migration, and it is where analytics and tracking projects succeed or fail regardless of what was bought.

Do and do not

Do

  • Name the decision the current tool cannot support
  • Budget implementation and training with the licence
  • Document every variable and who owns it

Do not

  • Buy enterprise tooling for a single small site
  • Treat differences from GA4 as reporting errors
  • Expect the platform to produce insight unaided

Questions people ask about this

How is Adobe Analytics different from GA4?

Adobe is licensed commercially and expects you to model your own structure through report suites and variables, with governance and analysts to match. GA4 is free at normal volumes, opinionated about its event model, and tightly connected to Google's advertising products. Adobe suits large organisations with dedicated analysts; GA4 suits most businesses, especially those running Google campaigns.

What is a report suite?

A report suite is the container that holds a defined set of data and the settings applied to it. It decides which sites, apps or regions are counted together, which variables exist, and who can see the results. Organisations typically run one per brand or market, plus a rolled-up suite that combines them for board-level reporting.

Does a small business ever need Adobe Analytics?

Very rarely. The platform is designed for scale, governance and dedicated analysts, and it delivers little value without them. A small business with one website and a few conversion actions gets more from measuring those conversions accurately, keeping definitions written down, and spending the difference on the site or on demand. Revisit the question when analysis becomes somebody's actual job.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.