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

    CONNECTIONS / Wasabi / Wasabi to TikTok Offline eAPI

    Wasabi objects into TikTok, built for TikTok's Offline Events API.

    Connect Wasabi and point Signals at your Wasabi objects; 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

    wasabi -> tiktok-offline-eapi :: live

    1. ● wasabi → tiktok.eapi :: live
    2. > read closed_deals rows=14,234
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 11,814 matched

    WHAT THIS ENABLES

    Wasabi to TikTok Offline Events API

    Wasabi to TikTok Offline Events API: your Wasabi objects, 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 Wasabi objects 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 Wasabi objects by teams archiving to Wasabi.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok File drop sync recorded in Wasabi 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 Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating TikTok's Offline Events API straight from Wasabi objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only key scoped to the Wasabi bucket you name to feed TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      Signals picks up your Wasabi objects, 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 Wasabi objects, 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 Wasabi records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Wasabi

    Wasabi to Google OCI

    Wasabi to Google Offline Conversions: your Wasabi objects, hashed and consent-checked, feed…

    Learn more

    from Wasabi

    Wasabi to Google Store Sales

    Wasabi to Google Store Sales: your Wasabi objects, hashed and consent-checked, feed Google…

    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 Wasabi TikTok Offline eAPI sync run?

    Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds TikTok on that cadence. Each run processes only the newly dropped file, so a unified web-and-offline conversion view holds up on web-to-offline deduplication. The live debugger confirms every delivery inline.

    What match rate should a Wasabi-sourced TikTok Offline eAPI batch expect?

    Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Offline Events API pinpoints web-to-offline deduplication, the number teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to TikTok Offline eAPI, in production this week.

    Talk to our team All Wasabi use cases