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

    CONNECTIONS / IBM DB2 / IBM DB2 to TikTok Offline eAPI

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

    Connect IBM DB2 and point Signals at your Db2 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

    ibm-db2 -> tiktok-offline-eapi :: live

    1. ● ibm db2 → tiktok.eapi :: live
    2. > read closed_deals rows=53,436
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 46,489 matched

    WHAT THIS ENABLES

    IBM DB2 to TikTok Offline Events API

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

    • Offline and in-store sales from your Db2 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 Db2 tables by enterprise data teams on IBM DB2.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Enterprise data teams on IBM DB2 activating TikTok's Offline Events API straight from Db2 tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      A scheduled read pulls your Db2 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 Db2 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 IBM DB2 records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

    signals :: ibm-db2.tiktok-offline-eapi :: wire

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

    Adjacent moves on the same stack.

    from IBM DB2

    IBM DB2 to Google OCI

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

    Learn more

    from IBM DB2

    IBM DB2 to Google Store Sales

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

    The pace follows your Db2 tables: Signals sends changes from IBM DB2 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 enterprise data teams on IBM DB2 keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    IBM DB2 to TikTok Offline eAPI, in production this week.

    Talk to our team All IBM DB2 use cases