Adobe Analytics is an enterprise analytics platform used by large retailers, banks, media companies and travel brands to understand digital behavior. This tutorial explains the concepts and the practical steps, from planning variables to implementing with Adobe Experience Platform Tags and the Web SDK, to building reports in Analysis Workspace.
Key takeaways
- Plan first: a solution design reference (SDR) that maps business questions to variables saves months of rework.
- Know the three variable types: eVars (conversion variables), props (traffic variables) and events (metrics).
- New implementations generally use the Adobe Experience Platform Web SDK deployed through Tags (formerly Adobe Launch).
- Analysis Workspace is where most analysis happens, using segments, calculated metrics and visualizations.
Step 1: Understand the data model
- Report suite: the container where data is collected and processed, usually one per site or brand, with optional virtual report suites for filtered views.
- eVars: dimensions that persist beyond the hit according to allocation and expiration settings, used to attribute conversions, for example internal campaign or search term.
- Props: dimensions that apply only to the hit they are set on, useful for traffic analysis and pathing.
- Events: success metrics such as orders, sign-ups or form starts, either counters or numeric.
- Classifications: metadata uploaded to enrich values, such as campaign tracking codes mapped to channel and creative.
Step 2: Write a solution design reference
List business questions, the KPIs that answer them, and the variables and events needed. Document variable names, allocation, expiration and which pages or interactions set them. Share it with developers, analysts and stakeholders so everyone works from the same plan.
Step 3: Build a data layer
A data layer is a JavaScript object on each page that exposes information such as page name, page type, product IDs and user status. Analytics tags read from it instead of scraping the page, which makes tracking more reliable when the site changes.
Step 4: Implement with Tags and the Web SDK
- In Adobe Experience Platform Data Collection, create a datastream and add Adobe Analytics as a service with your report suite.
- Create a Tags property and install the Adobe Experience Platform Web SDK extension, configured with your datastream.
- Create data elements that read from the data layer.
- Create rules, for example “on page load, send event” and “on add to cart click, send event”, mapping data elements into the XDM object or the data object for Analytics.
- Publish through development, staging and production libraries.
Older sites may still use AppMeasurement and the Analytics extension. Both approaches feed the same report suite, but the Web SDK is Adobe’s recommended path for new work and for connecting with other Experience Cloud apps.
Step 5: Validate the data
Use the Adobe Experience Platform Debugger browser extension and Assurance to inspect requests, confirm variables are populated correctly and check that events fire once. Then compare a few days of data in reports against expectations before sharing dashboards.
Step 6: Analyze in Analysis Workspace
- Freeform tables for breaking down metrics by dimensions.
- Segments to focus on hits, visits or visitors that meet conditions, such as mobile users who viewed a product.
- Calculated metrics such as conversion rate or revenue per visit.
- Visualizations such as fallout, flow, cohort tables and attribution panels.
- Intelligent alerts and anomaly detection to catch unusual changes.
Step 7: Share and govern
Curate projects for business users, schedule PDF or CSV deliveries, and use naming conventions and approval for components so the most important segments and metrics are trusted. Data Feeds and Data Warehouse exports provide raw data for data science teams.
Where Customer Journey Analytics fits
Customer Journey Analytics (CJA) is Adobe’s analytics application built on Adobe Experience Platform. It joins web, app, call center and offline data at the person level. Many organizations use Adobe Analytics today and evaluate CJA for cross-channel analysis.
FAQs
Is Adobe Launch still used?
Adobe Launch was renamed Tags and is part of Adobe Experience Platform Data Collection. The concepts of properties, extensions, data elements and rules are the same.
eVar or prop: which should I use?
Use an eVar when you need to tie a value to later conversions. Use a prop for hit-level traffic analysis or pathing.
Learn with Tutorials Mania
Our Adobe Analytics training, Adobe Launch (Tags) training and Adobe Experience Platform training are live and instructor-led with hands-on labs, certification guidance and a free demo. Prepare for interviews with our Adobe Analytics interview questions.