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

    CONNECTIONS / Datahash API / Datahash API to TikTok Offline eAPI

    Post offline and in-store sales to the Datahash API, wired to TikTok's Offline Events API.

    Send offline and in-store sales to one documented REST endpoint from any backend, in any language; Signals sends register and phone sales so offline joins TikTok's web optimization, hashed and consent-checked, with no pixel and no warehouse read.

    Talk to our team Explore the setup

    datahash-api -> tiktok-offline-eapi :: live

    1. ● datahash-api → tiktok.eapi :: live
    2. > POST /v1/events source=api.purchase_events count=51,808
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ 202 accepted · 40,928 forwarded

    WHAT THIS ENABLES

    Datahash API to TikTok Offline Events API

    Datahash API to TikTok Offline Events API: post your offline and in-store sales to one REST endpoint and Signals sends register and phone sales so offline joins TikTok's web optimization, hashed and consent-checked server-side before TikTok sees it.

    • Signals sends register and phone sales so offline joins TikTok's web optimization, from events your backend posts server-side.
    • Counter sales deduped against any TikTok web event for the same buyer, without a pixel, a connector, or a nightly export.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off TikTok, away from any pixel. Here is how Datahash API closes the loop.

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok REST event recorded in Datahash API 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, whose engineers would rather POST an event than maintain a connector.

    Backend and platform teams driving TikTok's Offline Events API by sending offline and in-store sales straight from their own stack.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Create an API key in the Signals console and point your backend at the endpoint that feeds TikTok's Offline Events API.

    2. Map

      Map your event payload to TikTok's Offline Events API fields once; per-request validation flags bad events instead of dropping the batch.

    3. Deliver

      Post events as they happen and Signals sends register and phone sales so offline joins TikTok's web optimization, hashing server-side, with web-to-offline deduplication shown 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 Datahash API records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

    signals :: datahash-api.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=api.purchase_events
    3. event "CompletePayment" · event_time 1784277353
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 42069 · properties.currency USD
    6. ✓ accepted · dedupe=event_id
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Datahash API

    Datahash API to Google OCI

    Datahash API to Google Offline Conversions: post your offline and in-store sales to one…

    Learn more

    from Datahash API

    Datahash API to Google Store Sales

    Datahash API to Google Store Sales: post your offline and in-store sales to one REST…

    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.

    Which backends can send to TikTok Offline eAPI through the Datahash API?

    Any backend that can make an HTTPS request. You POST offline and in-store sales as JSON to one documented endpoint and Signals forwards the offline conversions to TikTok's Offline Events API; identifiers are hashed at ingestion or sent pre-hashed, and brands whose TikTok conversions finish at a till, not a checkout track web-to-offline deduplication in the debugger.

    How fresh are TikTok Offline eAPI events sent over the API?

    As fresh as you post them. The API accepts events in near real time, so counter sales deduped against any TikTok web event for the same buyer reaches TikTok moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps web-to-offline deduplication current for the teams driving TikTok's Offline Events API.

    NEXT STEP

    Datahash API to TikTok Offline eAPI, in production this week.

    Talk to our team All Datahash API use cases