Sign InSign Up
Install on Shopify
Aimerce Blogs
Post-Purchase Upsell Revenue Meta Never Sees
20 November 2026
Post-Purchase Upsell Revenue Meta Never Sees
First-Party Data 101

Quick Answer: When a shopper accepts a post-purchase upsell on Shopify, the extra item is added to the same order after checkout. But the purchase event that ad platforms receive has already been sent with the original order value. Shopify's own checkout_completed event fires on the first upsell offer page, before the shopper accepts anything, and server-side tools typically send the purchase when the order is created. So unless your tracking waits for the upsell step to finish, Meta keeps the pre-upsell value, and the upsell revenue never reaches it. You can measure the gap by comparing each upsell order's current total in Shopify with the value sent to Meta, or by using your upsell app's own revenue report. Then decide whether Meta should see that revenue at all, because not every brand wants it to.

Key Takeaways

  • Post-purchase upsells are added to the original Shopify order after the purchase event has already gone out. Meta never sees the extra revenue.
  • This isn't one app's bug. Shopify fires checkout_completed on the first upsell page, and most server-side setups send the purchase at order creation.
  • The gap is biggest on your best customers, the ones who say yes to the upsell, so value-based bidding undervalues exactly the buyers you want more of.
  • You can measure the gap: compare each upsell order's current total with the value sent to Meta, or use your upsell app's own revenue report.
  • Waiting to send the purchase until the upsell step ends closes the gap, at the cost of a slower signal. And some brands deliberately keep upsell value out of Meta.
  • BFCM is when brands push upsells hardest, so it's when the gap matters most.

Post-purchase upsells are one of the best AOV levers on Shopify. A shopper finishes checkout, sees a one-click offer before the Thank You page, and adds something without re-entering payment details. Apps like AfterSell, ReConvert, and Zipify OCU have made this standard, and Shopify supports it natively.

There's a measurement catch that doesn't get nearly enough attention. The revenue from that upsell usually never reaches Meta. By default, that includes Aimerce: our purchase event fires when the order is created, right after checkout. For stores that want the full value, we can hold the purchase for a set time after the order is created, up to 30 minutes, and then send one purchase with the order as it stands. That covers any upsell app that adds items to the original order, which is how AfterSell, ReConvert, and Shopify's native post-purchase offers work. It's a per-store setting we turn on, not the default, because it trades signal speed for completeness. Either way, it's worth understanding exactly how the gap works, and whether you even want Meta to see that revenue.

Why doesn't upsell revenue reach Meta?

It comes down to timing. Here's the sequence on a Shopify store with a post-purchase upsell:

  1. The shopper completes checkout. Shopify creates the order right away and places it on hold so the upsell step can run.
  2. The purchase is reported. On the browser side, Shopify's own documentation says the checkout_completed event fires on the first upsell offer page instead of the Thank You page, and doesn't fire again afterward. On the server side, tools that report purchases from Shopify order data typically send them when the order is created.
  3. The shopper sees the upsell offer. If they accept, Shopify edits the original order and charges the payment method. The upsell becomes a new line item on the same order.
  4. The order is released and the shopper lands on the Thank You page.

By step 3, the purchase event has already gone out with the original value. The order in Shopify now has a higher total, but nothing tells Meta the value changed. Meta keeps the number it received.

Why does this matter more than it sounds?

On its own, a missing upsell looks like a rounding error. But it isn't spread evenly.

It hits your best customers. The shoppers who accept an upsell are, by definition, the ones willing to spend more. Their purchases reach Meta at a lower value than they're actually worth.

It skews value-based bidding. If you optimize for purchase value, Meta learns from the values you send it. Undervaluing your upsell takers teaches the algorithm that they're worth less than they are.

It makes good campaigns look worse. A campaign that brings in shoppers who love your offers will show lower ROAS in Ads Manager than it deserves, and it might get cut.

It peaks during BFCM. That's when brands run their most aggressive upsell offers, so the gap grows exactly when budget decisions move fastest.

How do you measure the upsell gap on your store?

You can calculate it precisely, because both numbers exist.

  1. Pick a time window, such as the last 30 days.
  2. Pull orders that had an upsell accepted. Most upsell apps report which orders included an accepted offer, or you can look for orders edited after checkout.
  3. For each order, compare two numbers: the order's current total in Shopify and the purchase value Meta received for it. Make sure you're comparing the same thing. Most setups, including Aimerce by default, send the order total with shipping and tax, after discounts. If your store sends a subtotal or excludes tax, compare against that instead. If your upsell app reports upsell revenue directly, that's an even simpler number to use.
  4. Add up the differences. That total is the upsell revenue Meta never saw.
  5. Divide it by Meta-attributed revenue for the same window. That tells you roughly how much Meta's reported ROAS understates your real return.
  6. Repeat by campaign if you can. Campaigns that bring in high-intent shoppers often have higher upsell take rates, so the gap won't be the same everywhere.

Shopify admin doesn't show what value was sent to Meta for each order. If you use Aimerce, our support team can look up the values sent for a sample of your upsell orders, so you can run this comparison.

What can you do about it?

There's no single right answer, so it helps to be clear about the trade-offs.

ApproachWhat it doesTrade-off
Measure and adjustCalculate the upsell gap monthly and factor it into ROAS when making budget decisionsFixes your decisions, not Meta's bidding
Judge upsell-heavy campaigns on Shopify revenueCompare campaigns using final order totals rather than Meta-reported valueNeeds reporting outside Ads Manager
Send a separate upsell purchaseA script on Shopify's post-purchase page sends an extra purchase event containing only the accepted upsell itemsMeta counts two purchases for one order, so conversion counts and cost per purchase shift
Wait to send the purchase until the upsell step endsCaptures the final order total in one event. Aimerce offers this per store, with a wait of up to 30 minutesSlower signal, and anything added after the wait ends is missed

The third option is the most common workaround, and Zipify documents it for its own app. With Shopify's native Meta Pixel integration, the purchase for the initial order fires automatically when the first upsell page loads, so you add a script to the post-purchase page that sends a purchase for the upsell only. It works, but Meta now sees two purchases for one customer. Conversion counts and cost per purchase both change, so don't compare those numbers across the switch. And if the extra event accidentally includes the original items, you're double counting revenue too. Our guide to deduplication errors in Meta Events Manager explains how to spot it.

The fourth option is what Aimerce does for stores that turn it on. We wait a set time after the order is created, configurable up to 30 minutes, then send one purchase with the order as it stands. If the shopper skips the upsell, the purchase still goes out at the end of the wait with the original value, so nothing is held open indefinitely. An upsell accepted after the wait ends isn't added. We don't make it the default, because a purchase that arrives quickly and reliably with a slightly low value is usually better for Meta's learning than one that arrives later. It's a real trade-off, which is why it's a per-store choice.

Should Meta see your upsell revenue at all?

Here's the part that surprised me. Not every brand wants this gap closed. We've had customers ask for the opposite: send Meta the price of a single unit instead of the post-upsell order value, or leave upsell items out of the purchase value entirely. They weren't the first to ask, and it's a reasonable choice.

The logic goes like this. Your ads sell the front-end offer. The upsell is sold by your post-purchase page, to a buyer your ads already won. If you want Meta to optimize toward people who buy the entry offer, and keep reported ROAS tied to what the ads actually did, a stable front-end value can be the cleaner signal. It also keeps value-based bidding from chasing upsell behavior that changes every time you swap the offer.

The opposite case is just as valid. If upsell takers really are your most valuable customers and you optimize for value, you want Meta to see the full total so it finds more people like them.

The point is to choose on purpose. Most brands never decide. They inherit whatever their tracking does by default. Aimerce can be set up either way for a store.

Which upsell setups does this affect?

Any post-purchase upsell that adds items to the original order after checkout, which covers most of the popular options:

  • Shopify's native post-purchase extensions
  • AfterSell
  • ReConvert
  • Zipify One Click Upsell (OCU)

Pre-purchase upsells and cart cross-sells aren't affected, because those items are in the order before checkout completes and the purchase is sent with the full value.

Upsell apps that create a separate second order work differently. That second order is reported as its own purchase, so the revenue does reach Meta, but as a second conversion rather than part of the first.

Pre-purchase vs. post-purchase upsells

Pre-purchase (cart or checkout cross-sell)Post-purchase (after payment, before Thank You page)
When the item is addedBefore checkout completesAfter the order is created
Included in the purchase value sent to MetaYesUsually not
Shows up in Shopify order totalYesYes
Effect on Meta-reported ROASNoneUnderstates real revenue by the upsell amount

FAQ

Does Meta see revenue from post-purchase upsells? Usually not. The upsell is added to the original Shopify order after the purchase event has already been sent with the original value, and Meta keeps the value it received.

Why does Shopify's checkout_completed event miss the upsell? Shopify's documentation says that for upsells and post-purchase offers, checkout_completed fires on the first upsell offer page instead of the Thank You page, and isn't triggered again. That's before the shopper has accepted the upsell.

Does server-side tracking fix the upsell gap? Not by itself. Server-side tools that send purchases when the order is created have the same timing problem, because the upsell is added afterward. The fix is to wait until the upsell step ends before sending. Aimerce sends at order creation by default and, for stores that want the full value, can hold the purchase for up to 30 minutes so Meta gets one purchase with the final total.

How do I calculate how much upsell revenue Meta is missing? For orders with an accepted upsell, subtract the purchase value Meta received from the order's current total in Shopify, then add up the differences for the period. Compare the same kind of value on both sides, total or subtotal. Or use the upsell revenue your upsell app reports.

Are pre-purchase upsells affected too? No. Items added in the cart or during checkout are part of the order when the purchase is sent, so their value is included.

Should my upsell app send its own purchase event to Meta? Only if it's a separate event or properly deduplicated against the original purchase. Otherwise Meta may count two purchases for one order.

Should Meta see my upsell revenue? It depends on what you want Meta to optimize for. Sending the full total helps value-based bidding find high-value buyers. Sending only the front-end value keeps ROAS tied to what the ads sold and gives Meta a steadier signal. Choose deliberately rather than inheriting a default.

Sources

[1] Shopify Developers, "checkout_completed,"

[2] Nosto Docs, "Post-Purchase Upsell,"

[3] Aimerce, "How to Fix Event ID Deduplication Errors in Meta Events Manager,"

[4] Aimerce, "How to Fix the Shopify vs. Meta Revenue Discrepancy,"

[5] Zipify Help Center, "Pixel tracking on the Post-purchase page [OCU],"

Try Aimerce Pixel Risk-Free
for 30 Days

Most teams see results within 2 weeks.

Money-back guarantee.
It pays for itself, or you don't pay anything.

Install On
Sign Up for a
30-Day Aimerce Pixel Free Trial
Sign Up Using Your Shopify Account Email
*Money back guaranteed.
Aimerce pays for itself or you don’t pay anything.