Start with the foundations › Adobe Analytics Fundamentals

Adobe Analytics Ecosystem

Amit G Dusane 16 years in digital analytics, seven of them at Adobe Published: 4 Sep 2026 6 min read

What Is Adobe Analytics settled why the tool exists and what it is at its core: a behavioral data platform that makes visitor behavior visible again. True, but that one line does not really tell you what the thing is once you are standing in front of it. If you have ever watched someone use Adobe Analytics, or just image-searched it out of curiosity, you have seen the surface, reports and bar charts and pie charts and trend lines, and you have probably overheard words like visits, page views, and visitors. That surface is exactly where this section starts.

Think of this as a deep-sea dive. You came to explore what is under the water, and What Is Adobe Analytics gave a fair sense of the place. This is the long jump down. Before anyone dives deep, they learn their gear first: the cylinder on your back, the suit, the protocols for when you are far below the surface. This section is that gear check. Welcome to the Adobe Analytics ecosystem.

Why it is an "ecosystem" and not just a tool

Adobe Analytics is doing many things at the same time. It collects data. It lets you customize how that data is collected. It hands the data back as many kinds of report. It filters and slices it, schedules deliveries, cleans it up, and controls who is allowed to see and touch which data. It is not just reports, not just collection, not just raw data, not just filtering, not just delivery. It is not any one of those things, and it is all of them at once. That "all of them at once" is what people mean by the ecosystem.

A car makes the point. A car is not its engine, not its tyres, not its interior, not its headlights, not its color. Pick any single part and it is not the car. The car is all of those parts working as one. Adobe Analytics is the same: a set of distinct pieces that together become one thing. So look at the pieces.

One system, and the parts you actually touch sit inside it

The two you meet first

When you look at a person, you do not know them by their hands or their feet. You know them by their face. The face of Adobe Analytics is Analysis Workspace, the space handed to you to build reports and play with data, and the part you will spend almost all your time in. The body underneath, the part that actually goes out and gathers everything, is the collection layer: Experience Platform Tags, still widely called Launch. It quietly captures every page load, download, form submission, and link click, and sends it in. One thing worth being precise about: the collection layer gathers and sends, it does not store. The storing and the heavy processing happen on Adobe's side, out of sight.

The full ecosystem, part by part

Six pieces make up most of what you will touch, and they split cleanly into three jobs: getting data in, working with it, and taking it back out.

🏷️

Adobe Launch (Tags) (the body)

How data gets gathered in the first place. Instead of asking engineering to hand-code tracking on every page, you configure data elements and rules here and publish them to your site. It gathers and sends, it is deployment, not reporting, so you will not analyze anything in it.

📈

Analysis Workspace (the face)

Your home base. Drag dimensions and metrics onto freeform tables, layer on visualizations, build filters and event sequences, and stack panels into a Project you share. Most questions that can be answered in Adobe are answered here, interactively, in seconds.

🗺️

Activity Map

A live overlay on your real site showing which elements visitors actually click and engage with, right there on the page. It is like a surveillance room for your own website: you watch, in near real time, what is working and what is being ignored, without building a single report.

🗄️

Data Warehouse

For when Workspace's in-browser view hits its ceiling. Request a very large, historical, deduplicated extract of your processed data, delivered later, sometimes minutes, sometimes hours. This is what you pull when you need to feed Tableau, Power BI, or heavy big-data calculations. Not interactive, not real time.

📤

Data Feeds

The raw counterpart. Where Workspace and Data Warehouse give you processed, normalized data, Data Feeds gives you the raw, hit-level data exactly as Adobe captured it, one row per hit, dropped to you on a schedule. This is what teams load into their own warehouse or pipe into Customer Journey Analytics.

🔗

APIs

The same data, reached by code instead of clicks. The Analytics APIs let you automate report pulls, feed external dashboards, and manage configuration at scale. When the interface itself becomes the bottleneck, this is the way through.

Normalized data versus raw data

This is the line that separates the export tools, and it is worth holding onto early. Analysis Workspace and Data Warehouse both work from Adobe's normalized data: the processed, business-ready version, where figures like visits and visitors are calculated for you at the moment you ask, against your dates and filters. Data Feeds is a different animal. It gives you the raw data, the technical record of each interaction as it was captured, before any of that calculation happens. The same events sit underneath both, in two very different shapes. Why the raw version matters, and what it looks like, is a story for its own module.

Not every part opens onto a live report

A classic first stumble: an analyst tries to pull two years of raw data into Workspace, watches it crawl or time out, and decides the tool is broken. It is not; that job was never Workspace's. Large historical and raw extracts are exactly what Data Warehouse and Data Feeds are for, while the collection layer is plumbing you deploy through, not analyze in. Match the part to the job and the friction disappears.

Default to Workspace, reach out only when it can't

Start every question in Analysis Workspace. Reach for Data Warehouse, Data Feeds, or the APIs only when Workspace genuinely cannot do the job: when you need the data outside Adobe, at raw grain, or delivered on an automated schedule.

For now, hold your curiosity. You have seen the gear and the parts, but you have only touched the surface of the water. Each of these gets its own deep dive in this course, and by the time you come back up you will know exactly which part to reach for when someone hands you a question. Let yourself be surprised by what is down there.

First, though, the words. Every conversation ahead of you, with a stakeholder, a developer, or Adobe's own documentation, quietly assumes a vocabulary nobody has handed you yet. Key Terminology hands it over.

Where to Find in Adobe Analytics

Analysis Workspace: Analytics → Workspace

Data Warehouse: Analytics → Tools → Data Warehouse

Activity Map: Analytics → Tools → Activity Map

← PreviousWhat Is Adobe Analytics Next →Key Terminology

Need implementation steps?

This article focuses on the concepts, architecture, and practical guidance behind the topic. For the latest UI walkthroughs and step-by-step implementation instructions, use the links below. They leave this site and open Adobe's own documentation in a new tab.

Learn More