CONNECTIONS / HubSpot / HubSpot to Google Store Sales
Report HubSpot deal revenue through Google Store Sales.
Some deals never had a click for Google to see. Store Sales Direct matches on who bought instead of what they clicked, and Signals prepares the hashed contact and deal data it needs.
- ● hubspot → google.store_sales :: live
- > event Deal closed-won value=33,750 AED
- > event Contact updated address confirmed
- hash sha256(email,phone,address)
- route google.store_sales upload batch=nightly
- ✓ delivered · transaction matched
WHAT THIS ENABLES
HubSpot to Google Store Sales
HubSpot to Google Store Sales turns closed-won deals and their contact records into Store Sales Direct uploads, matched on hashed identity rather than a click ID, so showroom and phone revenue still reaches Smart Bidding.
- In-store and phone-closed revenue recorded in HubSpot, counted in Google Ads reporting.
- Bid strategies learning from sales that a landing page never saw happen.
- A single upload path whether or not the underlying deal ever carried a GCLID.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how HubSpot closes the loop.
Built for the teams that own the number.
Teams already running Google Store Sales from POS who want HubSpot-sourced deals included too.
From kickoff to verified events.
-
Connect
Private app token limited to the HubSpot fields that describe the contact and the closed amount.
-
Map
The deal amount and its contact's identifiers take the shape of Google's Store Sales Direct match-key schema.
-
Deliver
Uploads run nightly or weekly, and Google reports matched transactions per batch.
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 HubSpot records the event. |
What Store Sales actually receives.
- ● signals :: transaction payload
- > POST /store_sales_direct source=hubspot.deal
- hashed_email sha256 "4b7f92…" · hashed_phone sha256 "a03ce1…"
- transaction_amount 33750 · currency_code AED
- transaction_date_time "2026-07-16 18:05:00+04:00"
- ✓ accepted · matched=true
Adjacent moves on the same stack.
from HubSpot
HubSpot to Google OCI
HubSpot to Google Offline Conversion Import keeps a captured GCLID pinned to the HubSpot…
Learn more
from HubSpot
HubSpot to Meta Offline CAPI
HubSpot to Meta Offline Conversions API takes each deal HubSpot marks closed-won and…
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.
How well do HubSpot contact records match once Store Sales hashes them?
Contact data quality decides this one almost entirely. Hashing works with whatever the record holds, so a contact carrying verified email, phone, and a confirmed address gives Google the most to match against, and a sparse record gives it very little, whatever the deal was worth. We look at your HubSpot property fill rates during discovery, which sets a realistic expectation before the first upload rather than after it.
Does Store Sales Direct care whether the HubSpot deal has a GCLID?
It does not. Identity is the match key here: hashed email, phone, and address stand in for the click ID entirely, which is what makes the format usable for a sale no ad click ever preceded. Plenty of teams still run OCI in parallel, letting whichever match path fits a given deal carry it, but Store Sales on its own never asks for a GCLID.
Can a HubSpot workflow trigger the Store Sales upload instead of waiting for the nightly batch?
The upload itself still runs on Signals' own schedule against the Google Ads API, but a HubSpot workflow can mark a deal ready for upload the moment a rep confirms the sale, so the deal is queued for the very next scheduled batch instead of waiting for someone to update the record hours later.
NEXT STEP