Meta Conversions API setup for Salesforce
Meta from Salesforce follows the same route with an extra constraint: B2B sales cycles routinely outrun Meta's attribution windows, so the realistic optimization target is a qualified stage rather than closed-won.
Free30 minutesNo obligation
Salesforce + Meta CAPI · what breaks
What goes wrong on Salesforce
- 01
Lead conversion drops unmapped fields
The value is on Lead, the Opportunity has nothing, nothing errors. The single most common Salesforce tracking fault.
- 02
Cycles longer than the import window
Enterprise deals routinely close beyond it, so closed-won can't be imported at all.
- 03
Web-to-Lead posting without identifiers
The standard form posts what it's given, and by default that's no click ID.
- 04
Amount changing after close
Upsells and adjustments move the number after the conversion was reported.
Salesforce + Meta CAPI · the fix
What changes — Salesforce + Meta CAPI
Identifiers surviving lead conversion
Mapped explicitly onto Contact and Opportunity.
A bidable milestone inside the window
Qualified, rather than a close nobody can import.
Real amounts fed back
Where the cycle allows.
Salesforce + Meta CAPI · architecture
How Meta tracking behaves on Salesforce
Same plumbing, tighter windows.
- 1
fbclid on all three objects
With conversion mapping.
- 2
Qualified stage as the optimization target
B2B cycles rarely fit Meta's windows.
- 3
Opportunity ID as event_id
Stable and unique.
- 4
Customer data from the Contact
Normalized before hashing.
- 5
Batch uploads deduplicated
Re-uploading the same opportunity is the realistic duplicate risk here.
Salesforce + Meta CAPI · diagnose
Where Salesforce tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Measure the share of Opportunities with a click ID
Not Leads. Opportunities.
- 02
Convert a test lead and check the Opportunity
The classic failure reproduces in two minutes.
- 03
Check conversion field mapping
It's almost never configured.
- 04
Measure median days from click to close
Against the import window.
- 05
Read the match rate after uploading
Not the success message.
Salesforce + Meta CAPI · prove
The QA evidence — Salesforce + Meta CAPI
Run on Salesforce specifically, on a live conversion rather than in preview mode.
Source of truth
your Salesforce opportunity records
- Click ID present on a live Opportunity after a full lead-conversion test.
- All four parameters mapped across Lead, Contact and Opportunity.
- Flow confirmed firing on stage change.
- Uploads confirmed by match rate rather than a success message.
- Opportunity counts reconciled against Salesforce for a closed quarter.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Salesforce + Meta CAPI · free audit
What we check in the free audit
- Measure the share of Opportunities with a click ID
- Convert a test lead and check the Opportunity
- Check conversion field mapping
- Measure median days from click to close
- Read the match rate after uploading
Checked against
your Salesforce opportunity records
Free30 minutesNo obligation
Salesforce + Meta CAPI · when not to buy
When you don't need this on Salesforce
Worth reading before you buy anything, from us or anyone.
- If your Opportunities already carry click IDs and outcomes reach your ad platforms, this is done.
- Converting one test lead and checking whether the field survived takes two minutes and tells you whether you have the classic problem.
- If your median cycle exceeds the import window, no build makes closed-won bidable. Optimize on a qualified stage and say so plainly to whoever asks.
- Salesforce's own ads integrations cover part of this. Check what's already configured before building a parallel path.
Salesforce + Meta CAPI · what we deliver
What gets built for Meta on Salesforce
A shared event ID on both paths
The Salesforce Opportunity ID, stable and available to any flow-triggered action.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
Written guarantee
95%+ tracking accuracy
Measured against your Salesforce opportunity records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Salesforce + Meta CAPI questions, answered
Yes, from a flow on stage change, referencing the identifier on the record.
The Opportunity ID. Stable and unique.
Because B2B cycles routinely outrun Meta's attribution windows, so closed-won arrives too late to be useful for optimization.
Batch re-uploads. Unlike browser tracking, the realistic risk here is sending the same opportunity twice, not double-firing.
Free · 30 min
Get Pixel and CAPI counting once on Salesforce
WhatsAppFree30 minutesNo obligation
