Back to DocsServer-Side Tracking

Conversion Event Mapping

Map your dispositions to platform-specific conversion events for each connected ad account.

Table of contents

What Is Event Mapping?

Event mapping is the connection between your DealOracle dispositions and the conversion events on each ad platform. It tells DealOracle: "When a lead reaches this outcome, fire this specific event on that platform."

For example:

  • When a lead's disposition is set to "Sold" → Fire a "Purchase" event on Facebook
  • When a lead's disposition is set to "Qualified" → Fire a "Lead" event on Google
  • When a lead's disposition is set to "Appointment Set" → Fire a "SubmitForm" event on TikTok

Without event mapping, DealOracle wouldn't know which platform events correspond to which dispositions. Event mapping is what makes the entire server-side tracking pipeline work.

Why It Matters

  • Correct attribution — The right event type ensures the platform categorizes the conversion correctly
  • Proper optimization — Platforms optimize differently for "Purchase" vs "Lead" events
  • Accurate reporting — Your conversion reports in the ad platform reflect the real outcomes

Setting Up Mappings

Configure event mappings for each connected integration:

Step-by-Step

  1. Navigate to Admin → Integrations
  2. Select the integration you want to configure (e.g., Facebook CAPI)
  3. Click the Event Mapping tab
  4. For each disposition, select which platform event to fire:
Your DispositionPlatform EventValue
QualifiedLead$25
Appointment SetCompleteRegistration$50
SoldPurchase$500
  1. Set the conversion value for each mapping (or use the disposition's default value)
  2. Click Save Mappings

Mapping Options

  • Fire event — Select the platform event to trigger
  • Don't fire — Skip this disposition (no event sent for this outcome on this platform)
  • Custom event — Some platforms support custom event names (see platform-specific details below)

Testing Your Mappings

After saving, use the API Tester to send a test event and verify it arrives correctly in the ad platform.

Platform-Specific Events

Each ad platform has its own set of standard conversion events:

Facebook / Meta (CAPI)

Event NameTypical Use
PurchaseFinal sale / deal closed
LeadQualified lead
CompleteRegistrationAppointment set / form completed
AddToCartStrong intent signal (e.g., credit application)
InitiateCheckoutDeal in progress
ViewContentLead engaged with content
ContactLead made contact
CustomEventAny custom name you define
EventTypical Use
Conversion Action IDEach Google conversion action has a unique ID. Map your dispositions to the appropriate conversion action in your Google Ads account.

Note: Google uses conversion action IDs rather than named events. You'll need to create conversion actions in Google Ads first, then map them in DealOracle.

TikTok (Events API)

Event NameTypical Use
CompletePaymentFinal sale
SubmitFormForm submission / appointment
ContactLead made contact
SubscribeSubscription signup
PlaceAnOrderOrder placed

Snapchat (Conversions API)

Event NameTypical Use
PURCHASEFinal sale
SIGN_UPRegistration
ADD_TO_CARTIntent signal
START_CHECKOUTDeal in progress

LinkedIn (Conversions API)

EventTypical Use
Conversion Rule IDSimilar to Google, LinkedIn uses conversion rule IDs. Create rules in LinkedIn Campaign Manager, then map in DealOracle.

Multi-Platform Mapping

One of DealOracle's most powerful features is the ability to fire events to multiple platforms simultaneously from a single disposition change.

How It Works

When you set a lead's disposition to "Sold":

  1. DealOracle checks ALL connected integrations
  2. For each integration, it looks up the event mapping for "Sold"
  3. It fires the mapped event on each platform in parallel:
Disposition: "Sold" ($500)
   ├──▶ Facebook CAPI  →  Purchase ($500)  → ✅ 200 OK
   ├──▶ Google Ads     →  Conversion #123  → ✅ 200 OK
   ├──▶ TikTok Events  →  CompletePayment   → ✅ 200 OK
   └──▶ Snapchat CAPI  →  PURCHASE ($500)   → ✅ 200 OK
  1. Results for each platform are logged in the lead's Event Stream

Different Events Per Platform

You can map the same disposition to different events on each platform. For example:

DispositionFacebookGoogleTikTok
QualifiedLeadConversion #101SubmitForm
SoldPurchaseConversion #102CompletePayment
Appointment SetCompleteRegistrationConversion #103Contact

Selective Platform Firing

You don't have to fire events on every platform for every disposition. Set any mapping to "Don't fire" to skip that platform:

DispositionFacebookGoogleTikTok
QualifiedLeadDon't fireDon't fire
SoldPurchaseConversion #102CompletePayment

This is useful when you only want certain platforms to receive certain events.

#conversion#events#mapping#sst