Getting started with Adobe Analytics takes three things: access through your company’s Adobe administrator, a report suite that already receives data, and a first project in Analysis Workspace. This beginner’s guide covers each one, from logging in to reading your first report.
It assumes the tracking is already in place. If it is not, the setup is a separate project, covered step by step in our Adobe Analytics implementation guide.
Logging in to Adobe Analytics

How to log in to Adobe Analytics
Adobe Analytics is licensed to an organization, not to a person, so there is no sign-up form: your company’s Adobe administrator gives you access.
- Go to experience.adobe.com and sign in with the account your company uses with Adobe. If your company uses single sign-on, enter your work email and you are sent to its login page.
- Pick the organization if your account belongs to more than one, from the menu at the top right.
- Open Analytics from the app switcher. If it is not there, your user is not in an Analytics product profile yet.
- No access? Ask your Adobe administrator to add you in the Admin Console to an Analytics product profile with the report suites you need.
What to check before your first report
- Which report suite to use. A report suite is the container your data is sent to. Most companies have one per site or app and a separate one for development; ask which one holds production data.
- Whether data is arriving. The Adobe Experience Platform Debugger, a Chrome extension, shows which report suites a page sends data to. Open your site with it to confirm.
- What each variable means. Ask for the solution design document (often called the SDR). It lists what every eVar, prop and event holds, which saves guessing later.
Navigating the interface
In this section, you will learn to navigate the Adobe Analytics dashboard, which is where every report starts.
Workspace and the components panel
When you log in to Adobe Analytics, you land on Workspace. These are the parts you will use most:
- Analysis Workspace: The browser tool for building reports. Projects hold panels, and panels hold tables and visualizations you build by drag and drop.
- Components: The building blocks of every report: Metrics (how many), Dimensions (which values), Segments (which subset of your data) and Date ranges.
- Projects list: Saved projects, your own and those shared with you. A shared project is often the quickest way to learn how your company reads its data.
Tips for finding your way
- Use the search in the components panel to find a metric or dimension by name, or by its variable number (for example
eVar1). - Favorite the projects you open every week so they are one click away.
- Rename and describe panels so the next person knows which question each one answers.
- Use Adobe’s tutorials: Experience League has short videos for each visualization.
Your first report

This section focuses on basic reporting: building a report, reading its metrics and turning it into a decision.
Building it step by step
- Start with a question, such as which traffic source brings the most orders on mobile?
- Create a project: in Workspace, select Projects, then Create project, and choose a blank project.
- Add a dimension and metrics: drag Marketing Channel into the rows of the freeform table, and Visits and Orders into the columns.
- Filter it: drop a segment for mobile visits at the top of the panel and set the date range.
- Visualize it: add a line visualization to see the trend, or a fallout visualization to see where people leave a funnel.
Props and eVars
Adobe Analytics has two kinds of custom dimension, and most beginner mistakes come from mixing them up:
- Prop: stores a custom value for a single hit. Use it to see what happened on that page or click.
- eVar: stores a custom value and keeps it until it expires. Use it to see what led to a conversion later, such as the campaign or the internal search term.
If a breakdown by an eVar and by a prop with the same name give different numbers, this is usually why.
A practical example: a mobile bounce problem
Objective: A digital analyst for an e-commerce site noticed a high bounce rate on mobile devices coming from Social Media campaigns. They want to isolate the problem.
- Build a freeform table with Marketing Channel in the rows and Visits and Bounce Rate in the columns.
- Drop the mobile segment on the panel and compare the social row with the others.
- Break the social row down by Entry Page to see which landing pages bounce.
- Break the worst entry page down by campaign tracking code to find which campaign sends the traffic.
The answer is usually one of two things: a landing page that does not work on mobile, or a campaign whose tracking is broken, so the visit is counted but what happens next is not.
Comparing Adobe Analytics with other tools

Adobe Analytics and Google Analytics are the two names most beginners compare. Both measure websites and apps; they differ in who they are built for.
- Business complexity: Adobe Analytics is built for large organizations with many data sources and custom reporting needs. Google Analytics is the more common choice for smaller businesses with simpler needs.
- Integration with existing systems: Adobe Analytics works with Adobe Experience Cloud products such as Adobe Target and Adobe Experience Manager. Google Analytics works with Google Marketing Platform and Google Ads.
For Adobe’s own comparison, see Adobe's official page.
When the numbers look wrong
Beginners often blame themselves for numbers that are actually a tracking problem. Four signs point to the implementation, not to your report:
- No data at all: the site may be sending to a different report suite.
- Page views or revenue too high: the tracking library may load twice on the page.
- Conversions credited to odd values: an eVar’s expiration may not match how it is used.
- Pages listed as URLs: the page name variable is not set on some templates.
Report these to whoever owns the tracking. The causes and fixes are in the common mistakes section of our Adobe Analytics implementation guide.
Next steps
Once you can build a freeform table and read it, you have the basics. Our Adobe Analytics guide goes further: segments, attribution, anomaly detection, exports and where to find each part of Adobe’s documentation. If you want to prove what you know, our guide to the Adobe Analytics certification lists the exams and how to prepare. For more on specific features, browse our Adobe Analytics expert guides.
FAQ
How do I get access to Adobe Analytics?
Adobe Analytics is licensed to an organization, not to a person, so there is no public sign-up. Your company’s Adobe administrator adds you in the Admin Console to an Analytics product profile with the report suites you need, and you sign in at experience.adobe.com.
What should a beginner learn first in Adobe Analytics?
Learn the vocabulary (report suite, visit, dimension, metric, segment, eVar, prop), then build a freeform table in Analysis Workspace: one dimension, one or two metrics, one segment and a date range. Everything else in Workspace is a variation of that.
What is the difference between a prop and an eVar?
A prop stores a custom value for a single hit. An eVar stores a custom value and keeps it until it expires, so it can take credit for a conversion that happens later. When the same question gives two answers, check which of the two you broke the report down by.
Do I need to implement Adobe Analytics myself to get started?
Usually not. Most analysts start on a report suite that already receives data. If your company has no implementation yet, that is a separate project for developers or a tagging specialist, covered in our Adobe Analytics implementation guide.