CONNECTIONS / Backblaze B2
Backblaze B2 + Datahash: archive exports become signals.
Backblaze B2 keeps your conversion exports and CRM backups at a fraction of typical cloud storage cost, with egress that will not spike your bill. Signals watches the bucket you already use for archiving, hashes each row as files land, and pushes matched events to your ad platforms.
- ● backblaze-b2 :: signals live
- > object arrived s3://dh-archive/crm-backups/2026-07-18.csv
- > parse rows=38,412 schema=customers
- hash sha256(email,phone)
- route meta · google · tiktok
- ✓ 3 destinations synced · match 76%
The signal Backblaze B2 yields, and receives.
Every kind of signal that moves between Backblaze B2 and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Backblaze B2's low egress cost means the watched bucket can be polled often without adding to your storage bill, so a nightly backup job feeds Signals the same day it runs.
- Lead conversions
- Archived exports rarely share one layout across years of backups, so the column mapper translates whatever header set a given file uses into the same event fields.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed as each file is read, and the object itself is discarded after processing, so nothing from the archive persists past that run.
- Lead generation inbound
- A malformed row in an older backup file is quarantined and reported individually, so one bad record does not block the rest of that day's file.
Pick your platform. Every use case for it, in one place.
Every way Backblaze B2 data moves, grouped by platform and ranked by how many use cases Backblaze B2 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 Backblaze B2 with a scoped, read-only application key.
-
Watch
Choose the bucket and file pattern to watch for new exports.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
Backblaze B2 questions, answered.
Which file formats are supported?
Delimited files such as CSV and TSV with configurable headers cover most exports, and fixed-width layouts can be handled through the column mapper. Point Signals at a bucket and file pattern, and any matching object is parsed on arrival, so a backup job writing daily archives needs no other integration work.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud. The B2 object is discarded once processed, so nothing from the archive persists on our side. A self-hosted Core deployment is available when data cannot leave your own infrastructure at all.
Why use Backblaze B2 instead of pulling files less often?
Backblaze's egress pricing makes frequent pulls inexpensive, so there is little reason to batch exports into large, infrequent files. Signals can watch the bucket on a tighter schedule, meaning fresher conversion data reaches Meta, Google, and other platforms without the storage or bandwidth cost concerns typical of other providers.
NEXT STEP
See your Backblaze B2 data working in every ad platform.
Ready to enable a use case, or still mapping what Backblaze B2 data could do? Our team helps you find the right place to start.
