> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# upsell_purchase Event

> Track upsell conversions — automatically generated by Upstack

> [!NOTE]
>
> **Automatically generated** — Upstack creates this event from Shopify order updates. You don't fire it.

For the rules Upstack uses to detect an upsell and why it isn't sent as a second `purchase`, see [How post-purchase upsells are tracked](https://docs.upstackdata.com/concepts/how-post-purchase-upsells-are-tracked.md).

Fires when a post-purchase offer adds to an order already sent as `purchase`.

## How It Works

1. **Purchase sent.** At checkout, Upstack sends `purchase` with the order total at that moment.
2. **Order update received.** The accepted offer is added to the same Shopify order, and Shopify sends Upstack an order update.
3. **Upsell check.** Upstack treats the update as an upsell only when the order has the tag `AfterSell Upsell`, was created in the last 2 hours, has a payment status of paid or pending, and has a new total higher than the `purchase` value already sent.
4. **Event generation.** Upstack generates one `upsell_purchase` for the order and sends it to your configured destinations.

Orders without the `AfterSell Upsell` tag never generate this event. Upstack sends at most one `upsell_purchase` per order.

## Parameters

You don't send this event. Upstack creates it from the original [`purchase`](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/purchase), so it carries the same standard parameters and user data, except that `value` is only the added amount and `items` lists only the added line items.

## Destination Mapping

| Destination | Event name | Sent by default |
| - | - | - |
| Meta | `upsellPurchase` (custom event) | Yes |
| TikTok | `UpsellPurchase` | Yes |
| GA4 | `upsell_purchase` | Yes, if you have an existing GA4 destination |
| Microsoft Ads | `upsell_purchase` (custom event) | Yes |
| Google Ads | The conversion action you map it to | No. Map it to a conversion action |
| Reddit, NewsBreak | Built-in mapping | No. Turn it on with a [destination event mapping](https://docs.upstackdata.com/guides/custom-events/destination-event-mappings.md) |
| Klaviyo, Pinterest | Your choice | No. Add a [destination event mapping](https://docs.upstackdata.com/guides/custom-events/destination-event-mappings.md) |
| Snapchat, LinkedIn, AppLovin | Not sent | No |

Meta needs each custom event approved before you can optimize on it. See [How to approve Meta custom events](https://docs.upstackdata.com/destinations/catalog/meta-capi/how-to-approve-facebook-meta-custom-events.md).

## Metrics Available

In the Upstack dashboard, you can view:

| Metric | Description |
| - | - |
| Upsell Purchases | Total number of upsell purchase events |
| Cost per Upsell Purchase | Average ad spend per upsell conversion |
| Upsell Purchase Value | Total revenue from upsell purchases |

## Related events

* [purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/purchase.md) — The base purchase event
* [rc\_purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/rc-purchase.md) — Returning customer purchases
* [all\_purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/upstack-generated/all-purchase.md) — All purchases
* [AOV Events](https://docs.upstackdata.com/event-tracking/event-taxonomy/upstack-generated/aov-events.md) — Purchase segmentation by order value


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.