CONNECTIONS / Salesforce / Salesforce to Google Customer Match
Customer Match, kept current from Salesforce.
Signals reads the segments your revenue team maintains in Salesforce and mirrors them into Google Customer Match, pushing adds and removals on whatever schedule you pick.
- ● salesforce → google.customer_match :: live
- > sync segment top_accounts_won rows=42,118
- hash sha256(email,phone)
- route google.customer_match upsert
- ✓ list refreshed · 38,904 matched
WHAT THIS ENABLES
Salesforce to Google Customer Match
Salesforce to Google Customer Match keeps Google's Customer Match lists synced with the high-value segments living in Salesforce, adding and removing members automatically so Search, YouTube, and Display campaigns always target the customers you actually want reached.
- Salesforce segments mirrored into Google Ads with no export step in between.
- Lookalike seeds and Smart Bidding signals drawn from cohorts your CRM already ranks.
- Existing customers excluded from acquisition campaigns the moment Salesforce says so.
WHAT FLOWS WHERE
Salesforce to Customer Match, mapped.
Salesforce segment changes flow through Signals, which hashes each record and updates the Google Customer Match list with the corresponding adds and removals.
Salesforce segment changes flow through Signals, which hashes each record and updates the Google Customer Match list with the corresponding adds and removals.
Built for the teams that own the number.
Marketers re-uploading CRM exports to Google Ads by hand.
From kickoff to verified events.
-
Connect
Scoped, read-only Connected App access to the Salesforce segment object or report you choose.
-
Map
Identifier columns hashed and shaped to the Customer Match upload schema.
-
Deliver
Delta uploads to Google Ads on your cadence, with matched-size reporting per list.
What ships with this use case.
Salesforce-defined audiences serving across Search, YouTube, Gmail, and Display.
Acquisition campaigns that stop paying to reach people already in your CRM.
Identifier hashing that satisfies Google's Customer Match policies end to end.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=salesforce.segment
- operation ADD · user_list "top_accounts_won"
- hashed_email sha256 "c48a12…" · hashed_phone sha256 "9de701…"
- members_uploaded 42,118 · members_matched 38,904
- ✓ accepted match=92%
Adjacent moves on the same stack.
from Salesforce
Salesforce to Meta Custom Audience
Salesforce to Meta Custom Audience keeps Meta's Custom Audiences synced with the customer…
Learn more
from Salesforce
Salesforce to TikTok Custom Audience
Salesforce to TikTok Custom Audience keeps TikTok's Custom Audiences synced with the list…
Learn more
same use case
ActiveCampaign to Google Customer Match
ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Google Customer Match
Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…
Learn moreAsked on almost every call.
How often do the Google Ads lists refresh from Salesforce?
Daily is typical, though the cadence runs anywhere from hourly to weekly depending on how often your Salesforce segment actually changes. Each refresh sends only the adds and removals since the last sync, not a full re-upload, so the schedule can run tighter without extra load on your Salesforce org or the Google Ads API.
What happens if a Salesforce segment falls under Google's list minimum?
Google requires a minimum number of matched, active users before a Customer Match list can serve on most surfaces. Datahash monitors the matched size after every sync and flags any Salesforce segment that drops below the threshold, so you know to broaden the report before the list stops serving instead of finding out from a drop in reach.
NEXT STEP