> ## 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.

# Destination event mappings in Upstack

> Fine-tune event mappings for a single destination — turn an inherited global mapping off, override it, or add a trigger that only one destination receives.

[Global event mappings](/guides/custom-events/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](/get-started/connect-a-destination) and saved
* Familiarity with [global event mappings](/guides/custom-events/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.

<Note>
  The Event Mappings tab appears only after a destination is saved, and it isn't available for **Google Ads** (Google Ads uses Conversion Actions instead).
</Note>

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.

<Info>
  Turning a mapping off here only affects this one destination. The global mapping still fires and still reaches your other destinations and your reporting.
</Info>

## 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 **Display name**, **Base event**, **Destination event name**, optional **conditions**, and an optional **value override** — then click **Save custom event**.

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

<CardGroup cols={2}>
  <Card title="Global event mappings" icon="globe" href="/guides/custom-events/global-event-mappings">
    Create a mapping once and send it to every destination.
  </Card>

  <Card title="Custom events overview" icon="bolt" href="/guides/custom-events/how-to-create-custom-event-triggers">
    What custom events are and when to use them.
  </Card>

  <Card title="Connect a destination" icon="plug" href="/get-started/connect-a-destination">
    Add Meta, Google, TikTok, Klaviyo, and more.
  </Card>

  <Card title="NC & RC Purchase in Meta" icon="meta" href="/guides/facebook-ads/set-up-nc-and-rc-purchase-events-in-meta">
    Set up new- and returning-customer purchase events in Meta.
  </Card>
</CardGroup>