Direct to consumer
Post-purchase upsell
Accepting an upsell after checkout either writes a second order or edits the first, and tracking installed for a single purchase event gets one of those two cases wrong in every implementation that has not decided which.
Paid, fixed scope · Within ten business days after complete access
What breaks
One-click upsell apps, post-purchase offer pages, subscription upgrades taken at checkout, and any flow that changes an order after it is first created
There are only two ways to record an upsell taken after the order is placed, and each breaks a different thing. If it creates a second order, a purchase event fires again for a customer who converted once, so the platform counts two conversions, the customer looks like a repeat buyer within seconds, and new-customer acquisition cost is understated. If it amends the original order, no second event fires at all, so the added revenue never reaches the ad platform and the campaign is judged on a value lower than what the customer actually paid. Both outcomes are silent. The store record is correct in both cases, which is precisely why the discrepancy sits unexamined between two systems that each look right.
Why nobody catches it
Upsell apps are installed by growth teams to raise average order value, and they succeed at that on the store report, so the feature is judged a win from the first week. The measurement consequence lands somewhere else entirely, inside the ad platform, weeks later, as a slow drift between platform-reported revenue and actual revenue. By then the drift has no obvious cause and gets absorbed into the general assumption that platform numbers always run high or low. Nobody connects it back to an app that was installed and validated months earlier.
The work
The order-record evidence of which path the app takes, the conversion definition in writing, and a reconciliation across the store and the ad platform.
- 01Establish which of the two paths the app actually takes, by putting a real upsell through and reading the resulting order records
- 02Decide deliberately what a conversion means when an order is amended, and write the definition down before changing any tag
- 03Send the purchase once per customer transaction with the final value, from the order record rather than from whichever page fired last
- 04Reconcile a day of upsell orders against both the store record and the ad platform, and keep the comparison
Elsewhere in ecommerce and subscription
One stack usually has more than one of these.
These boundaries compound. A brand running a hosted checkout and a subscription plan has two separate reasons for its channel report to be wrong, and fixing one leaves the other in place. The audit establishes which are live on your stack before anything gets rebuilt.
Start with the smallest useful check
Send one account running upsells and order edits and we will read its setup before anyone signs anything.
Send the domain, the customer journey, and the platforms that should receive it. The tracking audit shows what is working, what is missing or duplicated, and the exact build recommended next.
Paid, fixed scope · Within ten business days after complete access