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

> Turn an inherited mapping off for one destination, or add a trigger only that destination receives.

[Global mappings](/guides/custom-events/global-event-mappings) go to every destination. When one destination needs to behave differently, change it on the destination itself.

<Note>
  **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 here.
</Note>

## Open the tab

Open the destination from **Event Destinations** and select the **Event Mappings** tab. The tab appears only after a destination is saved.

## Turn off an inherited mapping

Under **Inherited Mappings** you'll see every global mapping this destination receives, each with a switch. Turn one off and this destination stops receiving it — everywhere else carries on unchanged.

That's the only control here. To send this destination something *different*, turn the inherited mapping off and add a custom trigger instead.

## Add a custom trigger

<Steps>
  <Step title="Click Add Custom Trigger">
    In the **Custom Triggers** section, click **+ Add Custom Trigger**.
  </Step>

  <Step title="Fill in the mapping">
    Same fields as a global mapping: **Display name**, **Base event**, **Destination event name**, optional conditions, and an optional [value override](/guides/custom-events/value-and-formulas).
  </Step>

  <Step title="Save">
    Click **Save custom event**. The trigger belongs to this destination only.
  </Step>

  <Step title="Save the destination">
    Click **Save Changes** at the bottom of the page. Your changes aren't live until you do.
  </Step>
</Steps>

Each trigger can be switched off, edited, or removed later. Custom triggers run alongside anything the destination still inherits — so if you're replacing an inherited mapping rather than adding to it, turn the inherited one off.

## 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 everywhere.
  </Card>

  <Card title="Value & formulas" icon="calculator" href="/guides/custom-events/value-and-formulas">
    Send profit, margin, a fixed amount, or your own formula.
  </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="/quickstart/connect-a-destination">
    Add Meta, Google, TikTok, Klaviyo, and more.
  </Card>
</CardGroup>