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

    CONNECTIONS / MariaDB / MariaDB to TikTok Offline eAPI

    MariaDB tables into TikTok, built for TikTok's Offline Events API.

    Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB 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

    mariadb -> tiktok-offline-eapi :: live

    1. ● mariadb → tiktok.eapi :: live
    2. > read closed_deals rows=38,527
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 33,904 matched

    WHAT THIS ENABLES

    MariaDB to TikTok Offline Events API

    TikTok Offline Events API for MariaDB: Signals sends register and phone sales so offline joins TikTok's web optimization straight from your MariaDB 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 MariaDB tables each time the read runs.
    • A unified web-and-offline conversion view, with no export step out of your MariaDB tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Engineering teams running MariaDB who need counter sales deduped against any TikTok web event for the same buyer out of MariaDB tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What Offline eAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from MariaDB

    MariaDB to Google OCI

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

    Learn more

    from MariaDB

    MariaDB to Google Store Sales

    Google Store Sales for MariaDB: 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 MariaDB TikTok Offline eAPI sync run?

    You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into TikTok. Since Signals reads only the records changed since the last run, counter sales deduped against any TikTok web event for the same buyer keeps pace and engineering teams running MariaDB watch web-to-offline deduplication. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Offline Events API pinpoints web-to-offline deduplication, the number engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to TikTok Offline eAPI, in production this week.

    Talk to our team All MariaDB use cases