Jump to a popular page, or start typing.

    CONNECTIONS / MySQL / MySQL to TikTok Offline eAPI

    From MySQL tables to TikTok's Offline Events API.

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

    mysql -> tiktok-offline-eapi :: live

    1. ● mysql → tiktok.eapi :: live
    2. > read closed_deals rows=51,438
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 40,122 matched

    WHAT THIS ENABLES

    MySQL to TikTok Offline Events API

    MySQL to TikTok Offline Events API: Signals reads your MySQL tables and sends register and phone sales so offline joins TikTok's web optimization, hashed and consent-checked each time the read runs.

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

    The click, the conversion, and the credit.

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

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

    Application teams on MySQL who need counter sales deduped against any TikTok web event for the same buyer out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Columns from your MySQL 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 MySQL 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 MySQL records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

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

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

    Asked on almost every call.

    How often does the MySQL TikTok Offline eAPI sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds TikTok on that cadence. Each run reads only the records changed since the last run, so a unified web-and-offline conversion view holds up on web-to-offline deduplication. The live debugger confirms every delivery inline.

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

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

    NEXT STEP

    MySQL to TikTok Offline eAPI, in production this week.