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

    CONNECTIONS / Cockroach / Cockroach to TikTok Offline eAPI

    From Cockroach tables to TikTok's Offline Events API.

    Connect Cockroach and point Signals at your Cockroach tables; it sends register and phone sales so offline joins TikTok's web optimization each time the read runs, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    cockroach -> tiktok-offline-eapi :: live

    1. ● cockroach → tiktok.eapi :: live
    2. > read closed_deals rows=34,302
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 27,785 matched

    WHAT THIS ENABLES

    Cockroach to TikTok Offline Events API

    TikTok Offline Events API for Cockroach: Signals sends register and phone sales so offline joins TikTok's web optimization straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Offline and in-store sales from your Cockroach tables 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 Cockroach tables by platform teams running CockroachDB.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok Scheduled read sync recorded in Cockroach 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 Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating TikTok's Offline Events API straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      A scheduled read pulls your Cockroach tables, 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 Cockroach tables, sends register and phone sales so offline joins TikTok's web optimization, and reads only the records changed since the last run, 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 Cockroach records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google OCI

    Google Offline Conversions for Cockroach: Signals reconciles closed-won revenue to the…

    Learn more

    from Cockroach

    Cockroach to Google Store Sales

    Google Store Sales for Cockroach: Signals matches in-person transactions to Google accounts…

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

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to TikTok each time the read runs. Because it reads only the records changed since the last run, counter sales deduped against any TikTok web event for the same buyer stays current while platform teams running CockroachDB keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Cockroach to TikTok Offline eAPI, in production this week.

    Talk to our team All Cockroach use cases