CONNECTIONS / Box / Box to Google Customer Match
Your Box files, wired to Google Customer Match.
Connect Box and point Signals at your Box files; it projects your segments into Google Ads as Customer Match lists each time a new file lands, hashed and consent-checked for Google Ads.
- ● box → google.match :: live
- > read segments rows=57,447
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 50,553 matched
WHAT THIS ENABLES
Box to Google Customer Match
Box to Google Customer Match: Signals reads your Box files and projects your segments into Google Ads as Customer Match lists, hashed and consent-checked each time a new file lands.
- Customer segments from your Box files 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 Box files by ops teams sharing exports in Box.
WHAT FLOWS WHERE
Box to Customer Match, mapped.
Each sync hands the customer segments from your Box files 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 Box files 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.
Ops teams sharing exports in Box activating Google Customer Match straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Google Ads' Customer Match API, sized for the serving-size threshold.
-
Map
Signals picks up your Box files, 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 Box files, 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 Box files and processes only the newly dropped file.
Lists that self-maintain across syncs from your Box files, 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 Box files.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=box.segments
- operation ADD · user_list "segment_83803"
- hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
- members_uploaded 57,447 · members_matched 50,553
- ✓ accepted match=88%
Adjacent moves on the same stack.
from Box
Box to Meta Custom Audience
Box to Meta Custom Audience: Signals reads your Box files and keeps Meta audiences synced…
Learn more
from Box
Box to TikTok Custom Audience
Box to TikTok Custom Audience: Signals reads your Box files and delivers first-party…
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 Box Google Customer Match sync run?
Delivery tracks Box, run by ops teams sharing exports in Box: a near-real-time or scheduled sync of your Box files 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 Box-sourced Google Customer Match batch expect?
Match rate follows identifier coverage in your Box files, which ops teams sharing exports in Box control, not Box 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 ops teams sharing exports in Box tune against.
NEXT STEP