Event maps: from canonical to destination names

Your app sends canonical events. Every destination wants its own names. Event maps are the per-space translation layer that sits between them — so you never hardcode a destination name in your app.

The idea

For each destination you configure, you map every canonical event to the name that destination expects:

canonical          fb_capi destination
─────────          ───────────────────
contact         →  Contact
subscribed      →  Lead
registration    →  CompleteRegistration
deposit         →  Purchase

When a deposit arrives, XTRACKER looks up the map for each destination and dispatches Purchase to Meta, conv to your affiliate network, and deposit to your webhook — all from one event.

Sensible defaults

A fresh destination isn't blank. XTRACKER pre-fills these defaults so you can ship immediately:

Facebook gets its standard funnel event names. Webhooks and S2S postbacks default to the canonical code itself (identity mapping) — most people keep that and filter on the receiving side.

Editing a map

Open a destination's event maps in the dashboard. Each row is canonical → target name:

Change the right-hand side to whatever your destination expects. For an affiliate network that wants lead and conv:

subscribed    →  lead
registration  →  lead
deposit       →  conv

Note you can collapse several canonicals onto one target (here both subscribed and registration become lead) — handy when a network only recognises two event types.

Unmapped events

If a canonical has no target name for a destination, that event simply isn't dispatched there. So if you only want deposits sent to a network, leave the other three blank for that destination.

Next

• Destinations — the three destination kinds and how delivery works.
• Webhook payload reference — exactly what your webhook receives.