AOV Purchase Events - Upstack Data

Five event names are set aside for purchases split by order value. Upstack has built-in measures for each of them, but it doesn’t calculate AOV thresholds or generate these events from your order history. To use one, create it yourself with a global event mapping on purchase, with a condition on order value.

Event names

Event name	Built-in measures
`high_aov_purchase`	High AOV Purchases, Cost per High AOV Purchase, High AOV Purchase Value
`low_aov_purchase`	Low AOV Purchases, Cost per Low AOV Purchase, Low AOV Purchase Value
`p70_aov_purchase`	P70 AOV Purchases, Cost per P70 AOV Purchase, P70 AOV Purchase Value
`p80_aov_purchase`	P80 AOV Purchases, Cost per P80 AOV Purchase, P80 AOV Purchase Value
`p90_aov_purchase`	P90 AOV Purchases, Cost per P90 AOV Purchase, P90 AOV Purchase Value

The measures count events with exactly these names, so use the name as written when you set up the mapping.

Set one up

Pick a threshold from your own order data, for example the order value your top 10% of orders exceed. Then create a global event mapping:

Field	Value
Base event	`purchase`
Only when	order value is greater than your threshold
Destination event name	`p90_aov_purchase`

Every purchase over the threshold now also sends p90_aov_purchase. The threshold stays fixed until you edit the mapping, so revisit it when your order values shift. A purchase can match more than one mapping. If you create p70_aov_purchase, p80_aov_purchase and p90_aov_purchase, a large order fires all three.

Where it goes

A global event mapping sends the new event to your connected destinations under the name you chose. Some destinations can’t receive it, and you can turn it off per destination. See Global event mappings for the details.

purchase — The base purchase event
nc_purchase — New customer purchases
rc_purchase — Returning customer purchases
all_purchase — All purchases