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

    CONNECTIONS / PostgreSQL / PostgreSQL to TikTok Offline eAPI

    Your PostgreSQL tables, wired to TikTok's Offline Events API.

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

    postgresql -> tiktok-offline-eapi :: live

    1. ● postgresql → tiktok.eapi :: live
    2. > read closed_deals rows=12,543
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 10,536 matched

    WHAT THIS ENABLES

    PostgreSQL to TikTok Offline Events API

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

    The click, the conversion, and the credit.

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

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

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

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What Offline eAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from PostgreSQL

    PostgreSQL to Google OCI

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

    Learn more

    from PostgreSQL

    PostgreSQL to Google Store Sales

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

    Delivery tracks PostgreSQL, run by engineering teams running PostgreSQL: a near-real-time or scheduled sync of your PostgreSQL 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 PostgreSQL-sourced TikTok Offline eAPI batch expect?

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

    NEXT STEP

    PostgreSQL to TikTok Offline eAPI, in production this week.

    Talk to our team All PostgreSQL use cases