What the metrics mean

Every number on the Analytics page is defined precisely — no metric here is a rough estimate.

The metrics

Metric	What it counts
Campaign salesNet revenue of the order lines a campaign discounted: unit price × quantity, less the discount and any refunds. Converted to your store currency.	Net revenue of the order lines a campaign discounted: unit price × quantity, less the discount and any refunds. Converted to your store currency.
Share of store revenueCampaign sales as a share of everything the store sold in the same date range.	Campaign sales as a share of everything the store sold in the same date range.
OrdersOrders containing at least one line a campaign discounted. An order is counted once however many discounted lines it holds.	Orders containing at least one line a campaign discounted. An order is counted once however many discounted lines it holds.
Added to cartSessions that added a discounted product to the cart from the widget. Counted once per session, not once per click.	Sessions that added a discounted product to the cart from the widget. Counted once per session, not once per click.
Widget seenSessions in which the widget actually rendered on a product page. Counted once per session.	Sessions in which the widget actually rendered on a product page. Counted once per session.
Tier clicks	Sessions that selected a discount level in the widget. Counted once per session, the same way as Widget seen and Added to cart.

Campaign sales is the one metric worth understanding in full — it’s also what your plan’s usage cap is measured against. See How campaign sales is calculated.

Note

The campaign breakdown table further down the page (by tier, by product) counts every click and add-to-cart, not unique sessions — it answers “how much activity happened,” a different question from the funnel above it, which answers “how many people got this far.”

The funnel

The funnel reads top to bottom as unique sessions per stage, with each percentage showing the step down from the stage above it:

1. Store visits
2. Product views
3. Widget seen
4. Tier clicks
5. Added to cart
6. Orders

A session only advances if it did what the stage before it describes — someone who saw the widget but never clicked a level stops at Widget seen. Opening a single campaign’s own breakdown drops the first stage: store visits are shop-wide, not specific to one campaign, so that funnel starts at Product views instead.

Tip

A shopper who saw two campaigns in the same visit is counted once per campaign, so a shop-wide step can legitimately run past 100% of the stage above it. That’s not a bug — the same session is doing double duty.

Needs attention

Below the campaign table, a Needs attentionDerived from the same counters — each one links to the fix. section flags active campaigns with signs of a display problem: no widget impressions despite product traffic, or impressions on fewer than half of product views. Each note links straight to the likely fix — see Troubleshooting for the same causes in more detail.

Date ranges and comparison

Pick Last 7 days, Last 30 days, Last 90 days, or a custom range up to 90 days. Every number on the page is compared automatically against the immediately preceding period of the same length — a custom 12-day range compares against the 12 days right before it, not the same dates last month or last year.

Ranges are measured in your store’s own timezone, so “today” ends when your store’s day does, not when UTC’s does.

Cross-link: How campaign sales is calculated, Troubleshooting.