CONNECTIONS / AWS S3
AWS S3 + Datahash: files in your bucket become ad signals.
Conversion and CRM exports land in your S3 bucket as CSV and similar files. Signals reads each file as it arrives, hashes the identifiers, routes the rows to Meta, Google, TikTok, and Snap, then discards the file.
- ● aws-s3 :: signals live
- > object arrived s3://exports/orders/2026-07-18.csv
- > parse rows=51,204 schema=orders
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 80%
The signal AWS S3 yields, and receives.
Every kind of signal that moves between AWS S3 and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Each file that lands in the watched prefix is picked up on schedule and parsed, so an export written by a nightly job becomes events without anyone moving it again.
- Lead conversions
- The column mapper aligns whatever headers your file uses to each platform's event fields, so a layout change on your side does not break the feed.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed as the file is read, and the file itself is discarded after processing, so no raw export lingers on our side.
- Lead generation inbound
- Every row comes back with a per-destination status, so a malformed record is flagged and quarantined instead of failing the whole file.
Pick your platform. Every use case for it, in one place.
Every way AWS S3 data moves, grouped by platform and ranked by how many use cases AWS S3 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 AWS S3 with scoped, read-only access.
-
Watch
Choose the bucket prefix and file pattern to watch.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
AWS S3 questions, answered.
Which file formats are supported?
Delimited files such as CSV and TSV with configurable headers are the common case, and fixed-width layouts can be handled through the column mapper. You point Signals at a bucket prefix and file pattern, and any file matching it is parsed on arrival, so an export job that writes daily files 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, and the source file is discarded once processed. A self-hosted Core deployment is available when data cannot leave your perimeter, in which case the hashing happens inside your own environment before anything is delivered to a platform.
How often are files picked up?
On a schedule you choose, from every few minutes to daily batches, and each file is processed exactly once and reported row by row. A new object landing in the watched prefix triggers the next run, so the cadence follows however often your export job writes, whether that is hourly deltas or a single nightly file.
NEXT STEP
See your AWS S3 data working in every ad platform.
Ready to enable a use case, or still mapping what AWS S3 data could do? Our team helps you find the right place to start.
