CONNECTIONS / Zithara / Zithara to Google Customer Match
From Zithara customer records to Google Customer Match.
Connect Zithara and point Signals at your Zithara customer records; it projects your segments into Google Ads as Customer Match lists as records change, hashed and consent-checked for Google Ads.
- ● zithara → google.match :: live
- > read segments rows=41,726
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 35,050 matched
WHAT THIS ENABLES
Zithara to Google Customer Match
Zithara to Google Customer Match: your Zithara customer records, hashed and consent-checked, feed Google Ads as Signals projects your segments into Google Ads as Customer Match lists as records change.
- Customer segments from your Zithara customer records activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
- Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Zithara customer records by retail CRM teams running Zithara.
WHAT FLOWS WHERE
Zithara to Customer Match, mapped.
Each sync hands the customer segments from your Zithara customer records to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.
Each sync hands the customer segments from your Zithara customer records to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.
Built for the teams that own the number.
Retail CRM teams running Zithara activating Google Customer Match 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' Customer Match API, sized for the serving-size threshold.
-
Map
Signals reads your Zithara customer records, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.
-
Deliver
On each run, Signals pulls your Zithara customer records, projects your segments into Google Ads as Customer Match lists, and sends only the records that changed, with the serving-size threshold in the debugger.
What ships with this use case.
Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Zithara customer records and sends only the records that changed.
Lists that self-maintain across syncs from your Zithara customer records, with API call volume steady because Signals sends only the records that changed.
A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Zithara customer records.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=zithara.segments
- operation ADD · user_list "segment_63463"
- hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
- members_uploaded 41,726 · members_matched 35,050
- ✓ accepted match=84%
Adjacent moves on the same stack.
from Zithara
Zithara to Meta Custom Audience
Zithara to Meta Custom Audience: your Zithara customer records, hashed and consent-checked,…
Learn more
from Zithara
Zithara to TikTok Custom Audience
Zithara to TikTok Custom Audience: your Zithara customer records, hashed and…
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 does the Zithara Google Customer Match 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, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and retail CRM teams running Zithara watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.
What match rate should a Zithara-sourced Google Customer Match 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 Customer Match API report shows retail CRM teams running Zithara where the serving-size threshold needs work, a data-quality task handled in Zithara.
NEXT STEP