CONNECTIONS / Wasabi
Wasabi + Datahash: hot storage becomes ad signals.
Conversion and CRM exports land in your Wasabi bucket, with no egress fees on the reads Signals performs. Signals reads each file as it arrives, hashes the identifiers, and routes the rows to every connected ad platform.
- ● wasabi :: signals live
- > object arrived wasabi://us-east-1/exports/purchases-2026-07-18.csv
- > parse rows=33,105 schema=purchases
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 81%
The signal Wasabi yields, and receives.
Every kind of signal that moves between Wasabi and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file that lands in the watched Wasabi bucket is picked up on schedule and parsed, and because Wasabi does not charge egress fees, Signals can poll more often without changing your storage bill.
- Lead conversions
- The column mapper aligns whatever headers your export uses to each platform's event fields, so a layout change on your side does not break the feed.
- Custom audiences
- Identifiers are SHA-256 hashed the moment Signals reads the file, and Wasabi keeps only the object you dropped, so no plaintext export sits in hot storage once processing finishes.
- Lead generation inbound
- Each row returns a per-destination status, so one malformed record is quarantined and reported rather than failing the batch you scheduled.
Pick your platform. Every use case for it, in one place.
Every way Wasabi data moves, grouped by platform and ranked by how many use cases Wasabi 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 Wasabi with scoped, read-only access.
-
Watch
Choose the bucket 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.
Wasabi questions, answered.
Which file formats are supported?
Signals supports CSV and TSV as the default delimited formats, with headers mapped through the visual mapper, and fixed-width files handled the same way through that mapper. Because polling a Wasabi bucket carries no egress penalty, a high-frequency export job writing several files an hour behaves the same as one that writes a single nightly file.
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. A self-hosted Core deployment is available when data cannot leave your own environment, in which case hashing happens there before anything reaches a platform.
Does frequent polling cost more with Wasabi?
No, because Wasabi charges a flat storage rate with no egress fees on the reads Signals performs. That makes a tighter polling schedule, down to every few minutes, a pricing-neutral choice rather than a tradeoff against your storage bill. Cadence is set to match how often your export job actually writes new files.
NEXT STEP
See your Wasabi data working in every ad platform.
Ready to enable a use case, or still mapping what Wasabi data could do? Our team helps you find the right place to start.
