How attribution is counted
The app credits an order after matching an identified shopper and a purchased variant to wishlist or alert activity. These rules explain the dashboard value; they do not establish that a particular email caused the purchase.
How an order is matched
- 1
Identify the shopper
The order needs a customer ID or email that matches a shopper record in this store. An anonymous browser-only wishlist with no identifiable order connection cannot be matched by its guest browser token alone.
- 2
Match a purchased variant
The app looks for a purchased variant among that shopper's existing saved variants or alert delivery records from the preceding seven days. A product-level save without a variant is not matched by this variant-based check.
- 3
Choose the source
If a recent matching alert delivery exists, the order is credited to the alert source and uses the newest matching delivery's type. Otherwise a matching saved variant credits the wishlist source. The recent-delivery check does not require a clicked status.
- 4
Record the order once
The app stores one attribution for a store/order pair. Several qualifying items do not create several copies of the same order value within Wishlist's recovered-revenue total.
What amount is recorded
The current order subtotal is used when supplied by Shopify, with fallbacks to the order subtotal or total. This is an order-level amount, not a sum restricted to the saved line items. The app does not later subtract refunds in this report.
| Example | What the report can do |
|---|---|
| A shopper saved a variant worth 40 and buys it in an order with subtotal 100. | Credit the order amount of 100, rather than only 40. |
| Two saved variants are bought in the same order. | Store one attributed order, not two copies of its subtotal. |
| A matching alert was recorded three days ago, but no click was recorded. | The recent-delivery rule can still attribute the order to that alert. |
| Only an anonymous product-level card save exists. | It may not satisfy shopper and exact-variant matching. |
The seven-day rule is not click verification
The current code checks the age of matching alert delivery records, not the time of an observed click. It also does not filter that matching query to successful sends only. Treat the output as the app's attribution model, not evidence that the shopper opened or clicked an email.
Why rate and purchase count differ
Alert → purchase rate counts delivery records marked as purchased. By alert type counts attributed orders. One order can mark several recent matching delivery records as purchased while still contributing only one order to the purchases table. Those two figures measure different units.
Other boundaries to keep in mind
- Direct wishlist orders contribute to recovered revenue but are not assigned to an alert-type row.
- The stored currency belongs to the order. The current report sums recorded amounts and displays the store currency; it does not provide a currency-conversion report.
- Another app can independently attribute the same order. Adding app dashboards together can double count it.
- An identified purchase also marks matching waiting/notified restock subscriptions as purchased, so those requests stop waiting.
Investigate an unexpected order
- Compare the order's customer/email with the shopper record.
- Compare the purchased variant ID/option values, not only the product title.
- Look for matching saved variants or recent alert activity.
- Compare the order subtotal and date with the selected Analytics period.
- For mixed currencies or a disputed attribution, send support the store and order reference so it can be checked.
Need help?
Open the chat bubble in the Shopify app, or contact us with your store address and what you are stuck on.