"Attributed revenue" is revenue we can trace to a real shopper click. We count on the strict side — when in doubt, an order does not count.
The rule
An order counts as PersonalizerAI revenue only when a shopper clicks a widget, a search result or a PersonalizerAI collection-page result first. A product added to the cart from that click counts whenever the order is placed. A click with no product added that way counts only if the shopper buys in the same visit. A view without a click never counts.
"Only when" means all of this must be true:
- The shopper clicked — a view alone is never enough.
- The product was added from the widget, or on its product page within 30 minutes of the click. Or, if no product was added that way, the purchase happened in the same visit. A visit ends after about 30 minutes without activity.
- The order went through your online store's checkout.
The three attribution levels
Not every click is an equally strong signal. The app records three levels of proof, with different credit:
Level | What happened | Credit |
|---|---|---|
Cart click | The shopper clicked the add-to-cart button inside the widget itself. | 100% — for the clicked products only, after discounts. |
Product-page click | The shopper clicked a product in a widget, opened its page, and added it there within 30 minutes. | 100% — for that product only. |
Same-visit click | The shopper clicked a widget, a search result or a collection-page result during the visit, but no bought product carries a click of its own. | 50% of the whole order — the weaker signal gets half credit. |
You can see this on the Session Replay tab. The Weight column of the Attributed Orders table shows 100% or 50%. The Sources column shows which models earned the credit; a same-visit order shows Same visit.

The Weight and Sources columns show each order's proof level.
What else counts
- Search clicks. A click on a search result counts the same way. This revenue appears as Search Revenue on the dashboard.
- Collection-page clicks. A click on a product in a PersonalizerAI collection page (the Collection filters block) counts the same way. This revenue is in Revenue Attributed, but not in Search Revenue or Rec Revenue.
- Email recommendations. When a shopper opens a product from a recommendation in one of your emails and adds it to the cart within 30 minutes, that product counts the same way.
- After-purchase offers. When a shopper accepts an offer after checkout, that amount counts in full, credited to the model that made the offer.
What never counts
- Views without clicks. A shopper who saw a widget but did not click it is not our sale.
- Orders from a later visit with no product added from a widget, search result or collection-page result. A product added that way still counts when the shopper comes back later to buy it; a click alone does not.
- Orders outside your online store: point-of-sale orders, draft orders, and orders synced from marketplaces such as Amazon, Etsy, or eBay.
Each order counts once
Shopify can send the same order to the app more than once. The app keeps exactly one record per Shopify order. A resent order changes nothing — no double counting.
How models share the credit
Each product added from a widget credits the model that showed it, at that product's value. An order with products from two models credits each model with its own products. A same-visit order (50%) names no model, so it counts in Revenue Attributed but not in the model tables on the dashboard and the Recommendations tab.
Two details keep the tables honest:
- Your Hand-Picked lists keep their own credit — the tables report them as Hand-Picked.
- When a hand-picked list is short, the app fills the empty slots from another model. A sale from a filled slot credits the model that supplied the product.
Credited revenue and what bundles add
Everything above is credited revenue: an order counts because a shopper clicked first. Credit tells you which orders PersonalizerAI touched. It does not tell you how many of those orders would have happened anyway.
For bundles, the app also measures the incremental number: what bundles add. While Measure what bundles add is on, 1 in 5 visitors on pages with pairs don't see bundles. The app compares revenue per visitor between the two groups, after bundle discounts. The difference is what bundles add, shown with a likely range once there is enough data.
Credited | What bundles add | |
|---|---|---|
Question it answers | Which orders had a bundle in them? | How much more revenue do visitors bring because they saw bundles? |
Counts sales that would have happened anyway | Yes | No |
Ready | From the first order | After at least 14 days, often longer |
Both are on the What bundles add card, and the credited rows are labelled credited, not all extra. See Bundles & bundle discounts: What bundles add.
Why our numbers differ from Shopify's reports
The differences, in one list:
- We count only orders with a real click. Shopify counts every order.
- Same-visit orders count at 50%, so their rows show half the order value.
- Cart-click and product-page-click orders count the clicked products only, not the whole cart.
- We record the amount at the time of the order. Refunds are not subtracted afterward.
- We exclude point-of-sale, draft, and marketplace orders.
- Our numbers refresh once per night. Shopify's reports are closer to live.
Currency
All attributed revenue is in your store's own currency. When a shopper pays in another currency, we record the amount Shopify reports in your store currency, so every row in Attributed Orders shows your store currency.
A/B test revenue works differently. It counts the value only of orders paid in your store currency. An order paid in another currency still counts as an order, so conversion rates include it, but its value is left out of the test's revenue for both versions alike.
Privacy
Attribution needs no personal data. The signal is an anonymous browser session — no name, no e-mail address, no profile. See Privacy & shopper consent.
When a shopper declines analytics cookies, the two full-credit levels still work — they ride on the cart itself, not on analytics. The half-credit same-visit level does not. So for these shoppers the dashboard undercounts; it never overcounts.
Related pages
- Dashboard & KPIs — where attributed revenue appears first.
- Analytics tabs — the Weight and Sources columns in action.
- Privacy & shopper consent — how consent changes what the app records.
- Hand-picked & custom models — how your own lists earn credit.
- Bundles & bundle discounts — what bundles add, measured against visitors who don't see them.