CONNECTIONS / Microsoft Excel / Microsoft Excel to Google Customer Match
Your Excel workbook rows, wired to Google Customer Match.
Signals reads your Excel workbook rows through read-only access to the Excel workbook you name, then projects your segments into Google Ads as Customer Match lists so Google Ads sees match-ready audiences without an export.
- ● microsoft excel → google.match :: live
- > read segments rows=15,568
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 13,856 matched
WHAT THIS ENABLES
Microsoft Excel to Google Customer Match
Microsoft Excel to Google Customer Match: your Excel workbook rows, 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.
- Signals projects your segments into Google Ads as Customer Match lists, reading your Excel workbook rows each time a new file lands.
- Lists that self-maintain across syncs, with no export step out of your Excel workbook rows.
WHAT FLOWS WHERE
Microsoft Excel to Customer Match, mapped.
Signals picks up the customer segments from your Excel workbook rows; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.
Signals picks up the customer segments from your Excel workbook rows; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.
Built for the teams that own the number.
Finance and ops teams working in Excel who need Customer Match lists that add joiners and drop lapsed members each sync out of Excel workbook rows.
From kickoff to verified events.
-
Connect
Read-only access to the Excel workbook you name, mapped to Google Ads' Customer Match API and tuned for the serving-size threshold.
-
Map
Columns from your Excel workbook rows align to Google Ads' Customer Match API in the visual mapper, hashed as the file lands and checked for the serving-size threshold.
-
Deliver
Each time a new file lands, Signals reads your Excel workbook rows and projects your segments into Google Ads as Customer Match lists, processes only the newly dropped file, with the serving-size threshold watched in the debugger.
What ships with this use case.
Customer Match lists that add joiners and drop lapsed members each sync from your Excel workbook rows, delivered each time a new file lands.
Lists that self-maintain across syncs out of your Excel workbook rows, delivered each time a new file lands without transfer overhead climbing.
Match feedback on the serving-size threshold from Google Ads' Customer Match API each run, tied back to your Excel workbook rows.
What Customer Match actually receives.
- ● signals :: audience upload
- > POST /user_list_operations source=microsoft-excel.segments
- operation ADD · user_list "segment_61948"
- hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
- members_uploaded 15,568 · members_matched 13,856
- ✓ accepted match=89%
Adjacent moves on the same stack.
from Microsoft Excel
Microsoft Excel to Meta Custom Audience
Microsoft Excel to Meta Custom Audience: your Excel workbook rows, hashed and…
Learn more
from Microsoft Excel
Microsoft Excel to TikTok Custom Audience
Microsoft Excel to TikTok Custom Audience: your Excel workbook rows, 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 Microsoft Excel Google Customer Match sync run?
You set the cadence, from near-real-time to a nightly Microsoft Excel sync of your Excel workbook rows into Google Ads. Since Signals processes only the newly dropped file, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and finance and ops teams working in Excel watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.
What match rate should a Microsoft Excel-sourced Google Customer Match batch expect?
Match rate follows identifier coverage in your Excel workbook rows, which finance and ops teams working in Excel control, not Microsoft Excel 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 finance and ops teams working in Excel tune against.
NEXT STEP