Google Store Sales
Google Store Sales, ready for scheduled uploads.
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS or warehouse into Google Ads.
- ● google.store_sales :: live
- > batch store_transactions rows=8,940
- hash sha256(em,ph,addr) pii=cleared
- upload offline_user_data_job match 47%
- ✓ uploaded · store sales attributed
WHAT THIS ENABLES
Google Store Sales
Google Store Sales is the scheduled upload of hashed in-store transactions from your POS or warehouse to Google Ads, attributing physical revenue to the Search and YouTube campaigns that drove the visit.
- In-store revenue attributed to the Search and YouTube campaigns that drove the footfall.
- Smart Bidding that weighs what happens at the till alongside what happens on the site.
- A nightly automated feed in place of manually formatted Store Sales uploads.
Built for the teams that own the number.
Brands whose ad clicks happen online but whose sales complete in a store, at a counter, or over a call.
From kickoff to verified events.
-
Source
Connect POS, ERP, or warehouse.
-
Match
Hashed email, phone, name, and address prepared per Google spec.
-
Upload
Automated cadence, nightly or weekly.
WHAT FLOWS WHERE
One use case, every source.
A purchase completes at the till, Signals hashes the customer identifiers and the transaction amount from your POS or warehouse, then uploads it to Google Ads through a Store Sales offline user-data job.
A purchase completes at the till, Signals hashes the customer identifiers and the transaction amount from your POS or warehouse, then uploads it to Google Ads through a Store Sales offline user-data job.
What ships with this offering.
In-store revenue visible inside Google Ads reporting.
Smart Bidding informed by offline outcomes.
No manual formatting or upload runs.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: store sales payload
- > POST customers/{id}/offlineUserDataJobs:addOperations
- user_identifiers hashed_email "a2c9…" · hashed_phone_number "6d41…"
- transaction_attribute transaction_amount_micros 249000000
- currency_code AED · conversion_action "store_sale"
- ✓ received · pending_match
Adjacent moves on the same stack.
Google Offline Conversion Import
Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions land in campaign optimization loops.
Learn more
meta
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
Learn more
snap
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreGoogle Customer Match
Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or SingleView, with hashed identifiers.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
What match rate should we expect?
It depends on how much contact data your POS captures at checkout, since matching runs on hashed email, phone, name, and address rather than a loyalty ID alone. With email or phone on a majority of transactions, useful match rates are achievable; we baseline your data during discovery and report accepted rates after every upload so you can see whether checkout capture needs improvement.
How fresh does the transaction data need to be?
Google accepts transactions uploaded within its attribution windows, so nightly or weekly cadence both work for Store Sales. Fresher data feeds Smart Bidding sooner and keeps in-store revenue closer to the campaigns that actually drove the visit, which is why we default new deployments to a nightly batch wherever POS operations allow it, moving to weekly only when the data pipeline requires it.
What are the consent implications of uploading customer data?
All identifiers, email, phone, name, and address, are hashed to SHA-256 before upload, and consent status is carried per record as Google's EU user consent policy requires. Records without the needed consent flags are excluded automatically before the batch reaches Google Ads, so a POS system that has not captured consent for a customer never puts that customer's data at risk.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.