Adobe Commerce Analytics: Complete Implementation Guide for 2026

E-commerce teams generate massive amounts of transaction data, customer behavior signals, and campaign performance metrics. Adobe Commerce Analytics turns this data into actionable insights — but only when properly configured and integrated with your broader marketing stack.

This guide walks you through implementing Adobe Commerce Analytics for your e-commerce operation. You'll learn how to set up tracking, connect data sources, build reports, and integrate with downstream analytics tools. Whether you're migrating from Magento Business Intelligence or implementing Commerce Intelligence for the first time, this guide covers the technical steps and strategic decisions that determine success.

Key Takeaways

✓ Adobe Commerce Analytics (formerly Magento Business Intelligence) provides native e-commerce tracking for Adobe Commerce and Magento installations

✓ Implementation requires configuring data warehousing, setting up report suites in Adobe Analytics, and mapping commerce events to analytics dimensions

✓ Integration with external marketing platforms demands either custom API work or a dedicated data pipeline tool to move data beyond Adobe's ecosystem

✓ Proper schema design and metric definitions at setup prevent months of rework later — plan your data model before connecting sources

✓ Marketing teams report steep learning curves with Adobe Analytics interfaces; budget time for training and documentation

✓ Real-time dashboards require streaming data architecture — batch sync models introduce 4–24 hour lag in commerce reporting

What Is Adobe Commerce Analytics

Adobe Commerce Analytics is the integrated business intelligence and reporting layer built into Adobe Commerce (formerly Magento). It combines Commerce Intelligence — the data warehouse and visualization tool previously sold as RJMetrics and Magento BI — with the behavioral tracking capabilities of Adobe Analytics.

The platform collects transactional data (orders, products, customers), website behavior (page views, cart actions, checkout flows), and marketing campaign data (UTM parameters, referral sources, promotional codes). This data flows into a centralized warehouse where teams build reports, dashboards, and customer segments.

Commerce Intelligence handles structured e-commerce metrics: revenue by product, customer lifetime value, repeat purchase rates, inventory turnover. Adobe Analytics adds behavioral dimensions: session paths, drop-off points, A/B test results, cross-device attribution. Together, they provide visibility from first click to final purchase.

The system works natively with Adobe Commerce storefronts but requires configuration for external platforms. If your stack includes Shopify, WooCommerce, or custom commerce APIs, you'll need middleware to pipe that data into the Adobe ecosystem.

Step 1: Configure Commerce Intelligence Data Warehouse

Start by defining your data warehouse schema. Commerce Intelligence creates tables for orders, customers, products, and coupons automatically when connected to an Adobe Commerce database. Your job is to decide which additional tables and columns you need for custom reporting.

Log into Commerce Intelligence and navigate to Manage Data > Data Warehouse Manager. You'll see a list of detected tables from your commerce database. Review the automatically synced columns — typically transaction_id, customer_id, product_sku, order_total, created_at timestamps.

Add custom dimensions you'll filter and group by later. Common additions include:

• Customer acquisition source — first touchpoint channel before purchase

• Product category hierarchy — nested taxonomy for rollup reports

• Fulfillment region — warehouse or distribution center

• Discount attribution — which promo code drove the order

• Payment method — credit card, PayPal, net terms

Set sync schedules for each table. Real-time commerce reporting requires updates every 15–30 minutes. Batch reporting can run once daily. Balance freshness needs against database load — frequent syncs on large order tables can slow production systems during peak hours.

Mapping Custom Commerce Events

Adobe Commerce fires standard events (product view, add to cart, purchase) automatically. Custom events — wishlist additions, product comparisons, size guide opens — require manual instrumentation.

Define each event in Admin > Stores > Configuration > Adobe Analytics > Events. Specify the event name, the trigger condition (JavaScript function or backend action), and which data layer variables to capture. For a "Request Restock" button, you'd log the product SKU, customer email, and timestamp.

Map these events to Adobe Analytics custom events (event1 through event1000). Document your schema in a shared sheet — after six months, no one remembers that event47 means "filter applied on category page."

Defining Calculated Metrics

Commerce Intelligence supports SQL-based calculated columns. Use these for metrics that don't exist in raw tables:

• Customer lifetime value (CLV) — sum of all order totals per customer_id

• Days since last purchase — date difference between today and max(order_date)

• Average order value (AOV) — total revenue / order count by time period

• Repeat purchase rate — customers with 2+ orders / total customers

Create these in Manage Data > Data Warehouse Manager > Create New Column. Write the calculation logic, set the update frequency, and save. These columns become available as dimensions in all downstream reports.

Step 2: Connect Adobe Analytics Report Suite

Adobe Analytics handles behavioral tracking — what users do on your site before, during, and after purchase. Commerce Intelligence handles transactional reporting — what happened when they bought. Connecting the two systems lets you answer questions like "Which blog posts drive highest CLV customers?" or "Do email vs. paid social visitors have different return rates?"

In Adobe Analytics, create a dedicated report suite for your commerce property. Navigate to Admin > Report Suites > Create New > Standard Template. Select the "Commerce" template — it pre-configures common e-commerce events and dimensions.

Define your success events:

• event1 — Product Views

• event2 — Cart Additions

• event3 — Checkouts

• event4 — Orders

• event5 — Revenue (currency event)

Map these to Commerce Intelligence transaction events. In Commerce Intelligence, go to Integrations > Adobe Analytics and authenticate with your Adobe ID. Select the report suite you just created. The integration imports dimensions (traffic source, device type, geo) and metrics (sessions, conversion rate) into your warehouse as new tables.

Configuring Cross-Domain Tracking

If your checkout flow spans multiple domains — for example, store.yoursite.com redirects to secure-checkout.paymentprovider.com — configure cross-domain tracking to preserve visitor IDs.

In your Adobe Analytics implementation (Launch or AppMeasurement.js), set the s.trackingServer and s.trackingServerSecure variables to a first-party domain you control. Add all checkout domains to the s.linkInternalFilters array. This prevents session breaks when users move between domains.

Test with Adobe Debugger (browser extension). Trigger a checkout flow and verify the same s_ecid cookie value persists across all domains.

Setting Merchandising eVars

Merchandising eVars bind dimension values to specific products at the time of interaction. Standard eVars apply page-wide; merchandising eVars let you say "this product was added to cart from a recommendation widget" while simultaneously saying "that product was added from search results."

Configure in Admin > Report Suites > Edit Settings > Conversion > Conversion Variables. Set the eVar to "Product Syntax" binding. In your tracking code, pass the dimension with the product string:

s.products=";SKU123;1;99.00;event2=1;eVar1=recommended"

Now you can report revenue by recommendation source, filtered to only purchases where the product entered the cart via that source.

Step 3: Implement Data Layer and Tracking

Adobe Analytics reads from a JavaScript data layer — a structured object containing page context, user state, and commerce variables. Without a clean data layer, tracking becomes a mess of inline scripts and inconsistent naming.

Define a global digitalData object that populates on every page load. Structure it according to Adobe's recommendations:

window.digitalData = {
  page: {
    pageInfo: {
      pageName: "Product Detail: Widget Pro",
      pageCategory: "Product",
      pageType: "PDP"
    },
    category: {
      primaryCategory: "Electronics",
      subCategory: "Widgets"
    }
  },
  product: [{
    productInfo: {
      productID: "SKU123",
      productName: "Widget Pro",
      price: 99.00,
      inStock: true
    },
    category: {
      primaryCategory: "Electronics"
    }
  }],
  user: [{
    profile: [{
      profileInfo: {
        customerID: "CUST789",
        loggedIn: true
      }
    }]
  }]
};

Your Adobe Launch rules or AppMeasurement.js code reads from this object to populate analytics variables. This separation keeps tracking logic independent of page markup changes.

Tagging Checkout Funnel Steps

Track each checkout stage as a distinct event. Define funnel steps in Commerce Intelligence:

• Step 1: Cart Review — user views cart page

• Step 2: Shipping Info — user enters shipping address

• Step 3: Payment Info — user enters payment method

• Step 4: Order Review — user reviews full order before submit

• Step 5: Confirmation — order complete, transaction ID issued

Fire a custom event at each step. Pass the cart total and item count as context variables. In Adobe Analytics, create a fallout report to visualize drop-off between steps.

Handling Single-Page Applications

If your storefront is a React or Vue SPA, page views don't trigger traditional page loads. Implement virtual page views by calling s.t() manually on route changes:

router.afterEach((to, from) => {
  window.digitalData.page.pageInfo.pageName = to.name;
  s.t(); // triggers page view
});

For interaction events (add to cart, filter applied), use s.tl() for link tracking instead of full page views.

Step 4: Build Core Commerce Reports

With data flowing into Commerce Intelligence and Adobe Analytics, build the reports your team checks daily. Start with pre-built templates, then customize for your business model.

In Commerce Intelligence, navigate to Report Builder. The commerce template includes:

• Revenue Over Time — daily, weekly, monthly trends

• Orders by Channel — acquisition source breakdown

• Top Products — revenue and unit sales by SKU

• Customer Cohorts — repeat purchase behavior by signup month

• Average Order Value Trends — AOV changes over time

Customize each report's date range, filters, and grouping. For example, filter "Orders by Channel" to only include orders above fifty dollars to see which channels drive high-value customers versus bargain hunters.

Creating Customer Lifetime Value Segments

Segment customers by total spend to date. Create a calculated column for CLV (sum of order totals per customer). Then build segments:

• Segment A — CLV below fifty dollars

• Segment B — CLV between fifty and two hundred dollars

• Segment C — CLV between two hundred and five hundred dollars

• Segment D — CLV above five hundred dollars

Export these segments to Adobe Analytics as audiences. Use them to personalize content, trigger re-engagement campaigns, or exclude high-value customers from discount promotions.

Setting Up Attribution Reports

Adobe Analytics supports multiple attribution models — first touch, last touch, linear, time decay, algorithmic. Apply different models to the same conversion data to understand channel contribution.

In Workspace, create a freeform table with "Marketing Channel" as the dimension and "Orders" as the metric. Click the metric header, select Column Settings > Use non-default attribution model, and choose your model.

Compare last-touch attribution (gives all credit to the final click) with first-touch (credits initial discovery) and linear (spreads credit evenly across all touchpoints). Channels like display and content marketing often look weak in last-touch but strong in first-touch models.

Step 5: Integrate External Marketing Platforms

Adobe Commerce Analytics doesn't natively connect to most marketing tools — email platforms, ad networks, CRMs, customer data platforms. Moving data between Adobe and these systems requires custom API integrations or a middleware layer.

Common integration patterns:

Email Marketing (Klaviyo, Braze, Iterable): Export customer segments and product affinity data from Commerce Intelligence. Push via CSV upload or API. Trigger flows based on purchase behavior — abandoned cart, post-purchase upsell, win-back campaigns.

Advertising Platforms (Google Ads, Meta, LinkedIn): Send high-CLV customer lists as match audiences for lookalike targeting. Export via CSV or use the Google Ads API to upload hashed emails. Refresh weekly to keep audiences current.

CRM Systems (Salesforce, HubSpot): Sync order history and customer lifetime value into contact records. Use Salesforce's Bulk API or HubSpot's CRM API. Map customer_id from Commerce Intelligence to contact_id in the CRM.

Data Warehouses (Snowflake, BigQuery, Redshift): Replicate Commerce Intelligence tables into your central warehouse for cross-platform analysis. Use Adobe's Data Warehouse export feature or build ETL jobs with Fivetran, Stitch, or custom Python scripts.

API Integration Constraints

Adobe provides APIs for pulling data out of Analytics (Reporting API, Data Warehouse API) and pushing segments in (Audience Manager API). Rate limits and data freshness vary:

• Reporting API — 120 requests per minute, data delayed 30–90 minutes

• Data Warehouse — batch exports, 4–24 hour delivery

• Audience Manager — segment updates propagate in 24–48 hours

For real-time use cases — dynamic site personalization, instant fraud detection — these delays are prohibitive. Teams either build streaming pipelines with Adobe Experience Platform (expensive, complex) or use third-party data activation tools.

When to Use a Marketing Data Pipeline

If you're connecting more than three external platforms, or if you need sub-hour data freshness, a dedicated marketing data pipeline becomes cost-effective. These tools — Improvado, Fivetran, Segment — handle API authentication, schema mapping, incremental sync, and error handling.

Improvado connects Adobe Commerce Analytics alongside 1,000+ other marketing and sales platforms. Data flows into a unified schema optimized for marketing analysis — no SQL required. Analysts query pre-joined tables instead of writing complex joins across disparate sources.

The platform includes Marketing Data Governance features — 250+ pre-built validation rules catch tracking errors, budget overruns, and schema breaks before they corrupt reports. Implementation typically completes within a week, with dedicated support included rather than sold as an add-on.

Limitation: Improvado is built for marketing and sales use cases. If your primary need is product analytics, operational BI, or engineering dashboards, traditional ETL tools or custom pipelines may fit better.

Step 6: Configure Alerts and Anomaly Detection

Commerce data changes constantly. Conversion rates drop, ad spend spikes, inventory runs low. Alerts notify you when metrics cross thresholds or deviate from expected patterns.

In Commerce Intelligence, navigate to Manage Data > Alerts. Create alerts for:

• Revenue drops — daily revenue below 80% of seven-day moving average

• Conversion rate dips — checkout completion rate below 2.5%

• Inventory alerts — top SKUs with fewer than 10 units remaining

• Fraud spikes — orders from high-risk regions exceed five per hour

Set notification channels — email, Slack, PagerDuty. Assign alerts to the team members who can act on them. Don't send every alert to everyone; alert fatigue kills responsiveness.

Using Adobe Analytics Anomaly Detection

Adobe Analytics includes statistical anomaly detection powered by machine learning models. It learns your metric's normal range and confidence bands, then flags unexpected spikes or drops.

In Workspace, add a line chart visualization. Click the metric name, select Show Anomaly Detection. The chart displays gray confidence bands and highlights anomalous data points in red or green.

Review flagged anomalies weekly. Investigate causes — was it a successful campaign, a tracking bug, a bot attack, a holiday weekend? Document findings so future analysts understand historical patterns.

Step 7: Optimize Report Performance

As data volume grows, reports slow down. Queries that returned instantly with six months of data take minutes with three years. Optimize before performance becomes a blocker.

Aggregating Historical Data

Commerce Intelligence recalculates metrics on every query unless you pre-aggregate. For reports that analyze trends over years, pre-calculate daily or monthly summary tables.

Create a daily_revenue_summary table with columns for date, total_revenue, order_count, average_order_value. Run a nightly SQL job to populate it. Point long-range trend reports at this summary table instead of raw order tables.

Indexing Frequently Filtered Columns

If you filter reports by customer segment, product category, or acquisition channel, index those columns in your data warehouse. In Redshift or Snowflake, create indexes or sort keys on frequently queried dimensions.

Monitor query execution plans. If a report scans millions of rows to filter a few thousand, add an index.

Caching Dashboard Results

Dashboards that update every 15 minutes don't need to query live data every time someone opens them. Enable caching in Commerce Intelligence under Dashboard Settings > Cache Results. Set cache lifetime to match your data update frequency — if the warehouse syncs hourly, cache for 60 minutes.

Common Mistakes to Avoid

Skipping schema planning before connecting sources. Teams connect their commerce database, realize they're missing key dimensions (customer acquisition source, product margin, promotional attribution), and have to retroactively add columns. Plan your reporting needs first, then configure tracking to capture that data from day one.

Using default attribution models without understanding what they measure. Last-touch attribution gives all credit to the final click before purchase. This systematically undervalues top-of-funnel channels like content marketing and brand campaigns. Apply multiple attribution models to the same data before making budget decisions.

Treating Commerce Intelligence and Adobe Analytics as separate systems. The two platforms have overlapping capabilities but different strengths. Commerce Intelligence excels at transactional analysis — cohort retention, product performance, customer lifetime value. Adobe Analytics handles behavioral analysis — session paths, content engagement, A/B tests. Use both, don't pick one.

Ignoring data governance until reports conflict. Two analysts define "active customer" differently. Marketing counts anyone who opened an email; finance counts anyone who purchased in the past year. Conflicting definitions produce conflicting reports. Document metric definitions in a shared glossary before building dashboards.

Building reports before validating data quality. Tracking bugs, schema changes, and API failures corrupt data silently. Validate data completeness and accuracy before trusting reports for decisions. Check order totals in Commerce Intelligence against your payment processor. Verify session counts in Adobe Analytics against server logs.

Over-segmenting audiences without statistical significance. Slicing data into dozens of micro-segments produces misleading results when sample sizes are small. A segment with 20 customers and a 15% conversion rate doesn't tell you much — the confidence interval spans 5% to 35%. Maintain minimum segment sizes (typically several hundred customers) for reliable analysis.

Tools That Help with Adobe Commerce Analytics

Adobe's ecosystem is powerful but closed. Moving data in and out requires additional tools for most use cases.

For teams running complex marketing stacks — Adobe Commerce plus email, paid media, CRM, and analytics tools — Improvado eliminates the integration work. Data syncs automatically, arrives in a consistent schema, and updates without manual intervention. The platform handles connector maintenance when APIs change, preserving historical data even when source schemas break.

Maintaining Adobe Commerce Analytics Over Time

Implementation is the start, not the finish. Commerce Analytics requires ongoing maintenance as your business evolves.

Quarterly schema reviews: Audit your data warehouse schema every quarter. Remove unused tables and columns. Add new dimensions for product launches, market expansions, or campaign types. Update calculated metrics when business logic changes.

Monthly tracking audits: Test critical tracking flows — checkout completion, add-to-cart events, campaign attribution. Use Adobe Debugger to verify data layer population. Check that UTM parameters pass through your entire funnel.

Weekly report validation: Compare Adobe Analytics order counts against payment processor records. Verify revenue totals match accounting systems. Investigate discrepancies immediately — they indicate tracking breaks or data pipeline failures.

Annual attribution model reviews: Marketing mix changes over time. A model that accurately credited channels two years ago may not reflect current strategy. Re-evaluate attribution models annually and adjust reporting to match how your team actually drives growth.

Conclusion

Adobe Commerce Analytics provides deep visibility into e-commerce performance when properly implemented. The system combines transactional data from Commerce Intelligence with behavioral tracking from Adobe Analytics, giving teams insight from first visit to repeat purchase.

Success depends on careful planning. Define your reporting needs before configuring tracking. Design a clean data layer that separates content from analytics logic. Document metric definitions so the entire team interprets data consistently. Build data quality checks into your pipelines rather than discovering errors in production reports.

For teams managing complex marketing stacks, integration becomes the primary challenge. Adobe's tools work well within their ecosystem but require custom work to connect external platforms. Data pipeline tools eliminate this integration burden, letting analysts focus on insights rather than API maintenance.

FAQ

What is the difference between Adobe Commerce Intelligence and Adobe Analytics?

Adobe Commerce Intelligence (formerly Magento BI) is a data warehouse and reporting tool purpose-built for e-commerce transaction analysis. It stores order data, customer records, and product information, then provides SQL-based reporting on revenue, cohorts, and lifetime value. Adobe Analytics is a behavioral analytics platform that tracks user interactions across websites and apps — page views, clicks, session paths, and conversion funnels. Commerce Intelligence answers "how much did we sell and to whom?" while Adobe Analytics answers "what did users do before they bought?" Most implementations use both: Commerce Intelligence for business performance metrics, Adobe Analytics for user behavior and attribution.

How long does Adobe Commerce Analytics implementation take?

Basic implementation — connecting your Adobe Commerce database to Commerce Intelligence and configuring standard reports — typically takes two to four weeks for a mid-sized store. This includes data warehouse setup, schema configuration, and building core dashboards. Full implementation with custom tracking, Adobe Analytics integration, external platform connections, and team training extends to two to three months. Complexity increases with custom checkout flows, multi-store setups, and large product catalogs. Plan additional time for data quality validation and historical data migration if you're switching from another analytics platform.

Can I use Adobe Commerce Analytics with Shopify or other platforms?

Adobe Commerce Analytics is designed for Adobe Commerce (Magento) and integrates natively with that platform's database structure. You can technically connect Shopify or other e-commerce systems by building custom data pipelines that transform external schemas into the format Commerce Intelligence expects, but this requires significant engineering work. Adobe Analytics (the behavioral tracking layer) works with any website via JavaScript tagging, regardless of the commerce platform. For multi-platform setups or non-Adobe storefronts, dedicated marketing data pipeline tools offer pre-built connectors that normalize data from Shopify, WooCommerce, BigCommerce, and other systems into a unified schema.

What skills do I need to manage Adobe Commerce Analytics?

Commerce Intelligence requires SQL proficiency for custom reports and calculated columns. Adobe Analytics demands understanding of JavaScript for tracking implementation and data layer design. Marketing analysts need to understand statistical concepts — attribution modeling, cohort analysis, funnel visualization — to interpret reports correctly. Database administration skills help optimize warehouse performance as data volume grows. For integration work, you'll need API development experience (REST APIs, OAuth authentication, error handling) or access to engineers who can build and maintain data pipelines. Many teams hire a dedicated marketing operations or analytics engineer role to manage the technical stack while business analysts focus on insight generation.

How much does Adobe Commerce Analytics cost?

Adobe Commerce Analytics pricing is custom and varies based on order volume, data sources, and feature requirements. Commerce Intelligence is included with Adobe Commerce plans but has tiered pricing for standalone use. Adobe Analytics is sold as part of Adobe Experience Cloud with pricing based on server calls (page views and events tracked). Enterprise implementations with Adobe Experience Platform add significant cost. For accurate pricing, request quotes directly from Adobe sales. Budget for implementation services, ongoing training, and potential integration costs if connecting external platforms.

How do I handle GDPR and privacy compliance?

Adobe Commerce Analytics supports GDPR, CCPA, and other privacy regulations through built-in data governance features. Configure data retention policies in Commerce Intelligence to automatically delete customer data after a specified period. Use Adobe Analytics' privacy controls to honor opt-out requests and exclude IP addresses from tracking. Implement consent management on your storefront — tools like OneTrust or Cookiebot integrate with Adobe Analytics to block tracking until users consent. Document your data processing activities and update privacy policies to disclose analytics usage. For customer data deletion requests, use Commerce Intelligence's API to purge records from your warehouse and Adobe's Privacy Service API to remove data from Analytics and Audience Manager.

What reports should I build first?

Start with revenue and order trend reports — these validate that data is flowing correctly and provide immediate business value. Add customer acquisition source reports to understand which channels drive purchases. Build cohort retention analysis to measure repeat purchase behavior by customer signup period. Create product performance dashboards showing revenue, units sold, and return rates by SKU. Add checkout funnel reports to identify drop-off points. Finally, implement customer lifetime value segmentation to prioritize high-value customer groups. This progression moves from validation (is data accurate?) to optimization (where should we invest?) while building team confidence in the system.