CONNECTIONS / Google Sheets
Google Sheets + Datahash: rows become ad signals.
A team adds rows by hand or a linked form appends them automatically, and the sheet keeps growing throughout the day. Signals watches the tab, reads only the rows added since the last check, hashes the identifiers, and routes each one to Meta, Google, TikTok, and Snap.
- ● google-sheets :: signals live
- > tab synced Leads!A2:G842
- > new rows=14 since last check
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 81%
The signal Google Sheets yields, and receives.
Every kind of signal that moves between Google Sheets and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Signals checks the tab or named range on a schedule, so a sheet a growth or ops team edits by hand still feeds the platforms without anyone exporting a file first.
- Lead conversions
- Column headers in the sheet map to event fields once, so a marketer adding a column for a new campaign does not need an engineer to touch the mapping again.
- Custom audiences
- Emails and phone numbers are hashed the moment a row is read, and nothing from the sheet is stored beyond that single read; only the resulting events move on.
- Lead generation inbound
- A row that fails to match an identifier is flagged with a reason instead of dropped silently, so whoever edits the sheet can see it and fix the row.
Pick your platform. Every use case for it, in one place.
Every way Google Sheets data moves, grouped by platform and ranked by how many use cases Google Sheets 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 Sheets with read-only access scoped to one spreadsheet.
-
Watch
Choose the tab or named range Signals should watch for new rows.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
Google Sheets questions, answered.
What happens if someone edits an old row instead of adding a new one?
Signals tracks rows by position and a change marker, so an edited existing row is treated as an update rather than a new event and re-sent with the corrected values. Only rows inside the watched range are read, so notes or scratch columns outside it are ignored. Deleted rows are skipped safely without breaking the next scheduled check.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed as each row is read, and no PII is stored on host servers in Datahash Cloud. The sheet itself is never copied; only the rows in the watched range are read and discarded from memory once hashed. A self-hosted Core deployment keeps that hashing inside your own environment when data cannot leave your perimeter.
How often is the sheet checked for new rows?
On a schedule you choose, from every few minutes up to daily, so a form appending a handful of rows a day and a sheet a team edits constantly can both run on a cadence that fits. Each check reads only rows added or changed since the last pass, so thousands of historical rows never get reprocessed.
NEXT STEP
See your Google Sheets data working in every ad platform.
Ready to enable a use case, or still mapping what Google Sheets data could do? Our team helps you find the right place to start.