Global event mappings

Set up a custom event once and every connected destination gets it.

A global event mapping sends your destinations an extra event when a condition is met — for example, every purchase over $500 also sends high_value_purchase. Set it up once and every connected destination gets it.

Good to know:

• Your standard events keep firing. A mapping adds an event, it doesn’t replace one.
• The new event is real — it shows up in your Upstack reporting too, not just at your destinations.
• You can turn it off for one destination later without affecting the rest.

LinkedIn, Snapchat, AppLovin, and NewsBreak can’t receive custom events at all.

Google Ads can, but not through global mappings — every custom event needs its own conversion action, so you set them up per destination. Enable its Conversions API, then add them under Destination event mappings.

Create one

1. Open the panel

   Go to Event Destinations and click the Event Mappings button (globe icon). The Global Event Mappings panel opens.

2. Click Add Mapping

   Give it a Display name — just for you, destinations never see it. Then pick the Base event: a standard event like purchase, or type a custom one.

3. Name the event

   Destination event name is what your destinations receive. Lowercase with underscores: high_value_purchase.

4. Set the conditions

   Under Only when…, add the rules that decide when it fires — for example, order value is greater than 500. Leave empty and it fires every time.

5. Save

   Optionally turn on Override event value first to send profit or a formula instead of the event’s own value. Then click Save custom event. Done.

Example: orders over $500

Field	Value
Display name	High value purchase
Base event	purchase
Only when	order value is greater than 500
Destination event name	high_value_purchase

Every purchase over $500 now also sends high_value_purchase.

Confirm it’s firing

Place a test order that matches your conditions, then open Upstack’s Events Manager — the mapped event appears in the events list with the name you chose.

Sending a revenue event to Meta? Pair it with a matching Custom Conversion in Meta Events Manager, or you can’t select it as a campaign goal. See Approve Meta custom events.

Conditions

A condition is a field, an operator, and a value — order value is greater than 500. You can use any field the event carries: order and cart values, customer traits, page and campaign context, device.

Conditions sit in groups. Match ALL means every condition in the group must be true; ANY means one is enough. Add more groups for either/or logic.

If two mappings could match the same event, both fire. Make each mapping’s conditions specific enough that only one matches.

Related

Destination event mappings

Turn a mapping off for one destination, or add a destination-only trigger.

Value & formulas

Send profit, margin, a fixed amount, or your own formula.

Custom events overview

What custom events are and when to use them.

Approve Meta custom events

Create the matching Custom Conversion in Meta.