CONNECTIONS / Salesforce / Salesforce to Google EC for Leads
Salesforce stages to Google EC for Leads.
Signals captures the GCLID when the form submits, stores it on the Salesforce record, and returns hashed stage conversions to Google Ads as opportunities progress.
- ● salesforce → google.ec_leads :: live
- > event Lead created gclid captured
- > event Opportunity stage change SQL→Opportunity
- hash sha256(email,phone) gclid=carried
- route google.ec_leads conversion_action="sql_reached"
- ✓ delivered · bid signal live
WHAT THIS ENABLES
Salesforce to Google EC for Leads
Salesforce to Google Enhanced Conversions for Leads captures GCLID at the lead form, carries it through Salesforce's opportunity stages, and delivers hashed stage conversions to Google Ads so lead campaigns bid toward revenue, not raw form fills.
- Opportunity milestones reported to Google as distinct conversion actions.
- Bidding weighted toward clicks that become real pipeline.
- Long sales cycles still attributed through hashed identifiers when the click ID fades.
WHAT FLOWS WHERE
Salesforce to EC for Leads, mapped.
Lead creation and opportunity stage changes exit Salesforce, pick up hashing in Signals, and register at Google's Enhanced Conversions API as stage conversions.
Lead creation and opportunity stage changes exit Salesforce, pick up hashing in Signals, and register at Google's Enhanced Conversions API as stage conversions.
Built for the teams that own the number.
Revenue teams whose opportunities mature long after the first click.
From kickoff to verified events.
-
Connect
GCLID captured at the form and written to the Salesforce lead with hashed identifiers.
-
Map
Each opportunity stage tied to its own Google Ads conversion action.
-
Deliver
Scheduled Google Ads API delivery with hashed user data as the fallback match key.
What ships with this use case.
Google campaigns judged on qualified pipeline, with values where you map them.
An always-on feed replacing periodic conversion imports.
Identifier handling that stays inside Google's consent requirements.
What EC for Leads actually receives.
- ● signals :: event payload
- > POST /conversion_action source=salesforce.opportunity
- gclid "Cj0KCQjw…" · conversion_action "sql_reached"
- conversion_value 1 · currency AED
- hashed_email sha256 "a71c9e…"
- ✓ accepted match=gclid+hashed_email
Adjacent moves on the same stack.
from Salesforce
Salesforce to Meta Conversion Leads
Salesforce to Meta CAPI for CRM is the pipeline that maps opportunity stage changes and…
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 Google EC for Leads
ActiveCampaign to Google EC for Leads: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Enhanced Conversions for Leads
Datahash pushes hashed user data from your CRM back to Google Ads so lead-based campaigns…
Learn moreAsked on almost every call.
Do we need a GCLID on every Salesforce lead for this to work?
No. Enhanced Conversions for Leads matches primarily on hashed email and phone, so a Salesforce lead created without a captured GCLID still counts. Capturing the click ID where the form allows it improves attribution precision, and Datahash sets up that capture as part of the build so both match paths run at once.
Which Salesforce stages should feed Google EC for Leads?
Most teams send the stages that predict revenue, commonly SQL, Opportunity, and Closed Won, each registered as its own conversion action in Google Ads. Custom stage names in your Salesforce pipeline are mapped during the working session, and the set can change later without touching the underlying connection.
How is EC for Leads different from Offline Conversion Import?
OCI matches purely on the GCLID captured at click, so it fails outright when that identifier is lost between form and close. EC for Leads adds hashed user data as a second match path, which survives longer Salesforce sales cycles and cross-device journeys. Many advertisers run both side by side on the same underlying pipeline.
NEXT STEP