Skip to main content
The Analytics dashboard is where you see whether a test is working. Every time a visitor visits a page, adds something to their cart, reaches checkout, or completes checkout, ABConvert records that event and links it to the visitor’s test group.

Accessing your analytics

To view analytics for a test, go to the test table on your ABConvert homepage and open the Analytics dashboard for that test.
Test table listing tests with status, visitors, uplift, and significance for each test

Open analytics from the test table

How the page is organized

  1. Test info: when the test started, how long it has run, and how traffic is split.
  2. Toolbar: filter the data, check its health, and export orders.
  3. Result summary: whether one test group is better, and how strong the evidence is.
  4. Metric cards: the four key metrics, compared across test groups.
  5. Performance: the detailed numbers behind the summary.
  6. Engagement: how visitors interact with your pages.
  7. Custom Events: how often visitors trigger the merchant-defined actions selected for this test.

The result summary

The summary shows whether one test group is better on your primary metric, for example “Variant A has 30.4% higher Conversion Rate”. Early in a test, it says Collecting data and shows progress toward first results.
Result summary showing Statistically significant, Variant A has 30.4% higher Conversion Rate, and a Confidence of over 99%

The result summary

  • The Confidence number shows how strong the evidence is. At 95% or higher, the result is statistically significant. See Statistical significance.
  • Estimated monthly revenue impact estimates what the best test group would add to your monthly revenue if all traffic saw it. The estimated range applies the 95% confidence interval of the measured difference, so it shows how much that estimate could vary.
Results can change until the test ends. To turn this summary into a decision, see How to interpret Analytics results.

Metric cards

Four cards compare the metrics that matter most for a revenue decision: Revenue per Visitor, Conversion Rate, Average Order Value, and Profit per Visitor.
Four metric cards comparing Control, Variant A, and Variant B, with the Primary badge on Conversion Rate and a Show funnel metrics button below

The four metric cards

  • The Primary badge marks your primary metric.
  • Each card compares every test group against Control.
  • Click Show funnel metrics to add funnel rates such as Add-to-cart Rate and Reached Checkout Rate.
  • Click the expand icon on any card to open a detailed view of that metric, including the uplift range, p-value, and sample size per test group.
Detailed view of the Conversion Rate metric showing the uplift, a range bar for each test group, the p-value, and the sample size per test group

Expand a metric card for the full statistics

Profit metrics use your COGS settings. Until you set up COGS, profit assumes 0% cost.

Performance

Overall

A chart of any metric over time, with the Statistical Significance table below it. See Statistical significance for how to read each column.
Performance section on the Overall tab with a Conversion Rate chart over time and the Statistical Significance table below it

The Overall tab: metric chart and Statistical Significance table

Funnel

The conversion funnel shows where visitors drop off, per test group. It counts sessions at each stage, not visitors, so Sessions is the 100% baseline and a visitor who returns and drops off again counts twice.
Session-Based Conversion Funnel card showing Sessions, Added to Cart, Reached Checkout, and Completed Checkout bars for each test group

The conversion funnel per test group

By default, most tests show a standard 4-step funnel:
1

Sessions

A distinct session in your test. Sessions is always the top of the funnel and serves as the 100% baseline for the funnel rates below it.
2

Added to Cart

The visitor adds the product to their cart. This is the first sign the visitor wants to buy.
3

Reached Checkout

The visitor reaches the checkout page. This shows they moved past browsing and are actively considering buying.
4

Completed Checkout

The visitor completes a purchase.
Every stage is tracked per test group, so you can compare test groups at each point in the funnel, not just at the order level.

Custom funnel steps

You can customize the funnel to track more detailed steps like Shipping Information Submitted or Payment Submitted. This lets you see exactly where visitors drop off in your checkout flow.
  1. Open the Funnel tab in the Performance section.
  2. Click the gear icon in the top right of the funnel.
  3. Select and reorder up to 5 steps. Sessions stays fixed as the baseline.
  4. Click Apply.
Customize funnel dialog with steps for Added to Cart, Reached Checkout, and Completed Checkout, plus controls to add a stage, reset to default, or apply

Customize the funnel steps

Funnel customization is saved in your current browser for this test and Measured by setting. Other team members see their own saved view or the default funnel until they customize it.
To add a merchant-defined action to the funnel, see Use Custom Events in Analytics.

Discount

Discount metrics show how much discount cost contributes to each test group’s result: how many orders used a discount, and how much revenue and profit the discounts cost. See Discount metrics.

Breakdown

The Breakdown table lets you compare the metrics you care about across test groups and audience segments. A segment dimension, such as country or device type, splits the results into one row per value.
  • Use Metrics to choose which columns to compare, such as visitors, orders, conversion rate, or average order value.
  • Select Product, Country, Device Type, Visitor type, or Traffic Source to group results by one preset dimension. See Product breakdown for how the Product tab works.
Each row shows the combined value for every test group, and you expand it to compare the test groups. Counts and money, such as visitors, orders, and total revenue, are added up. Each rate is calculated again from the combined totals with the same formula as the test group values, so CVR (Visitors) is the visitors with orders in all test groups divided by the visitors in all test groups. The combined value is not an average of the test group rates. See Traffic and conversion metrics, Revenue and profit metrics, and Discount metrics for each formula.
Breakdown table with tabs for All, Country, Device Type, Visitor type, Traffic Source, and Custom above test group results

Preset dimensions in the Breakdown table

To combine two dimensions in the same table:
1

Open the custom breakdown

Click Custom in the Breakdown table.
2

Choose the primary dimension

Select the first level used to group results, such as Country.
3

Choose the secondary dimension (optional)

Optionally select a nested level, such as Device Type, to compare segments within each primary dimension.
4

Apply your dimensions

Click Apply to update the table. Use the swap button to reverse the primary and secondary order when needed.
Custom breakdowns can group by Product, Country, Market, Device Type, Visitor type, Traffic Source, Traffic Platform, Referrer Domain, Landing Page, and the five UTM parameters.
Custom breakdown grouped by Country and Device Type, with nested rows per test group

A custom breakdown with two dimensions

In a custom breakdown with two dimensions, each first-level row combines the rows below it, so a visitor who appears under two second-level values counts in both. When one of the two dimensions is Product, the other dimension’s rows count every product in the test, including products the table doesn’t list, and count each visitor once.
Visitor type is not determined by Shopify’s session cookie. ABConvert compares each visitor’s first-seen timestamp with the test start time:If the first-seen timestamp is after the test start time, the visitor is counted as new.If the first-seen timestamp is before the test start time, the visitor is counted as returning.To segment this data correctly, enable the ABConvert app embed in your theme before the test starts and keep it enabled. Visitors tracked only after the embed is enabled may otherwise be treated as new by default.

Product breakdown

The Product tab shows how each product and product variant performed in each test group. It covers every product observed in the test, so you don’t need a product group to use it. Apply a product group only when you want to narrow the table to that group’s products. Product variant rows show Added to Cart, Reached Checkout, Completed Checkout, Orders, Revenue, Profit, Units sold, and Margin. Visitors, sessions, and rates show --- for product variants, because a product view records only the product variant selected when the page loads, and shoppers often switch product variants after that. Products are ranked by revenue. The table shows the first 25; click More products to show 25 more. Each product shows its top product variants by orders; click Show more product variants to see more. When the table can’t list every product or product variant, a warning appears above it:
Product tab of the Breakdown table with the Search products field, the note Showing the top 100 products by revenue, and a warning that some product rows aren't shown because of dataset or per-product limits

The warning shown when some product rows are left out

The warning means the rows on screen are a subset, not that data is missing. Click More products to load the next products by revenue. The totals for each product and product variant row are the same whether or not other rows are left out.

Engagement

The Engagement section shows whether a test group keeps visitors interested: how often they click through, how often they bounce, and how long they stay. Click Show engagement to open it.
Engagement section with Click-Through Rate, Bounce Rate, and Avg Time on Page cards per test group, and a breakdown table below

The Engagement section

Engagement metrics are directional. Use them as an early signal, and rely on order metrics for decisions. See Engagement metrics.

Custom Events

The Custom Events section compares the share of visitors who triggered each selected event in every test group. These results are directional and do not include statistical significance. See Set Up Custom Events and Use Custom Events in Analytics.

The toolbar

The toolbar sits above the result summary. It is where you choose the measurement view, filter the data, check its health, and export orders.
Toolbar with the date range, the measurement view selector showing Visitors who experienced the test, Filters, and Compare controls on the left, and export, refresh, last updated time, and Health on the right

The toolbar

Date range

Pick a preset such as Last 7 days or Start to date, or set custom dates. Useful for checking the impact of a promotion or seasonal change.

Measure results by

The selector between the date range and Filters names the measurement view every number on the page uses. It is not a filter — it decides who counts as the denominator, so read it before you read any rate:
  • Visitors who experienced the test tells you whether the change was effective for the visitors who entered the test experience.
  • Assigned visitors tells you the scale of its commercial impact across the full audience assigned to the test.
Click the selector and pick a view. The choice applies immediately.
Pick one measurement view and stay with it for the whole test. The two views use different denominators, so switching mid-test changes every rate on the page, and a number you read last week no longer compares with one you read today.

What counts as experiencing the test

A visitor is counted under Visitors who experienced the test at the first point where the test could affect them. That point is different for each test type, so exposure means something specific to what the test changes:
A test only offers Visitors who experienced the test if it started after that basis became available for its type. A test that started earlier stays on Assigned visitors for its whole life, so its measurement population never changes mid-test. Theme tests never show the selector: they apply storewide, so every assigned visitor experiences the test.

When an order counts toward a test

An order counts toward a test only if the visitor was still in that test when they checked out. Most conditions in Audience Targeting are settled when a visitor first joins a test and never change. Customer conditions are the exception, because signing in can reveal something the condition cares about. A shopper browsing as a guest gets a test price, then signs in on your storefront as a wholesale customer on a test you limited to retail. From that point the test stops applying to them, and an order they place stops counting toward it.

Filters

The Filters dialog has two settings:

Compare

When a test has more than two test groups, Compare switches between viewing all test groups and one test group against Control. In All groups, the verdict anchors on the strongest test group, ranking significant results first.
Compare dropdown open with Variant A, Variant B, and All groups options

Compare one test group against Control

Export orders

To check results in your own tools, click the Export orders button. It downloads the order data behind the results, up to 10,000 orders.

Refresh

Opening this dashboard recomputes your results if they are more than an hour old, so what you see is at most an hour behind your store. Updated shows when the numbers were last computed. To recompute them now, click Refresh.

Health

Health verifies that the test is collecting trustworthy data. A green dot means every check passed, amber means one needs attention, and gray means the storefront checks have not finished verifying.
Health popover showing passing checks for Traffic split (SRM), Web pixel health, and Theme connection

The three Health checks

It runs three checks:
  • Traffic split (SRM): the actual split across test groups matches the target split.
  • Web pixel health: the web pixel is firing on storefront sessions.
  • Theme connection: the ABConvert app embed is active on your live theme, so visitors see the changes in each test group.
When a check fails, follow the fix action before trusting the affected results.

FAQ

The floor applies to every test group individually, and to both counts: each test group needs at least 100 visitors and 25 orders. A test with 900 visitors in Control but 60 in Variant A is still collecting, and so is a test with 5,000 visitors per test group but 12 orders each.
The line appears when you measure results by Visitors who experienced the test. Total Visitors then counts only the visitors who reached the point where the test could affect them, and the percentage shows what share of assigned visitors that is. Assigned visitors are everyone placed into a test group, whether or not they went on to experience the test. For example, 1,029 with 48.5% of assigned means 2,122 visitors were assigned to a test group and 1,029 of them experienced the test. A low share is normal, not lost data: many visitors never reach the pages the test changes. When you measure by Assigned visitors, the line disappears, because Total Visitors already counts every assigned visitor. See Measure results by for how the two views differ.
Yes. Switch to classic view is under More actions in the test header. The classic layout is frozen: fixes and new metrics land on the current dashboard only, and the switch will be retired.
Search products covers only the products loaded in the Product tab so far. Click More products to load more, then search again.