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

    CONNECTIONS / Server-side GTM / Server-side GTM to TikTok Web eAPI

    Server-side GTM events into TikTok, built for TikTok's web Events API.

    Connect Server-side GTM and point Signals at your server-side GTM events; it sends checkout events to TikTok server-side, deduped against the pixel as each event fires, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    sgtm -> tiktok-web-eapi :: live

    1. ● server-side gtm → tiktok.eapi :: live
    2. > read web_orders rows=18,588
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 13,569 matched

    WHAT THIS ENABLES

    Server-side GTM to TikTok Events API

    Server-side GTM to TikTok Events API: your server-side GTM events, hashed and consent-checked, feed TikTok as Signals sends checkout events to TikTok server-side, deduped against the pixel as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for TikTok, as Signals sends checkout events to TikTok server-side, deduped against the pixel.
    • Purchase signal that holds up when the browser pixel drops, drawn from your server-side GTM events by teams running server-side GTM.

    WHAT FLOWS WHERE

    Server-side GTM to Web eAPI, mapped.

    Signals receives the on-site purchase and checkout events from your server-side GTM events; Signals hashes and consent-screens each record before TikTok's Events API accepts the web conversions for event_id deduplication.

    Signals receives the on-site purchase and checkout events from your server-side GTM events; Signals hashes and consent-screens each record before TikTok's Events API accepts the web conversions for event_id deduplication.

    WHO THIS IS FOR

    Built for the teams that own the number.

    TikTok advertisers whose web conversions leak through the pixel, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating TikTok's web Events API straight from server-side GTM events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Signals tag in your server-side GTM container to feed TikTok's Events API, sized for event_id deduplication.

    2. Map

      Signals receives your server-side GTM events, and its columns map to TikTok's Events API in the visual mapper, hashed and checked for event_id deduplication.

    3. Deliver

      On each run, Signals pulls your server-side GTM events, sends checkout events to TikTok server-side, deduped against the pixel, and forwards each event as it arrives, with event_id deduplication in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Purchase signal that holds up when the browser pixel drops on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Server-side purchases deduped against the pixel from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from TikTok's Events API on event_id deduplication, straight out of your server-side GTM events.

    ON THE WIRE

    What Web eAPI actually receives.

    signals :: sgtm.tiktok-web-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=sgtm.web_orders
    3. event "CompletePayment" · event_time 1784279242
    4. user.email sha256 "64af2c…" · user.phone sha256 "0d93b7…"
    5. properties.value 3853.00 · properties.currency GBP
    6. ✓ accepted · dedupe=event_id
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Server-side GTM

    Server-side GTM to Meta CAPI

    Server-side GTM to Meta Conversions API: your server-side GTM events, hashed and…

    Learn more

    from Server-side GTM

    Server-side GTM to Meta CTM

    Server-side GTM to Meta Click-to-Message: your server-side GTM events, hashed and…

    Learn more

    same use case

    BigCommerce to TikTok Web eAPI

    TikTok Events API for BigCommerce: Signals sends checkout events to TikTok server-side,…

    Learn more

    generic

    TikTok Web eAPI

    Datahash is a TikTok Partner. We deliver server-side TikTok Events API with dedupe against…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM TikTok Web eAPI sync run?

    Delivery tracks Server-side GTM, run by teams running server-side GTM: a near-real-time or scheduled sync of your server-side GTM events feeds TikTok on that cadence. Each run forwards each event as it arrives, so server-side purchases deduped against the pixel holds up on event_id deduplication. The live debugger confirms every delivery inline.

    What match rate should a Server-side GTM-sourced TikTok Web eAPI batch expect?

    Match rate follows identifier coverage in your server-side GTM events, which teams running server-side GTM control, not Server-side GTM itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Events API pinpoints event_id deduplication, the number teams running server-side GTM tune against.

    NEXT STEP

    Server-side GTM to TikTok Web eAPI, in production this week.

    Talk to our team All Server-side GTM use cases