CONNECTIONS / Wasabi / Wasabi to Google Customer Match
Wasabi objects into Google Ads, built for Google Customer Match.
Connect Wasabi and point Signals at your Wasabi objects; it projects your segments into Google Ads as Customer Match lists each time a new file lands, hashed and consent-checked for Google Ads.
- ● wasabi → google.match :: live
- > read segments rows=32,674
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 24,179 matched
WHAT THIS ENABLES
Wasabi to Google Customer Match
Wasabi to Google Customer Match: your Wasabi objects, hashed and consent-checked, feed Google Ads as Signals projects your segments into Google Ads as Customer Match lists each time a new file lands.
- Customer segments from your Wasabi objects 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 Wasabi objects by teams archiving to Wasabi.
WHAT FLOWS WHERE
Wasabi to Customer Match, mapped.
Each sync hands the customer segments from your Wasabi objects 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 Wasabi objects 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.
Teams archiving to Wasabi activating Google Customer Match straight from Wasabi objects.
From kickoff to verified events.
-
Connect
A read-only key scoped to the Wasabi bucket you name to feed Google Ads' Customer Match API, sized for the serving-size threshold.
-
Map
Signals picks up your Wasabi objects, 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 Wasabi objects, projects your segments into Google Ads as Customer Match lists, and processes only the newly dropped file, 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 Wasabi objects and processes only the newly dropped file.
Lists that self-maintain across syncs from your Wasabi objects, with transfer overhead steady because Signals processes only the newly dropped file.
A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Wasabi objects.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=wasabi.segments
- operation ADD · user_list "segment_55313"
- hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
- members_uploaded 32,674 · members_matched 24,179
- ✓ accepted match=74%
Adjacent moves on the same stack.
from Wasabi
Wasabi to Meta Custom Audience
Wasabi to Meta Custom Audience: your Wasabi objects, hashed and consent-checked, feed Meta…
Learn more
from Wasabi
Wasabi to TikTok Custom Audience
Wasabi to TikTok Custom Audience: your Wasabi objects, hashed and consent-checked, feed…
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 Wasabi Google Customer Match sync run?
Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds Google Ads on that cadence. Each run processes only the newly dropped file, so lists that self-maintain across syncs holds up on the serving-size threshold. The live debugger confirms every delivery inline.
What match rate should a Wasabi-sourced Google Customer Match batch expect?
Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Customer Match API pinpoints the serving-size threshold, the number teams archiving to Wasabi tune against.
NEXT STEP