Discount Dependency by SKU
Discount Dependency by SKU compares, for each SKU, the price visitors saw with the price they paid. It shows which SKUs only sell at a discount, and which sell fine at full price.
How It’s Calculated
The report takes each item on an order that das Pixel linked to a visit. It compares the price the visitor was shown for that variant in the same visit with what the order charged for the item. The comparison is made per variant, and the results are added up per SKU.
Each row is one SKU. A variant with no SKU gets its own row. The table lists up to 200 rows, with the largest Discount Given first.
The columns are:
- SKU and Product: the SKU and the product and option it belongs to.
- Units Sold: the items sold on those linked orders.
- Price Coverage: the share of units sold for which das Pixel had a price shown to the same visitor.
- Listed Price: the average price shown, per item that was compared.
- Paid Price: the average price paid, per item that was compared. It is the item’s price times its quantity, minus the discount on that item. It leaves out shipping, tax and refunds.
- Discount Depth: Discount Given divided by the total price shown.
- Full-Price Share: the share of compared items that were paid at 99% or more of the price shown.
- Discount Given: the total price shown minus the total price paid, for the compared items.
The price shown is the last price the visitor saw for that variant in the visit, from a product view or an add to the cart. A price shown in a currency other than your store’s is left out, so an exchange rate doesn’t read as a markdown.
Price Coverage below 50% leaves Discount Depth and Full-Price Share blank for that row. A figure built on under half the units isn’t reliable. Discount Given is still shown, but it covers fewer units than the SKU sold.
Items sold outside the orders das Pixel linked don’t count, and items on canceled or voided orders are left out.
Summary Cards and Chart
The cards above the table are SKUs, Units Sold, Discount Depth and Discount Given. SKUs is the number of rows. The others add up the rows.
With Compare on, each card shows its change.
The totals for Discount Depth are blank when the coverage across all rows is below 50%.
The chart shows the 10 SKUs with the most Discount Given.
What Counts
- Visitors who declined analytics cookies, or who opted out of the sale or sharing of their data while Require Sale-of-Data Consent is on, aren’t recorded. Known bots are left out.
- Only visits inside the date range count, in your store’s time zone.
- Turn on Live to refresh the report every 30 seconds. Without it, a figure can be up to 10 minutes old.
A warning shows above the report when das Pixel saw less than 70% of your online-store orders in the last 30 days. This report has no Segment, Sales Channel or Filters control.
What Good Looks Like
There’s no target. A SKU with a high Units Sold, a low Full-Price Share and a large Discount Given looks like a bestseller, but it sells because of its discounts.
A SKU with a high Full-Price Share that still has a large Discount Given is being discounted when it doesn’t need to be.
What to Do About It
- A low Full-Price Share: review the SKU’s price, or the discounts that apply to it.
- A high Full-Price Share with a large Discount Given: check for a store-wide or collection-wide promotion that includes it, and exclude it.
- A low Price Coverage: treat the rates as unknown. Discount Given covers only the compared units.
Promotion Efficiency by Product shows discount use by product from your orders alone.
Get AI Insight at the top of the report asks Copilot for a short read of it.
Where to Find It
- Discount Dependency by SKU: open Reports and look under Web Analytics.