CONNECTIONS / Google Drive
Google Drive + Datahash: exports become ad signals.
A recurring job or a teammate drops an exported report or CSV into a shared drive in Google Drive. Signals watches that location, hashes the identifiers in each file as it lands, and routes matched rows to Meta, Google, TikTok, and Snap, then discards the file.
- ● google-drive :: signals live
- > file arrived /Shared drives/Growth/exports/leads_2026-07-18.csv
- > parse rows=33,772 schema=leads
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 79%
The signal Google Drive yields, and receives.
Every kind of signal that moves between Google Drive and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A report landing in the watched shared drive folder is picked up on schedule and parsed, so a scheduled Sheets or BigQuery export reaches the platforms without a manual step.
- Lead conversions
- The column mapper reads whatever header row that report uses, so a shared drive that several people export into does not need one fixed file layout to stay usable.
- Custom audiences
- The moment the report is opened, emails and phone numbers become SHA-256 hashes, and the file is deleted once the run finishes so no export copy remains.
- Lead generation inbound
- Each row's outcome is reported per destination as it happens, turning a platform rejection into a visible flag rather than a quiet gap in match rate.
Pick your platform. Every use case for it, in one place.
Every way Google Drive data moves, grouped by platform and ranked by how many use cases Google Drive supports.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Google Drive with a scoped, read-only service account.
-
Watch
Point Signals at the shared drive folder and file pattern to watch.
-
Map
Translate spreadsheet or export columns into event and identifier fields with the visual mapper.
-
Go live
Preview a batch of sample rows in the live debugger before turning delivery on.
Google Drive questions, answered.
Which file formats are supported?
A header-row CSV or TSV is the typical export, and fixed-width layouts are supported by mapping columns manually. You choose a folder inside a shared drive and a file pattern, and Signals parses whatever lands there right away, so a recurring Sheets or BigQuery export needs no additional configuration.
Can Signals read from a shared drive rather than My Drive?
Yes, and a shared drive is the recommended setup since ownership stays with the team rather than one person's account. Signals connects with a scoped, read-only service account granted access to that specific shared drive folder, so existing sharing permissions and any access review your workspace runs are unaffected by the connection.
Is customer PII stored by Datahash?
PII is not retained. Datahash hashes every identifier with SHA-256 as the file is ingested, host servers in Datahash Cloud never store PII, and the source file is discarded right after processing. A self-hosted Core deployment is available for teams whose data cannot leave their perimeter, hashing everything internally before delivery.
How often are files picked up?
Pickup frequency is configurable, from a few-minute interval up to a single daily run, and each report is processed exactly once with results returned row by row. The next run starts as soon as a new file lands in the shared drive, so cadence follows whatever schedule your export or script already keeps.
NEXT STEP
See your Google Drive data working in every ad platform.
Ready to enable a use case, or still mapping what Google Drive data could do? Our team helps you find the right place to start.