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

    CONNECTIONS / Databricks / Databricks to TikTok Offline eAPI

    Your Databricks lakehouse, wired to TikTok's Offline Events API.

    Signals reads the Delta table through a Unity Catalog grant and sends register and phone sales so offline joins TikTok's web optimization, hashed on the way out and governed like any other lakehouse job.

    Talk to our team Explore the setup

    databricks -> tiktok-offline-eapi :: live

    1. ● databricks → tiktok.eapi :: live
    2. > read main.sales.pos_ledger rows=18,685
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 16,443 matched

    WHAT THIS ENABLES

    Databricks to TikTok Offline Events API

    Databricks to TikTok Offline Events API: A notebook job reads the offline and in-store sales in your Databricks Delta tables, and Signals sends register and phone sales so offline joins TikTok's web optimization, hashed and consent-checked each time the model rebuilds.

    • Signals sends register and phone sales so offline joins TikTok's web optimization, reading your Databricks Delta tables each time the model rebuilds.
    • Counter sales deduped against any TikTok web event for the same buyer, fed by data engineers modeling in Databricks notebooks.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok D Delta table sync recorded in Databricks 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 numbers already modeled in Databricks Delta tables governed by Unity Catalog.

    Data engineers modeling in Databricks notebooks who need counter sales deduped against any TikTok web event for the same buyer.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Unity Catalog-scoped service principal on the single Delta table in play to feed TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      A notebook job reads your Databricks Delta 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

      Each time the model rebuilds, Signals sends register and phone sales so offline joins TikTok's web optimization, reads only the rows the model rebuilt, 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 Databricks records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /event/track source=databricks.main.sales.pos_ledger
    3. event "CompletePayment" · event_time 1784520302
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 32937 · properties.currency GBP
    6. ✓ accepted · dedupe=event_id
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Databricks

    Databricks to Google OCI

    Databricks to Google Offline Conversions: A notebook job reads the offline and in-store…

    Learn more

    from Databricks

    Databricks to Google Store Sales

    Databricks to Google Store Sales: A notebook job reads the offline and in-store sales in…

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

    Cadence follows the job that rebuilds the table: a nightly model gives TikTok a nightly feed, an hourly one an hourly feed. Because a run picks up only the rows the model rebuilt, counter sales deduped against any TikTok web event for the same buyer keeps pace on web-to-offline deduplication and job-cluster time stays modest.

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

    Identifier quality in the Delta table drives it, not the cluster size. Rows carrying a live hashed email or phone land; rows with neither will not, and no rebuild changes that. The opening run's feedback from TikTok's Offline Events API flags the gap for brands whose TikTok conversions finish at a till, not a checkout tracking web-to-offline deduplication.

    NEXT STEP

    Databricks to TikTok Offline eAPI, in production this week.

    Talk to our team All Databricks use cases