Destination event mappings

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

Global mappings go to every destination. When one destination needs to behave differently, change it on the destination itself.

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.

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

1. Click Add Custom Trigger

   In the Custom Triggers section, click + Add Custom Trigger.

2. Fill in the mapping

   Same fields as a global mapping: Display name, Base event, Destination event name, optional conditions, and an optional value override.

3. Save

   Click Save custom event. The trigger belongs to this destination only.

4. Save the destination

   Click Save Changes at the bottom of the page. Your changes aren’t live until you do.

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

Global event mappings

Create a mapping once and send it everywhere.

Value & formulas

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

Custom events overview

What custom events are and when to use them.

Connect a destination

Add Meta, Google, TikTok, Klaviyo, and more.