CONNECTIONS / Salesforce / Salesforce to Meta Conversion Leads
Salesforce stages to Meta Conversion Leads, mapped once.
Meta's lead objective improves when it sees which leads mattered. Signals translates your Salesforce funnel into the Conversion Leads spec and keeps the feed alive.
- ● salesforce → meta.capi_crm :: live
- > event Opportunity stage change MQL→SQL
- > event Opportunity closed-won value=48,500 AED
- hash sha256(email,phone) pii=cleared
- route meta.capi_crm match 87%
- ✓ delivered · revenue attributed to campaign
WHAT THIS ENABLES
Salesforce to Meta CAPI for CRM
Salesforce to Meta CAPI for CRM is the pipeline that maps opportunity stage changes and closed-won revenue from Salesforce into Meta's Conversion Leads events, so Meta optimizes lead campaigns on pipeline quality instead of raw form-fill volume.
- Opportunity progress narrated to Meta as Conversion Leads events.
- Lead campaigns optimized against the funnel depth you choose.
- Closed-won revenue visible in the same reporting as the original lead.
WHAT FLOWS WHERE
Salesforce to CAPI for CRM, mapped.
Opportunity stage changes and closed-won revenue exit Salesforce, are hashed and deduped by Signals, and post to Meta's Conversion Leads API.
Opportunity stage changes and closed-won revenue exit Salesforce, are hashed and deduped by Signals, and post to Meta's Conversion Leads API.
Built for the teams that own the number.
Teams whose real conversion happens in a sales call, weeks out.
From kickoff to verified events.
-
Connect
Connected App authorization, limited to lead and opportunity objects, revocable anytime.
-
Map
Funnel stages such as Qualified and Converted joined to Conversion Leads events via lead ID.
-
Deliver
Server-side stage delivery in near real time, diagnosable in Events Manager.
What ships with this use case.
Campaign credit that follows the lead all the way to booked revenue.
A stage feed that runs itself once the mapping is agreed.
Identifiers hashed at ingestion, consent respected end to end.
What CAPI for CRM actually receives.
- ● signals :: event payload
- > POST /conversion_leads source=salesforce.opportunity
- event_name "Purchase" · value 48500 AED
- em sha256 "f3a91c…" · ph sha256 "b07de2…"
- lead_id "00Q5f000…" · action_source "system_generated"
- ✓ accepted pii=hashed-at-ingestion
Adjacent moves on the same stack.
from Salesforce
Salesforce to Google EC for Leads
Salesforce to Google Enhanced Conversions for Leads captures GCLID at the lead form,…
Learn more
from Salesforce
Salesforce to TikTok CRM
Salesforce to TikTok CRM Integration is the pipeline that maps Salesforce lead status and…
Learn more
same use case
ActiveCampaign to Meta Conversion Leads
ActiveCampaign to Meta CAPI for CRM: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta CAPI for CRM
Datahash ingests lead status from your CRM and sends Meta the qualified events it needs to…
Learn moreAsked on almost every call.
Is there a minimum volume of Salesforce stage events for Meta to optimize on?
Meta's Conversion Leads optimization needs steady weekly volume on at least one down-funnel stage to learn from, and the right number depends on your funnel shape and sales cycle length. We review your Salesforce stage volumes in the working session and recommend which stage to send first if current volume is thin.
Can we backfill historical Salesforce opportunities into Meta?
Yes, within Meta's accepted lookback window for Conversion Leads events. A backfill lets Meta's optimization start with a fuller picture of which leads converted instead of learning only from stage changes going forward, which is useful when a Salesforce pipeline has months of qualified history already sitting in it.
NEXT STEP