How Do I Measure Revenue From Wishlist and Reminder Emails?
Track Revenue by Email Type, Clicks, and Orders
The cleanest way to measure revenue from wishlist and reminder emails is to treat each reminder type as its own channel inside your email reporting.
That means one bucket for wishlist reminder emails, one for back-in-stock reminders, and one for price-drop reminders. Each email should use tagged links that identify the flow, campaign type, and product. Then you match clicks to orders inside the same attribution window every time.
A small fashion store can do this without a big analytics setup. If a black midi dress sells out in size M, the store can send a back-in-stock email only to shoppers who saved that product, tag those links clearly, and measure the orders that came from that reminder alone.
If you want the cleanest measurement, start by separating wishlist saves, back-in-stock reminders, and price-drop reminders into distinct reporting buckets.
What Counts as Revenue From Wishlist and Reminder Emails?
Revenue from wishlist and reminder emails is the order value you can reasonably connect to a wishlist reminder, a back-in-stock email, or a price-drop email.
That sounds obvious, but this is where reporting gets messy fast. A lot of stores mix all automated emails together, then wonder why the numbers feel vague. If you want a real answer, you need clear boundaries.
Here is what usually counts:
- Revenue from clicks on a wishlist reminder email
- Revenue from clicks on a back-in-stock reminder email
- Revenue from clicks on a price-drop reminder email
- Orders placed inside your chosen attribution window after the click
- Assisted revenue, if you report it separately
Here is what should not be mixed into that total:
- Revenue from standard promotional campaigns
- Revenue from abandoned cart emails
- Revenue from browse abandonment emails
- Revenue from paid ads unless you are doing a broader multi-touch model
- Organic return visits with no clear email interaction, unless you are tracking view-through separately
A jewellery merchant is a good example here. If the merchant sends a price-drop reminder for a saved gold necklace and also sends a weekend sale blast featuring the same necklace, those should not sit in one bucket. If they do, you cannot tell whether the reminder email worked or the broad promotion did.
The fix is simple. Separate the campaign types first. Then measure them.
Why Measuring Wishlist Email Revenue Matters for Small Ecommerce Stores
Measuring wishlist email revenue matters because saver audiences are usually your highest-intent shoppers, and high intent deserves its own reporting.
A shopper who saves a product is telling you something useful. A shopper who clicks a reminder and comes back later is telling you even more. If that behavior gets buried inside general email revenue, you lose the signal.
Small stores feel this most. You do not have time to guess which products deserve a restock, which discounts actually bring people back, or which categories attract serious buyers. Clear measurement helps you answer those questions with less noise.
A home goods store can use this in a very practical way. If saved ceramic lamps keep generating reminder-driven orders, that store has a stronger case for restocking those lamps before restocking slower items with fewer saves and weaker reminder revenue.
A print-on-demand shop can use the same logic. If three saved designs get repeated clicks and purchases after reminder emails, those designs have earned another push. Saves are not just a nice engagement metric. Saves are demand ranking.
A wishlist program works best when saves, demand signals, and reminder emails are measured together rather than as isolated campaigns.
If you want one place to connect saves, reminders, and the orders that follow, this is exactly the kind of reporting flow Keepsy is built to support.
How to Measure Revenue From Wishlist and Reminder Emails Step by Step
Measuring revenue from reminder emails is easier when you use one repeatable framework and do not change the rules every month.
The framework below is simple enough for a small team, but strong enough to answer the real question: are these emails bringing in orders you care about?
A beauty brand can make this even sharper by checking cross-device behavior. If a shopper saves a serum on mobile, opens a reminder email later on desktop, and then buys, the measurement setup should still count that order if the shopper is identified correctly. If cross-device tracking breaks, reminder revenue will look weaker than it really is.
The attribution window matters more than people expect. Back-in-stock emails often convert quickly because the shopper was already waiting. Price-drop reminders can also convert fast, but some buyers take a day or two to come back. Wishlist reminders often sit in the middle.
Here is a good starting point:
| Email type | Good starting window | Why it works |
|---|---|---|
| Wishlist reminder | 7 days after click | Gives shoppers time to return without stretching credit too far |
| Back-in-stock reminder | 3 to 7 days after click | Urgency is usually highest right after inventory returns |
| Price-drop reminder | 3 to 7 days after click | The price change creates immediate buying intent |
Weak reporting looks like this:
Weak: "Automated email brought in $4,200."
Stronger reporting looks like this:
Stronger: "Back-in-stock emails for saved apparel products generated 18 orders and $4,200 inside a 5-day click window. Price-drop reminders for the same category generated 9 orders and $1,700 in the same window."
That second version gives you something you can actually use.
Best Ways to Measure It: Simple Attribution Models Compared
The best attribution model for small ecommerce stores is usually click-based attribution first, with assisted reporting as a second view.
You do not need a perfect model to get a useful answer. You need a model that is consistent, understandable, and hard to misread.
| Attribution model | What it credits | Best use | Main risk |
|---|---|---|---|
| Click-based attribution | Orders after a shopper clicks the reminder email | Best default for small stores | Misses shoppers who saw the email but returned another way |
| Last-click attribution | The final clicked channel before purchase | Good if your reporting stack already uses last-click everywhere | Reminder emails can lose credit to another late touch |
| Assisted or view-through reporting | Orders from shoppers who opened or saw the email and later purchased | Helpful as a influence view | Easy to over-credit email |
| Holdout-style comparison | Compare shoppers who got the reminder vs shoppers who did not | Best way to estimate incremental lift | Harder to run cleanly for small teams |
Click-based attribution is usually the safest starting point because it is concrete. A shopper clicked. A shopper bought. The link between the two is clear.
Last-click attribution can still work, but it often underplays reminder emails. A shopper clicks a back-in-stock reminder, comes back later through direct traffic, and the sale gets credited elsewhere. The reminder helped. The report misses it.
Assisted reporting is useful, but only if you keep it separate from direct attributed revenue. If you blend click-attributed and view-attributed revenue into one total, you can end up counting the same sale twice.
Holdout comparisons are the closest thing to an incrementality check. A jewellery merchant can send a price-drop reminder to one saver group and hold back another similar group for a short test. If the reminder group buys more often, that gap is the clearest sign the reminder created extra sales rather than just claiming sales that would have happened anyway.
Common Mistakes When Tracking Wishlist Email Revenue
Most tracking mistakes come from mixing signals that should stay separate.
The first mistake is combining all automated emails into one report. Wishlist reminders, back-in-stock emails, and price-drop reminders do different jobs. If they share one revenue line, you lose the story.
The second mistake is double-counting revenue. This happens when one order appears in click-attributed revenue and again in assisted revenue, then both totals get added together. Keep direct and assisted reporting in different columns.
The third mistake is changing the attribution window every time results look weak. A 3-day window one month and a 14-day window the next month turns reporting into guesswork. Pick a window and stick to it long enough to compare periods honestly.
The fourth mistake is ignoring inventory timing. A back-in-stock email sent 12 hours after inventory returns is not the same as one sent 5 days later. A small fashion store that waits too long after a popular size comes back will often see weaker conversion, even if demand was real.
The fifth mistake is focusing on opens instead of orders, clicks, and saves. Opens can tell you whether the subject line got attention. Opens do not tell you whether the email made money.
A better dashboard tracks:
- Emails sent
- Delivered emails
- Clicks
- Click rate
- Orders
- Attributed revenue
- Revenue per email sent
- Saves-to-purchase rate
- Product-level saves
- Demand ranking by product or category
If your reporting stops at opens, you are seeing activity, not outcomes.
What We Recommend for Keepsy-Style Wishlist Programs
Keepsy-style wishlist programs work best when reporting mirrors shopper intent instead of flattening everything into one email total.
We recommend three separate revenue views: wishlist reminder revenue, back-in-stock reminder revenue, and price-drop reminder revenue. We also recommend pairing each revenue view with saves, product demand ranking, and category-level patterns so the reporting helps both retention and merchandising.
That matters because reminder revenue is only half the story. A home goods store deciding on a restock order needs to know which saved products actually pull buyers back. A print-on-demand shop deciding which design to feature again needs to know which saves turn into clicks and purchases after a reminder.
Review results by product category and restock cycle. Apparel behaves differently from beauty. Jewelry behaves differently from home goods. A popular ring with a price-drop reminder can have a very different buying curve than a sold-out dress size or a restocked candle set.
If you want clearer reporting, do not stop at campaign totals. Look at revenue by product, by category, and by reminder type. That is where the useful decisions live.
Best answer: Use separate reporting for wishlist, back-in-stock, and price-drop emails, attribute orders inside one fixed click window, and review the results alongside saves and product demand. That setup gives small ecommerce stores a clean way to prove email value and make better restock and promotion calls.
If your store already has shoppers saving products, the next step is not more reporting clutter. The next step is cleaner intent signals tied to real orders.
FAQs
What metrics should I track for wishlist reminder emails?
Track clicks, orders, attributed revenue, revenue per email sent, and saves-to-purchase rate. Product-level saves and demand ranking also matter because wishlist email performance makes more sense when you can see which saved items attract real buying intent.
How do I measure revenue from back-in-stock emails?
Measure revenue from back-in-stock emails by tagging the links in each back-in-stock send and attributing orders that happen inside a fixed click window. Keep back-in-stock reporting separate from other automated emails so sold-out and restocked product behavior stays clear.
How do I measure revenue from price-drop emails?
Measure revenue from price-drop emails the same way: tagged links, fixed attribution window, and separate reporting by email type. A separate view matters because price-drop reminders often compete with standard sale campaigns for credit.
What attribution window should I use for reminder emails?
Most small stores should start with a 3 to 7 day click window for back-in-stock and price-drop reminders, and about 7 days for wishlist reminders. The exact number matters less than consistency, because consistent windows make comparisons trustworthy.
How can I tell if wishlist email revenue is incremental?
The cleanest way to judge incremental revenue is to compare a group that received the reminder against a similar group that did not. If a holdout test is too much work, compare reminder-driven performance against similar periods and similar products, but keep the limits of that method in mind.
Should I track saves-to-purchase rate as well as email revenue?
Yes. Email revenue tells you what happened after the send, while saves-to-purchase rate tells you how strong the underlying demand was. Both numbers together give a much better read on which products deserve a restock, a reminder, or another push.
Summary: A Simple Revenue Measurement Framework You Can Reuse
Revenue from wishlist and reminder emails is measurable if you keep the setup simple and disciplined.
Split wishlist reminders, back-in-stock emails, and price-drop reminders into separate reporting buckets. Tag links the same way every time. Use one attribution window. Track orders and attributed revenue first, then layer in assisted reporting and holdout comparisons if you want a fuller picture.
The stores that get the most from wishlist programs do one thing well. They connect saves, reminders, and purchases instead of treating them as separate events.
Want clearer demand signals and easier reminder-email reporting? See how Keepsy helps OpoShop stores turn saves into measurable revenue.
