Analytics
Analytics combines retained wishlist saves, alert delivery records and orders credited by the app. Read each card's scope before comparing periods or interpreting the recovered-revenue figure.
Set a date range
- 1
Open Analytics
Use the date selector at the top of the page. The starting range is Last 30 days.
- 2
Choose the period
Select Today, Yesterday, Last 7 days, Last 30 days or Last 90 days. Numeric ranges are rolling periods ending now. Today and Yesterday use calendar boundaries on the app server, which can differ from your local midnight.
- 3
Compare matching scopes
The Dashboard uses 30-day summaries for recent saves and sends. Choose Last 30 days when comparing those cards, and remember that Active wishlisters is a current count even when you change the range.
Read the cards
| Metric | What is counted | Practical limit |
|---|---|---|
| Items saved | Existing saved items whose saved date falls in the period. | Removed saves are not preserved as immutable historical events. |
| Active wishlisters | Shoppers who currently have at least one saved item. | Changing the date range does not turn this into a historical audience count. |
| Alerts sent | Successful alert delivery records created in the period. | An hourly multi-item digest can create several item-delivery records for one email. |
| Alert → purchase rate | Delivery records in the period marked with a purchase, divided by successful delivery records in that period. | It is a delivery-record measure, not a unique-customer conversion rate. |
| Recovered revenue | Attributed order amount for orders dated in the selected period. | Uses order-level value and does not deduct later refunds. |
Read By alert type
The table shows Back in stock, Price drop and Low stock, with Sent, Purchases and Recovered revenue. The overall alert total can also include Wishlist reminder deliveries, which do not have their own row in this table. Orders attributed directly to a saved item can contribute to total revenue without contributing to an alert-type row.
How to interpret a difference
| Question | Explanation |
|---|---|
| Why do active wishlisters stay the same across ranges? | That is the current saved-list audience. |
| Why are sends higher than the emails I received? | A digest can have one item-delivery record per included variant. |
| Why does revenue exceed the saved item's price? | The credited amount is the order subtotal used by the app, rather than only that item's value. |
| Why does the table not add up to the top total? | Direct wishlist attribution and reminder activity have different coverage from the three visible rows. |
Attribution is broader than a verified click
The screen's short description mentions an alert click. The current implementation matches purchased variants to saved items or recent alert delivery records; it does not require a recorded click. Use How attribution is counted when interpreting the numbers.
A useful review routine
- Set one period and record saves, send records and credited orders together.
- Use Wishlist Items to inspect current product demand.
- Use Alert log for the individual event behind a delivery question.
- Keep revenue figures from different apps separate because one order can qualify in more than one report.
Need help?
Open the chat bubble in the Shopify app, or contact us with your store address and what you are stuck on.