Insights
Analytics
Four tiles, a chart of any metric, a discount type filter, By day and By discount tables with CSV export, and what the storefront pixel collects.
Opening the Analytics page
Open the app
Open xDiscount from Apps in your Shopify admin.
Go to Analytics
Click Analytics in the app’s sidebar.
Pick a range
Use the date button at the top. It is labelled with the range you are looking at, Last 7 days when the page first opens, and clicking it lists Today, Last 7 days, Last 30 days and Last 90 days, with a custom range below the divider.
Narrow the metrics if you want to
Beside the date button, the All metrics chip narrows what the chart can plot and which columns the By day table shows. Click it for a small card of three choices: All metrics, Storefront metrics (approximate) for product views, added to cart and checkouts seen, or Shopify metrics (exact) for discounted orders and discounted revenue. The four tiles never narrow, and your choice is remembered on this browser.
To set a custom range, type a From and a To date as YYYY-MM-DD and click Apply. Cancel, or Escape, discards dates you typed but did not apply, so the button never labels a range that was not actually fetched. Reversed dates are swapped, not rejected. Days are UTC calendar days, the same way they are counted everywhere else in the app.
The range lives in the page address, so a reload or a shared link lands on the same numbers, and it is the same range the Performance strip on Home uses. Moving between the two screens does not change it. The date button is greyed out while numbers are loading, and picking a range re-reads everything on the page together, so tiles, chart and table always cover the same window. While a new range loads, what is already on screen stays put and dims slightly, with a small spinner beside the date button.
What you get is four tiles, a chart of any one of them and a day-by-day table. The update adds a By discount table with one row per discount, and a CSV of it. See The By discount table below.
The Analytics page, the storefront pixel and the campaign order field are included on every plan, Free included. Nothing on this screen is held back for an upgrade.
How far back the history goes
History reaches back 250 days at most. If a custom range starts earlier than that, the page shows what it has and an information banner says where the range really starts: “History goes back 250 days, so this range starts on …”
The four tiles
The first row of the page is four plain cards, always in this order: the metric’s name, and the figure under it. Money first, then orders, then the two ratios. Hover any card, or tab to it, or tap it, and it tells you where its number comes from and how exact it is. The same answers are in the table below.
| Tile | What it counts | Where it comes from | Exact? |
|---|---|---|---|
| Discounted revenue | The full totals of the orders that used one of your discounts, shipping and taxes included, in your store’s currency | Shopify’s own order webhook | Exact |
| Discounted orders | Orders where xDiscount actually reduced the price | Shopify’s own order webhook | Exact |
| Average order value | Discounted revenue divided by discounted orders | Derived from the two above | Exact |
| Conversion rate | Discounted orders divided by product views | Derived | Not applicable |
The shopper’s journey, Product views, Added to cart, Checkouts started and Checkouts seen, is on the page too, as the chart’s metric choices and as columns of the By day table below. A few things are worth knowing about how those are counted:
- Added to cart counts units. A shopper adding three of the same item adds 3 to the number, not 1.
- Checkouts started carries no money. Nothing has been charged at that point, so counting a total there would be counting a sale that may never happen. The gap between Checkouts started and Discounted orders is your checkout abandonment, and it is the one number on this page Shopify’s own discount reports cannot give you.
- Product views and Added to cart are not filtered to discounted products. They count activity across your product pages, so they are a traffic baseline to read the later steps against, not a count of shoppers who saw an offer. That is why the chart says Product views, not “offer views”, and why Conversion rate is orders over all product views, a store-wide rate rather than an offer’s.
The Discounted revenue tile has one honest exception. Orders counted before this figure existed carry a count and no money, so a range made only of them does not print 0.00. It shows a dash, and hovering it, or reading it with a screen reader, says “Not recorded. These orders were counted before their totals were kept.” A zero would claim nobody paid. The truth is that the figure was never recorded. New orders fill it in from the moment they arrive.
Within a range that has activity, a real zero is shown as a zero. A range with no activity at all is a different case, covered in The other states this page can show below.
The chart
Under the tiles is a line chart of one metric at a time. Its heading is the metric’s name, and the Chart metric dropdown in the top-right corner switches between Product views, Added to cart, Cart viewed, Checkouts started, Checkouts seen, Discounted orders and Discounted revenue. The dates the chart covers are printed beneath it.
- One point per day, zero days included. Quiet days are drawn as zeros, never skipped.
- Hover along the plot and a crosshair snaps to the nearest day, with a readout of that day’s date and value. The same readout works from the keyboard: focus the chart, then use Left and Right to walk day by day, Escape to clear.
- Only the latest point carries a printed value. Every other day is in the readout and in the By day table below.
- A metric with nothing to draw in this range shows a sentence instead of an empty axis, for example “No product views between Sep 9, 2026 and Sep 15, 2026.”
The chart is a viewing preference. Switching it changes nothing about the page address or the data, only which line you are looking at.
Why “Checkouts seen” and “Discounted orders” disagree
They will differ, and that is expected:
“Checkouts seen” comes from the storefront and is approximate: ad blockers and shoppers who decline analytics are not counted. “Discounted orders” comes from Shopify itself and is exact.
Checkouts seen is a storefront signal, and so is Checkouts started. Both are missed whenever a shopper runs an ad blocker, declines analytics tracking in your store’s privacy settings, or closes the tab before the beacon leaves. Nothing is retried.
The two are different moments. Checkouts started is reaching the checkout, and Checkouts seen is the pixel witnessing it completed. A shopper who abandons is counted in the first and not the second.
Discounted orders arrives on a Shopify-signed order webhook. An order is counted only when the order carries an xDiscount discount and your store has at least one discount registered with Shopify. That is the same test your billing uses when it counts an order against your plan’s included orders, so the two are counting the same orders.
Which number to trust
Treat Discounted orders as the number of record. Use the three pixel steps for shape and trend, not for accounting.
Filtering by discount type
Beside the date range is a filter chip. It starts on All and offers your four discount types:
| Choice | What the page then shows |
|---|---|
| All | Everything your storefront recorded, plus every discounted order |
| Percentage | Only activity on products covered by a percentage discount |
| Fixed amount | Only activity on products covered by a fixed-amount discount |
| Buy X get Y | Only activity on products covered by a Buy X get Y discount |
| Free shipping | Only activity on products covered by a free-shipping discount |
Every number on the page follows the chip: the tiles, the chart and the By day table. The By discount table follows it too.
How an event gets its type. A product belongs to one discount for each kind of buyer, so a product page view, an add to cart, or a checkout resolves to one kind, or to two when the product has a discount for retail shoppers and another for B2B buyers: the event then counts under both types, as the visit could be either. A product no discount covers counts under All and under no type, which is why the four types will not account for all of your product views. That is your untargeted catalogue, and it is meant to be there as a baseline.
The four types add up to more than All
That is correct, not a rounding error. One checkout can contain a percentage product and a Buy X get Y product. It is one checkout under All, and it is honestly counted under both types, because “checkouts that contained a percentage discount” is the question the filter asks. All is measured in its own right, never added up from the four.
Archiving frees a product. An archived discount no longer covers its products, so activity on them stops appearing under that type, exactly as the discount form stops reserving them.
After you change a discount’s type, new events follow the new type within about a minute. Nothing already recorded is rewritten. A day that happened under the old type stays where it was, because it is what happened.
The By discount table
Below the chart, By discount lists one row per discount for the range and the discount type you picked, with four columns:
| Column | What it is | Where it comes from |
|---|---|---|
| Discount | The discount’s name as it reads in the app today. A deleted discount keeps the name it had | Your discounts |
| Discounted orders | Orders this discount took money off, each counted once | Shopify’s order webhook |
| Amount given | What this discount took off those orders, items and shipping together, in your store currency | The discount amounts Shopify recorded on each order, added up |
| Order totals | The full totals of those orders, shipping and taxes included, in your store currency | The order total Shopify recorded on each order, added up |
None of these come from the storefront pixel, and none of them are estimates. Each money figure is the exact sum of amounts Shopify wrote on the orders when they were placed, in your store’s own currency, so you can check any row against the orders themselves. The Discounted revenue tile reads the same order data, counted once per order, so an order that used two of your discounts is once in the tile and under both discounts here.
Sorting. The table opens with the discount with the most discounted orders at the top. Click any column heading to sort by it, and click it again to reverse the order. Ties are broken by Amount given, then by name. A range with more than 30 discounts is split into pages, like By day.
An order that used two of your discounts is counted under both, and its whole total is added to both rows. That is why the table has no totals row and why its rows do not add up to the tiles: adding them would count such an order twice.
Two discounts with the same name. If two of your discounts print the same name at checkout and have the same value, such as 10% off each, Shopify’s order records only that name and value, so it cannot say which of the two applied. Those orders go to one row named after the checkout name, marked “Shared by 2 discounts with this checkout name. The order does not say which one applied.” The app warns you when you give a second discount a name that is already in use, and a different name, or a different checkout label, keeps their orders apart. A row marked “Not matched to one discount” is an order whose discount is named only by an older checkout title.
Refunds and cancellations are not taken off. Each order is counted on the day it reached the app, with the amounts it was placed with, the same way the Discounted orders tile counts it. A refund, return or cancellation later does not change the row. For figures after returns, use Shopify’s own sales reports, grouped by order.metafields.xdiscount.campaign. See Where the revenue numbers are below.
Your store currency only. Amounts are in the currency your store reports in, not the currency a shopper paid in. If your store ever changed its currency, a discount gets one row per currency, and amounts in different currencies are never added together.
History. The table counts orders from the day it was added to xDiscount. When the range you picked starts earlier than the first order it holds, the table says so: “The first order in this table is from …. Orders placed before this table was added to xDiscount are not in it.” Older orders are still in the Discounted orders tile and in your Shopify reports.
Days are counted the same way as everywhere else on this page: whole calendar days in UTC, on the day the order reached the app.
Your assistant reads it too. With Connect AI, the readPerformance tool gives an assistant the same rows for the days it asks about, added up the same way, so “which discount brought the most orders?” gets the table’s answer. See Connect AI.
Exporting the table as CSV
Click Export CSV at the top of the card. Your browser saves a file named like xdiscount-by-discount-2026-10-14-to-2026-10-20.csv, with the dates of the range on screen. It holds every row of the table, all pages, in the order you sorted it, under this header row:
Discount,Discounted orders,Amount given,Order totals,Currency,Note- Money is written as plain numbers with your currency’s own decimals, such as
1234.50, with no currency symbol and no thousands separator, so a spreadsheet can add them up. The Currency column says which currency they are in. - Note carries the shared name or unmatched explanation for those rows, and is empty otherwise.
- The file is UTF-8, so names with accents, Arabic, Japanese or emoji open correctly in Excel, Numbers and Google Sheets. A name that holds a comma, a quote or a line break is quoted, so it stays in its own cell.
- A name that starts with
=,+,-or@is written with a leading apostrophe, so a spreadsheet shows it as text instead of running it as a formula.
The button is greyed out when the table has no rows.
What the card shows when there is nothing to list
| State | What you see |
|---|---|
| Loading | A placeholder card with a few grey lines, on the first load only. Later range switches keep the table on screen and dim it |
| No orders | “No discounted orders between … and ….” When the range is older than the table, it adds that earlier orders are not counted here |
| Read failed | A red banner headed Couldn’t load the By discount table, with a Try again button. The rest of the page still shows |
| Range too long | The same banner, asking for a shorter range, when a range holds more rows than the table can add up at once. It never shows part of a total |
The By day table
Below the chart, By day lists one row per day with eight columns:
| Day | Product views | Added to cart | Cart viewed | Checkouts started | Checkouts seen | Discounted orders | Discounted revenue |
|---|
- Newest day first.
- Days with nothing on them are shown as zeroes rather than skipped, so a quiet week looks quiet instead of being squeezed out of the list.
- Days are whole calendar days (UTC) recorded on our side, not on the shopper’s device clock, so a shopper with a badly set clock cannot land in yesterday’s row. If your store runs on a different timezone, a day here will not line up exactly with the same day in Shopify’s own reports.
- Every number the chart draws is in this table, so nothing on the page depends on colour or hover.
How the storefront pixel contributes
xDiscount installs a Shopify web pixel for you when the app is installed. You do not add it, configure it or maintain it, and there is no setting for it in the app.
It subscribes to exactly five storefront events and nothing else:
| Event | What is sent |
|---|---|
| Product viewed | The product ID and variant ID |
| Product added to cart | The product ID, variant ID and quantity |
| Cart viewed | The product IDs in the cart, with no quantities and no money |
| Checkout started | The product IDs in the checkout, with no money, since nothing has been charged yet |
| Checkout completed | The currency code, the order total, and the title and type of each discount applied |
Everything is folded into one daily total per store as it arrives. Nothing is kept as an individual shopper’s event trail.
It is fire-and-forget. A beacon that fails is dropped, never retried. A queue of pending telemetry inside a storefront is not worth what it would cost your shoppers in page speed. This is why the storefront counts are honestly labelled approximate.
Very busy stores
A very busy store can send more events in a minute than we accept from one store, and the excess is dropped rather than queued. This only ever nudges the pixel-sourced numbers downward. Discounted orders is untouched by it.
Privacy: what xDiscount never collects
The pixel declares itself as analytics only. In your store’s customer privacy settings that means:
| Purpose | Declared |
|---|---|
| Analytics | Yes |
| Marketing | No |
| Preferences | No |
| Sale of data | Disabled |
Shopify only runs the pixel for visitors who have consented to every purpose it declares. Declaring marketing would have quietly dropped the pixel for every shopper who allowed analytics but declined marketing, so it is declared false. The pixel does no advertising, no retargeting, no sharing and no selling.
The pixel never collects, and cannot collect:
- No shopper identity, so no name, email, phone number or customer record.
- No IP address, no device identifier, no browser fingerprint input.
- No per-visitor tracking ID, so one shopper’s views cannot be stitched into a session or followed across visits.
- No page URLs, no referrers, no search terms.
- No cookies or browser storage of its own.
What actually leaves the storefront is the short list in the table above: product and variant IDs, a quantity, an order total and currency, and discount titles. They are treated as opaque text on arrival, nothing is ever looked up from them, no pricing and no entitlement, and they are not kept. What is written down is the day’s running totals for your store, and nothing else.
If a customer asks what the app tracks
Product and cart activity in totals per day, and no information about who they are.
Where the revenue numbers are
The Discounted revenue tile, the option of the same name in the Chart metric dropdown and the column in the By day table are Shopify’s figure: the full total of each order one of your discounts reduced, recorded once per order from the same signed webhook that counts Discounted orders. Hover the tile, or reach it with the keyboard, and it says so in its own words, “From Shopify (exact). The full totals of the orders that used one of your discounts, shipping and taxes included, in your store currency.” It is gross, as placed: refunds and cancellations are not taken off, and it is never used for billing.
The By discount table’s Amount given and Order totals are a different kind of number. They are exact sums of what Shopify recorded on each order when it was placed, described in The By discount table above. They are not net sales: Shopify’s sales reports take off returns and count days in your store’s timezone. For net sales by discount, use the steps below.
The number of record is in Shopify. Shopify already reports discount revenue natively and does the money arithmetic on its own records, and a figure from us that differed by a cent would just read as a bug and cost you an afternoon reconciling it. So xDiscount tags the orders it discounts, and you slice your own Shopify reports by them.
How it works:
- When xDiscount reduces the price on an order, that order is stamped with the name of the discount that did it.
- The stamp lands on an order field called xDiscount campaign, which is set up in your store when the app is installed.
- In Shopify Analytics, group or filter a sales report by
order.metafields.xdiscount.campaign.
The field name is exactly order.metafields.xdiscount.campaign. The Analytics page no longer repeats it, so keep this page to hand when you build the report.
Points to be aware of:
- Only orders xDiscount actually discounted are stamped. Orders it did not touch stay blank rather than being lumped into a misleading bucket.
- Your own manual discounts are never stamped into this field, even if they were on the same order.
- Discount names longer than 120 characters are shortened in the stamp. A report dimension with thousands of near-identical values is unusable, so the value is kept short. The full name stays on the discount itself.
- The field is read-only in the admin. It is written by the app, and an edit would be overwritten.
- Shopify can decline to make the field groupable in reports on a given store. If that happens the field is still created, the stamp is still written and still visible on the order, it just cannot be used as a report dimension there.
The other states this page can show
| State | What you see | What it means |
|---|---|---|
| Loading | Four placeholder tiles and a blank chart-sized block | The first read of the page is in flight. Later range switches keep the old numbers on screen and dim them instead |
| No activity | No activity in this range, naming the dates, with an Open settings button | Nothing at all has been recorded in the selected range. No tiles, chart or table are drawn, because a wall of zeros would be indistinguishable from a broken pipeline |
| Read failed | A red banner headed Couldn’t load your analytics with a Try again button | We could not read your numbers |
| By discount failed | A red banner inside the By discount card, headed Couldn’t load the By discount table | Only that table could not be read. The tiles, chart and By day table still show |
The failure banner reads: “Your discounts are unaffected. This page only reads what has already been recorded.” That is the important part. This page only reads, so a failure here never stops a discount from applying at checkout.
The empty state explains itself, “Nothing was recorded between … and …. Numbers appear once shoppers see your discounts. The offer card has to be added to your theme for views and cart activity to be counted.”, and points you at Settings, where you add the offer card to your theme. The offer card is what shows shoppers a discount on the product page, before they reach checkout, and it is included on every plan, Free included. In Settings, the offer card’s Add to theme button is in the Storefront features section.
Reading the page well
- Compare like ranges. Switch between Last 7 days, Last 30 days and Last 90 days rather than reading one window in isolation, and use a custom range to line up with a specific promotion.
- Compare the storefront counts with Discounted orders. The counts move with your traffic. The ratio between them moves with your offer.
- Judge performance on Discounted orders. It is the exact number, and the one counted against your plan’s included orders.
- Compare your discounts in By discount. Its orders and amounts are exact sums of Shopify’s orders, and Export CSV takes them to a spreadsheet.
- Expect the storefront counts to miss some shoppers. Ad blockers and declined consent are normal, and they only ever undercount.
- Go to Shopify Analytics for money questions, grouped by
order.metafields.xdiscount.campaign. The Discounted revenue tile is gross and as placed, and your Shopify reports take off returns.