Conversion tracking for Salesforce
Salesforce is where the revenue is recorded and where the click identifier goes to die. Custom fields are not carried through lead conversion unless someone configures the mapping, so the value sits happily on the Lead, the Opportunity has nothing, and no error is raised anywhere. That single unconfigured mapping is the most common reason a Salesforce offline conversion import matches almost nothing.
Free30 minutesNo obligation
Salesforce tracking · 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 tracking · the fix
What changes — Salesforce tracking
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 tracking · architecture
What Salesforce actually lets you do
Salesforce can do anything and will do exactly what it was configured to do, including losing your fields.
- 1
Custom fields on Lead, Contact, Opportunity
Three objects, and the identifier needs to exist on all three.
- 2
Lead conversion field mapping
Configured explicitly, or the field is silently dropped.
- 3
Flows and Apex triggers
Fire an action on stage change. The clean upload trigger.
- 4
Web-to-Lead
Simple, and it posts only what the form contains.
- 5
The API
Full access for reconciliation and outcome export.
Salesforce tracking · 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 tracking · prove
The QA evidence — Salesforce tracking
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 tracking · 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 tracking · 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 tracking · what we deliver
The event map on Salesforce
Landing
Click ID captured and written into the form.
Lead created
Web-to-Lead or API, carrying all four parameters.
Lead converted
The step where unmapped fields vanish. Configure the mapping.
Opportunity stage change
Flow-triggered. The realistic bidding target.
Closed won
With amount, where the cycle fits the import window.
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 tracking questions, answered
Custom fields aren't carried automatically. The mapping has to be configured explicitly on conversion, and it almost never is.
Convert a test Lead and look at the resulting Opportunity. Two minutes, and it reproduces the most common Salesforce tracking fault.
A qualified stage inside the import window. Closed-won is often too slow and starves the conversion action.
Store both and choose deliberately. The worst answer is whichever field happened to be written last.
Free · 30 min
Get Salesforce tracking done properly
WhatsAppFree30 minutesNo obligation
