Skip to main content
Global event mappings let you take an event that’s already flowing through Upstack — like a purchase — and send it to your destinations under a new name when it meets conditions you choose. You set it up once, and every connected destination inherits it. It’s the fastest way to create events like high_value_purchase or subscription_purchase without touching each destination one by one.

​
Prerequisites

  • An Upstack Data account with the pixel installed and events flowing
  • At least one destination connected
  • A clear idea of the event you want to create and when it should fire

​
What a global event mapping does

A mapping watches for a source event (standard or custom), and when its conditions match, it sends that event to your destinations under a new name. For example, a purchase over $500 can be sent as high_value_purchase, so your ad platforms can optimize for high-value buyers specifically. A few things to know up front:
  • It applies everywhere. Every connected destination inherits your global mappings automatically. You can fine-tune or turn one off for a single destination later — see Destination event mappings.
  • It shows up in your reporting. A global mapping fires as a real event, so it appears in your Upstack analytics and event debugger as well as at your destinations.
  • Your standard events keep flowing. A mapping adds a renamed event — it doesn’t replace or stop the original.
Google Ads is the one exception — it doesn’t use event mappings. Google Ads relies on its own Conversion Action setup instead.

​
Create a global event mapping

1

Open Event Mappings

Go to Event Destinations and click the Event Mappings button (globe icon) in the page header. The right-side Global Event Mappings panel opens, listing any mappings you already have.
2

Add a mapping

Click Add Mapping to open the trigger editor.
3

Name it and pick the source event

Give the mapping a clear Name (this is just for you). Then choose the Source Event — pick a standard event like purchase from the list, or type your own custom event name.
4

Set the destination event name

Enter the Destination Event Name — the name your destinations will receive. Use lowercase with underscores, e.g. high_value_purchase.
5

Set priority (optional)

Priority (1-100) controls the order when more than one mapping could apply — higher priority is evaluated first. The default is fine for most setups.
6

Add conditions

Add the conditions that decide when the event fires. Set Match to ALL or ANY of your condition groups, then add conditions inside each group (for example, order value is greater than 500). Use ANY when any one rule should be enough; use ALL when every rule must be true.
7

Save

Click Create Trigger. The mapping is now live for every connected destination (except Google Ads).

​
Worked example: high-value purchases

Say you want to optimize for orders over $500.
  1. Name: High value purchase
  2. Source Event: purchase
  3. Destination Event Name: high_value_purchase
  4. Conditions: Match ALL → order value is greater than 500
Now whenever a purchase over $500 comes through, your destinations also receive a high_value_purchase event — and it shows up in your Upstack reporting so you can confirm it’s firing.
If you send a revenue event to Meta, pair it with a matching Custom Conversion in Meta Events Manager so you can select it as a campaign optimization goal. See Approve Meta custom events.

​
Frequently asked questions

No. A mapping adds a renamed event when its conditions match — your standard events keep flowing exactly as before.
Yes. Global mappings fire as real events, so they show up in your Upstack analytics and event debugger in addition to being sent to your destinations.
Every connected destination inherits it automatically — except Google Ads, which uses Conversion Actions instead. You can disable or override a global mapping for a single destination from that destination’s Event Mappings tab.
Higher-priority mappings are evaluated first. Use the Priority field to control the order when you have overlapping mappings.

Destination event mappings

Disable or override a global mapping for a single destination, or add destination-only triggers.

Custom events overview

What custom events are and when to use them.

NC & RC Purchase in Meta

Set up new- and returning-customer purchase events in Meta.

Approve Meta custom events

Approve and verify custom events in Meta Events Manager.