CONNECTIONS / Zithara / Zithara to Google Store Sales
From Zithara customer records to Google Store Sales matching.
Connect Zithara and point Signals at your Zithara customer records; it matches in-person transactions to Google accounts as store-sales conversions as records change, hashed and consent-checked for Google Ads.
- ● zithara → google.sales :: live
- > read closed_deals rows=58,294
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 46,052 matched
WHAT THIS ENABLES
Zithara to Google Store Sales
Zithara to Google Store Sales: your Zithara customer records, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions as records change.
- Offline and in-store sales from your Zithara customer records activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
- Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Zithara customer records by retail CRM teams running Zithara.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Zithara closes the loop.
Built for the teams that own the number.
Retail CRM teams running Zithara activating Google Store Sales matching straight from Zithara customer records.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Zithara, reading only your Zithara customer records to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals reads your Zithara customer records, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.
-
Deliver
On each run, Signals pulls your Zithara customer records, matches in-person transactions to Google accounts as store-sales conversions, and sends only the records that changed, with the store-sales match rate in the debugger.
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 Zithara records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=zithara.closed_deals
- transaction_time 2026-07-15T11:18:41 · transaction_amount_micros 42290000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=79%
Adjacent moves on the same stack.
from Zithara
Zithara to Google OCI
Zithara to Google Offline Conversions: your Zithara customer records, hashed and…
Learn more
from Zithara
Zithara to Meta Offline CAPI
Zithara to Meta Offline CAPI: your Zithara customer records, hashed and consent-checked,…
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 often does the Zithara Google Store Sales sync run?
You set the cadence, from near-real-time to a nightly Zithara sync of your Zithara customer records into Google Ads. Since Signals sends only the records that changed, counter and showroom revenue inside the same ROAS view as online orders keeps pace and retail CRM teams running Zithara watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.
What match rate should a Zithara-sourced Google Store Sales batch expect?
In Zithara, match rate tracks the email and phone quality your Zithara customer records carry. Clean identifiers land for Google Ads; blank ones never will. The first Store Sales Direct API report shows retail CRM teams running Zithara where the store-sales match rate needs work, a data-quality task handled in Zithara.
NEXT STEP