Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Backblaze B2 / Backblaze B2 to Meta Offline CAPI

    From Backblaze B2 files to Meta's offline optimization.

    Connect Backblaze B2 and point Signals at your Backblaze B2 files; it credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    backblaze -> meta-offline-capi :: live

    1. ● backblaze b2 → meta.capi :: live
    2. > read closed_deals rows=34,128
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 26,620 matched

    WHAT THIS ENABLES

    Backblaze B2 to Meta Offline CAPI

    Backblaze B2 to Meta Offline CAPI: your Backblaze B2 files, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands.

    • Offline and in-store sales from your Backblaze B2 files activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your Backblaze B2 files by teams archiving exports to Backblaze B2.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Meta, away from any pixel. Here is how Backblaze B2 closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta File drop sync recorded in Backblaze B2 S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Backblaze B2 buckets and object prefixes.

    Teams archiving exports to Backblaze B2 activating Meta's offline optimization straight from Backblaze B2 files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only application key scoped to the Backblaze B2 bucket you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals picks up your Backblaze B2 files, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Backblaze B2 files, credits dealer, branch, and phone sales to the Meta campaigns behind them, and processes only the newly dropped file, with Meta's 62-day event window in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Backblaze B2 records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: backblaze.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=backblaze.closed_deals
    3. event_name "Purchase" · event_time 2026-07-18T09:37:28
    4. value 27619.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-91448"
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Backblaze B2

    Backblaze B2 to Google OCI

    Backblaze B2 to Google Offline Conversions: your Backblaze B2 files, hashed and…

    Learn more

    from Backblaze B2

    Backblaze B2 to Google Store Sales

    Backblaze B2 to Google Store Sales: your Backblaze B2 files, hashed and consent-checked,…

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Backblaze B2 Meta Offline CAPI sync run?

    The pace follows your Backblaze B2 files: Signals sends changes from Backblaze B2 to Meta each time a new file lands. Because it processes only the newly dropped file, in-store and phone revenue joining Meta's optimization loop stays current while teams archiving exports to Backblaze B2 keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

    What match rate should a Backblaze B2-sourced Meta Offline CAPI batch expect?

    Coverage of hashed identifiers across your Backblaze B2 files decides it, and teams archiving exports to Backblaze B2 own that inside Backblaze B2. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which teams archiving exports to Backblaze B2 then raise inside your Backblaze B2 files.

    NEXT STEP

    Backblaze B2 to Meta Offline CAPI, in production this week.

    Talk to our team All Backblaze B2 use cases