Jump to a popular page, or start typing.

    CONNECTIONS / GCS / GCS to TikTok Offline eAPI

    Your GCS objects, wired to TikTok's Offline Events API.

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

    google-cloud-storage -> tiktok-offline-eapi :: live

    1. ● gcs → tiktok.eapi :: live
    2. > read closed_deals rows=65,705
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 58,477 matched

    WHAT THIS ENABLES

    GCS to TikTok Offline Events API

    GCS to TikTok Offline Events API: your GCS 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 GCS 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 GCS objects by data teams landing exports in GCS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Data teams landing exports in GCS activating TikTok's Offline Events API straight from GCS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What Offline eAPI actually receives.

    signals :: google-cloud-storage.tiktok-offline-eapi :: wire

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

    Asked on almost every call.

    How often does the GCS TikTok Offline eAPI sync run?

    The pace follows your GCS objects: Signals sends changes from GCS 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 data teams landing exports in GCS keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    GCS to TikTok Offline eAPI, in production this week.