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

    CONNECTIONS / Server-side GTM / Server-side GTM to X CAPI

    Server-side GTM events into X, built for the X Conversions API.

    Connect Server-side GTM and point Signals at your server-side GTM events; it reports online sales to X server-side so campaigns keep measuring conversions as each event fires, hashed and consent-checked for X.

    Talk to our team Explore the setup

    sgtm -> x-capi :: live

    1. ● server-side gtm → x.capi :: live
    2. > read web_orders rows=72,520
    3. hash sha256(email,phone) consent=filtered
    4. route x deliver
    5. ✓ delivered · 62,367 matched

    WHAT THIS ENABLES

    Server-side GTM to X Conversions API

    Server-side GTM to X Conversions API: your server-side GTM events, hashed and consent-checked, feed X as Signals reports online sales to X server-side so campaigns keep measuring conversions as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for X, as Signals reports online sales to X server-side so campaigns keep measuring conversions.
    • X conversions that persist after the browser signal fades, drawn from your server-side GTM events by teams running server-side GTM.

    WHAT FLOWS WHERE

    Server-side GTM to X CAPI, mapped.

    Signals receives the on-site purchase and checkout events from your server-side GTM events; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.

    Signals receives the on-site purchase and checkout events from your server-side GTM events; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers keeping X conversion measurement alive post-cookie, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating the X Conversions 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 X's Conversions API, sized for hashed-email matching.

    2. Map

      Signals receives your server-side GTM events, and its columns map to X's Conversions API in the visual mapper, hashed and checked for hashed-email matching.

    3. Deliver

      On each run, Signals pulls your server-side GTM events, reports online sales to X server-side so campaigns keep measuring conversions, and forwards each event as it arrives, with hashed-email matching in the debugger.

    WHAT YOU GET

    What ships with this use case.

    X conversions that persist after the browser signal fades on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Online sales still counted on X from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from X's Conversions API on hashed-email matching, straight out of your server-side GTM events.

    ON THE WIRE

    What X CAPI actually receives.

    signals :: sgtm.x-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversion source=sgtm.web_orders
    3. conversion_time 1784384609000
    4. identifiers [{ hashed_email: "9c04ef…" }]
    5. conversion_value 2304.00 · conversion_currency USD
    6. ✓ accepted · match=true
    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 X CAPI

    X Conversions API for BigCommerce: Signals reports online sales to X server-side so…

    Learn more

    generic

    X CAPI

    Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM X CAPI 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 X on that cadence. Each run forwards each event as it arrives, so online sales still counted on X holds up on hashed-email matching. The live debugger confirms every delivery inline.

    What match rate should a Server-side GTM-sourced X CAPI 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 X; one missing both cannot. First-run feedback from Conversions API pinpoints hashed-email matching, the number teams running server-side GTM tune against.

    NEXT STEP

    Server-side GTM to X CAPI, in production this week.

    Talk to our team All Server-side GTM use cases