CONNECTIONS / Salesforce / Salesforce to Google Store Sales
Salesforce revenue, uploaded as Google Store Sales.
Not every closed deal in Salesforce started with an ad click Google can see. Signals hashes the contact and Opportunity record and uploads it to Store Sales Direct, matching on identity instead of click ID.
- ● salesforce → google.store_sales :: live
- > event Opportunity closed-won value=61,400 AED
- > event Contact updated address confirmed
- hash sha256(email,phone,address)
- route google.store_sales upload batch=nightly
- ✓ delivered · transaction matched
WHAT THIS ENABLES
Salesforce to Google Store Sales
Salesforce to Google Store Sales is the pipeline that hashes contact and closed-won Opportunity data from Salesforce and uploads it to Google's Store Sales Direct spec, so revenue closed by a field sales team or retail location counts toward Smart Bidding even without a GCLID.
- Field-sales and in-store revenue recorded in Salesforce, counted in Google Ads reporting.
- Smart Bidding informed by outcomes that never touched a landing page.
- One upload pipeline covering deals with or without a captured GCLID.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Salesforce closes the loop.
Built for the teams that own the number.
Teams already running Google Store Sales from POS who want Salesforce-sourced field deals included too.
From kickoff to verified events.
-
Connect
Connected App access to the Salesforce Contact and Opportunity objects that carry closed-won revenue.
-
Map
Contact identifiers and Opportunity amount shaped to Google's Store Sales Direct match-key schema.
-
Deliver
Nightly or weekly upload through the Google Ads API, with matched transaction reporting.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Store Sales reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment Salesforce records the event. |
What Store Sales actually receives.
- ● signals :: transaction payload
- > POST /store_sales_direct source=salesforce.opportunity
- hashed_email sha256 "7d0f4b…" · hashed_phone sha256 "e29a86…"
- transaction_amount 61400 · currency_code AED
- transaction_date_time "2026-07-13 16:27:00+04:00"
- ✓ accepted · matched=true
Adjacent moves on the same stack.
from Salesforce
Salesforce to Google OCI
Salesforce to Google Offline Conversion Import is the pipeline that persists the GCLID…
Learn more
from Salesforce
Salesforce to Meta Offline CAPI
Salesforce to Meta Offline Conversions API is the pipeline that routes closed-won…
Learn more
same use case
ActiveCampaign to Google Store Sales
ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…
Learn moreAsked on almost every call.
What match rate should we expect from Salesforce-sourced Store Sales uploads?
It depends on how complete the Contact record is at the point of close. Deals with a verified email, phone, and address on the Salesforce Contact typically match well once hashed; thinner records match less reliably. We baseline your Contact data quality during discovery and report the accepted match rate after every upload.
Do we still need a GCLID if we run Store Sales from Salesforce?
No. Store Sales Direct matches on hashed identity rather than click ID, which is exactly why it works for deals that close in a branch, showroom, or over the phone with no ad click behind them at all. Teams running both OCI and Store Sales get coverage either way a deal arrives in Salesforce.
NEXT STEP