CONNECTIONS / GCS
GCS + Datahash: Google exports become ad signals.
GA4 and BigQuery exports often land as files in Google Cloud Storage before they go anywhere else. Signals reads each file as it arrives, hashes the identifiers, and routes the rows to every connected ad platform.
- ● gcs :: signals live
- > object arrived gs://ga4-exports/daily/events-2026-07-18.csv
- > parse rows=64,320 schema=ga4_events
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 83%
The signal GCS yields, and receives.
Every kind of signal that moves between GCS and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file that lands in the watched GCS bucket, including a scheduled BigQuery export, is picked up on schedule and parsed, so a nightly analytics job becomes events without anyone moving the file again.
- Lead conversions
- The column mapper aligns GA4 or BigQuery export field names to each platform's event fields, so a schema built for analytics still feeds ad platforms without a separate transform step.
- Custom audiences
- Identifiers are SHA-256 hashed while the export is read, and the file is dropped after processing, so a GA4 or BigQuery export reaches the platforms with no plaintext leaving the pipeline.
- Lead generation inbound
- Every row comes back with a per-destination status, so a malformed record from an export job is flagged and quarantined instead of failing the whole file.
Pick your platform. Every use case for it, in one place.
Every way GCS data moves, grouped by platform and ranked by how many use cases GCS supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - 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 Cloud Storage with scoped, read-only access.
-
Watch
Choose the bucket and file pattern to watch.
-
Map
Map GA4 or BigQuery export columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
GCS questions, answered.
Which file formats are supported?
Delimited files such as CSV and TSV with configurable headers are the common case, including the exports BigQuery writes to a GCS bucket on a schedule. Point Signals at the bucket and file pattern, and any object matching it is parsed on arrival, so a scheduled BigQuery export needs no other change to feed the platforms.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, with the source file discarded once processed, whether it originated from GA4, BigQuery, or another export job. A self-hosted Core deployment is available when data cannot leave your own environment, with hashing happening there before delivery.
How does this pair with GA4 or BigQuery exports?
GA4 and BigQuery can both write scheduled exports into a GCS bucket, and Signals watches that bucket the same way it watches any other file source. A daily BigQuery export lands, gets parsed and hashed, and is routed to every connected platform without a custom pipeline built around the export schema.
NEXT STEP
See your GCS data working in every ad platform.
Ready to enable a use case, or still mapping what GCS data could do? Our team helps you find the right place to start.
