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

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

    Server-side GTM events into Snapchat, built for Snapchat's web Conversions API.

    Connect Server-side GTM and point Signals at your server-side GTM events; it posts checkout purchases to Snapchat server-side alongside the pixel as each event fires, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    sgtm -> snap-web-capi :: live

    1. ● server-side gtm → snap.capi :: live
    2. > read web_orders rows=65,577
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 55,740 matched

    WHAT THIS ENABLES

    Server-side GTM to Snap Conversions API

    Server-side GTM to Snap Conversions API: your server-side GTM events, hashed and consent-checked, feed Snapchat as Signals posts checkout purchases to Snapchat server-side alongside the pixel as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for Snapchat, as Signals posts checkout purchases to Snapchat server-side alongside the pixel.
    • Web conversions Snapchat can optimize on without pixel-only gaps, drawn from your server-side GTM events by teams running server-side GTM.

    WHAT FLOWS WHERE

    Server-side GTM to Web 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 Snapchat's Conversions API accepts the web conversions for server-and-pixel deduplication.

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

    WHO THIS IS FOR

    Built for the teams that own the number.

    Snapchat advertisers whose store conversions slip past the pixel, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating Snapchat's web 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 Snapchat's Conversions API, sized for server-and-pixel deduplication.

    2. Map

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

    3. Deliver

      On each run, Signals pulls your server-side GTM events, posts checkout purchases to Snapchat server-side alongside the pixel, and forwards each event as it arrives, with server-and-pixel deduplication in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Web conversions Snapchat can optimize on without pixel-only gaps on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Checkout purchases counted server-side on Snap from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from Snapchat's Conversions API on server-and-pixel deduplication, straight out of your server-side GTM events.

    ON THE WIRE

    What Web CAPI actually receives.

    signals :: sgtm.snap-web-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=sgtm.web_orders
    3. event_type "PURCHASE" · timestamp 1784275726
    4. hashed_email "2ac910…" · hashed_phone_number "e04b7f…"
    5. price 1983.00 · currency GBP
    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 Snap CAPI

    Snap Conversions API for BigCommerce: Signals posts checkout purchases to Snapchat…

    Learn more

    generic

    Snap Web CAPI

    Datahash is a Snapchat Marketing Partner. We deliver Snap CAPI for web, deduped with the…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM Snap 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 Snapchat on that cadence. Each run forwards each event as it arrives, so checkout purchases counted server-side on Snap holds up on server-and-pixel deduplication. The live debugger confirms every delivery inline.

    What match rate should a Server-side GTM-sourced Snap 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 Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints server-and-pixel deduplication, the number teams running server-side GTM tune against.

    NEXT STEP

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

    Talk to our team All Server-side GTM use cases