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

    CONNECTIONS / Backblaze B2 / Backblaze B2 to TikTok Offline eAPI

    From Backblaze B2 files to TikTok's Offline Events API.

    Connect Backblaze B2 and point Signals at your Backblaze B2 files; it sends register and phone sales so offline joins TikTok's web optimization each time a new file lands, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    backblaze -> tiktok-offline-eapi :: live

    1. ● backblaze b2 → tiktok.eapi :: live
    2. > read closed_deals rows=23,404
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 19,893 matched

    WHAT THIS ENABLES

    Backblaze B2 to TikTok Offline Events API

    Backblaze B2 to TikTok Offline Events API: your Backblaze B2 files, hashed and consent-checked, feed TikTok as Signals sends register and phone sales so offline joins TikTok's web optimization each time a new file lands.

    • Offline and in-store sales from your Backblaze B2 files activated for TikTok, as Signals sends register and phone sales so offline joins TikTok's web optimization.
    • Counter sales deduped against any TikTok web event for the same buyer, 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 TikTok, away from any pixel. Here is how Backblaze B2 closes the loop.

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

    Built for the teams that own the number.

    Brands whose TikTok conversions finish at a till, not a checkout, with the records already in Backblaze B2 buckets and object prefixes.

    Teams archiving exports to Backblaze B2 activating TikTok's Offline Events API 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 TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      Signals picks up your Backblaze B2 files, and its columns map to TikTok's Offline Events API in the visual mapper, hashed and checked for web-to-offline deduplication.

    3. Deliver

      On each run, Signals pulls your Backblaze B2 files, sends register and phone sales so offline joins TikTok's web optimization, and processes only the newly dropped file, with web-to-offline deduplication 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 eAPI 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 eAPI actually receives.

    signals :: backblaze.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=backblaze.closed_deals
    3. event "CompletePayment" · event_time 1784497139
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 43042 · properties.currency SAR
    6. ✓ accepted · dedupe=event_id
    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 TikTok Offline eAPI

    ActiveCampaign to TikTok Offline Events API: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    TikTok Offline eAPI

    Move your in-store and call-centre conversions to TikTok server-side, so TikTok can…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Backblaze B2 TikTok Offline eAPI sync run?

    The pace follows your Backblaze B2 files: Signals sends changes from Backblaze B2 to TikTok each time a new file lands. Because it processes only the newly dropped file, counter sales deduped against any TikTok web event for the same buyer stays current while teams archiving exports to Backblaze B2 keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

    What match rate should a Backblaze B2-sourced TikTok Offline eAPI 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 TikTok; neither, and it will not. First-run feedback flags web-to-offline deduplication, which teams archiving exports to Backblaze B2 then raise inside your Backblaze B2 files.

    NEXT STEP

    Backblaze B2 to TikTok Offline eAPI, in production this week.

    Talk to our team All Backblaze B2 use cases