Destination event mappings in Upstack

Global event mappings apply to every destination. When you need one destination to behave differently — skip a mapping, change its rules, or get an event no other destination receives — you do that on the destination itself.

​

Prerequisites

• A destination connected and saved
• Familiarity with global event mappings (the inherited ones you’ll fine-tune here)

​

Open the Event Mappings tab

Open the destination from Event Destinations, then select the Event Mappings tab. The tab has two sections:

• Inherited Mappings — the global mappings this destination receives.
• Custom Triggers — mappings that belong to this destination only.

​

Adjust an inherited mapping

Open the Inherited Mappings section to see every global mapping this destination inherits. For any one of them you can:

• Turn it off for this destination — use the switch next to the mapping. The mapping keeps working everywhere else; this destination just stops receiving it.
• Override it — click Override to make a copy you can edit just for this destination. The destination then follows your copy instead of the global version.

​

Add a destination-only custom trigger

Open the Custom Triggers section and click Add Custom Trigger to create a mapping that only this destination receives. It uses the same editor as global mappings — set a Name, Source Event, Destination Event Name, Priority (1-100), and conditions — then click Create Trigger. Each custom trigger in the list can be switched on or off, edited, or removed at any time.

​

Save your changes

Changes on the Event Mappings tab are staged until you save. Click Update Configuration to apply them to the destination.

​

Which mapping wins

When a destination has its own version of a mapping, that version takes over for that destination:

• A destination override beats the inherited global mapping — for that one destination.
• Everywhere else, the global mapping still applies as usual.

​

Related