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

    CONNECTIONS / Clickhouse / ClickHouse to TikTok Offline eAPI

    From ClickHouse tables to TikTok's Offline Events API.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then sends register and phone sales so offline joins TikTok's web optimization so TikTok sees offline conversions without an export.

    Talk to our team Explore the setup

    clickhouse -> tiktok-offline-eapi :: live

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

    WHAT THIS ENABLES

    ClickHouse to TikTok Offline Events API

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

    • Signals sends register and phone sales so offline joins TikTok's web optimization, reading your ClickHouse tables each time the read runs.
    • A unified web-and-offline conversion view, with no export step out of your ClickHouse tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok Scheduled read sync recorded in Clickhouse 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, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need counter sales deduped against any TikTok web event for the same buyer out of ClickHouse tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the ClickHouse tables you name, mapped to TikTok's Offline Events API and tuned for web-to-offline deduplication.

    2. Map

      Columns from your ClickHouse tables align to TikTok's Offline Events API in the visual mapper, hashed as the read runs and checked for web-to-offline deduplication.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and sends register and phone sales so offline joins TikTok's web optimization, reads only the records changed since the last run, with web-to-offline deduplication watched 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 Clickhouse records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Google OCI

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

    Learn more

    from Clickhouse

    ClickHouse to Google Store Sales

    Google Store Sales for ClickHouse: Signals matches in-person transactions to 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 ClickHouse TikTok Offline eAPI sync run?

    The pace follows your ClickHouse tables: Signals sends changes from ClickHouse 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 analytics engineers on ClickHouse keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

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

    In ClickHouse, match rate tracks the email and phone quality your ClickHouse tables carry. Clean identifiers land for TikTok; blank ones never will. The first Offline Events API report shows analytics engineers on ClickHouse where web-to-offline deduplication needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to TikTok Offline eAPI, in production this week.

    Talk to our team All Clickhouse use cases