Jump to a popular page, or start typing.

    CONNECTIONS / Tencent COS / Tencent COS to TikTok Offline eAPI

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

    Connect Tencent COS and point Signals at your Tencent COS 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.

    tencent -> tiktok-offline-eapi :: live

    1. ● tencent cos → tiktok.eapi :: live
    2. > read closed_deals rows=69,962
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 62,266 matched

    WHAT THIS ENABLES

    Tencent COS to TikTok Offline Events API

    TikTok Offline Events API for Tencent COS: Signals sends register and phone sales so offline joins TikTok's web optimization straight from your Tencent COS objects, hashed and consent-screened each time a new file lands.

    • Offline and in-store sales from your Tencent COS 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 Tencent COS objects by teams running Tencent Cloud COS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Teams running Tencent Cloud COS activating TikTok's Offline Events API straight from Tencent COS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Signals picks up your Tencent COS 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 Tencent COS 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 Tencent COS records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /event/track source=tencent.closed_deals
    3. event "CompletePayment" · event_time 1783942695
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 36924 · properties.currency SAR
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the Tencent COS TikTok Offline eAPI sync run?

    The pace follows your Tencent COS objects: Signals sends changes from Tencent COS 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 running Tencent Cloud COS keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Tencent COS objects decides it, and teams running Tencent Cloud COS own that inside Tencent COS. A live email or phone matches into TikTok; neither, and it will not. First-run feedback flags web-to-offline deduplication, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to TikTok Offline eAPI, in production this week.