CONNECTIONS / OneDrive / OneDrive to Google Customer Match
From OneDrive files to Google Customer Match.
Connect OneDrive and point Signals at your OneDrive 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.
- ● onedrive → google.match :: live
- > read segments rows=15,425
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 12,957 matched
WHAT THIS ENABLES
OneDrive to Google Customer Match
OneDrive to Google Customer Match: Signals reads your OneDrive 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 OneDrive 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 OneDrive files by teams sharing exports via OneDrive.
WHAT FLOWS WHERE
OneDrive to Customer Match, mapped.
Each sync hands the customer segments from your OneDrive 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 OneDrive 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.
Teams sharing exports via OneDrive activating Google Customer Match straight from OneDrive files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the OneDrive folder you name to feed Google Ads' Customer Match API, sized for the serving-size threshold.
-
Map
Signals picks up your OneDrive 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 OneDrive 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 OneDrive files and processes only the newly dropped file.
Lists that self-maintain across syncs from your OneDrive 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 OneDrive files.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=microsoft-onedrive.segments
- operation ADD · user_list "segment_66211"
- hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
- members_uploaded 15,425 · members_matched 12,957
- ✓ accepted match=84%
Adjacent moves on the same stack.
from OneDrive
OneDrive to Meta Custom Audience
OneDrive to Meta Custom Audience: Signals reads your OneDrive files and keeps Meta…
Learn more
from OneDrive
OneDrive to TikTok Custom Audience
OneDrive to TikTok Custom Audience: Signals reads your OneDrive files and delivers…
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 OneDrive Google Customer Match sync run?
The pace follows your OneDrive files: Signals sends changes from OneDrive to Google Ads each time a new file lands. Because it processes only the newly dropped file, Customer Match lists that add joiners and drop lapsed members each sync stays current while teams sharing exports via OneDrive keep the serving-size threshold in view. Delivery needs no export and no manual upload.
What match rate should a OneDrive-sourced Google Customer Match batch expect?
Coverage of hashed identifiers across your OneDrive files decides it, and teams sharing exports via OneDrive own that inside OneDrive. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the serving-size threshold, which teams sharing exports via OneDrive then raise inside your OneDrive files.
NEXT STEP