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

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

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

    Connect Server-side GTM and point Signals at your server-side GTM events; it sends every browser checkout to Meta server-side so the pixel gap closes as each event fires, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    sgtm -> meta-web-capi :: live

    1. ● server-side gtm → meta.capi :: live
    2. > read web_orders rows=63,184
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 46,756 matched

    WHAT THIS ENABLES

    Server-side GTM to Meta Conversions API

    Server-side GTM to Meta Conversions API: your server-side GTM events, hashed and consent-checked, feed Meta as Signals sends every browser checkout to Meta server-side so the pixel gap closes as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for Meta, as Signals sends every browser checkout to Meta server-side so the pixel gap closes.
    • Purchase events that survive ad blockers and Safari cookie limits, 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 Meta's Conversions API accepts the web conversions for browser-to-server deduplication.

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

    WHO THIS IS FOR

    Built for the teams that own the number.

    Online stores losing pixel coverage to browser privacy controls, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating Meta'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 Meta's Conversions API, sized for browser-to-server deduplication.

    2. Map

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

    3. Deliver

      On each run, Signals pulls your server-side GTM events, sends every browser checkout to Meta server-side so the pixel gap closes, and forwards each event as it arrives, with browser-to-server deduplication in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Purchase events that survive ad blockers and Safari cookie limits on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Browser purchases Meta can still optimize on from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from Meta's Conversions API on browser-to-server deduplication, straight out of your server-side GTM events.

    ON THE WIRE

    What Web CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /events source=sgtm.web_orders
    3. event_name "Purchase" · event_time 1784524241
    4. em sha256 "5f3a92…" · ph sha256 "a107cd…"
    5. value 3188.00 · currency USD
    6. ✓ accepted match=74%
    RELATED USE CASES

    Adjacent moves on the same stack.

    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

    from Server-side GTM

    Server-side GTM to Google EC Web

    Server-side GTM to Google Enhanced Conversions: your server-side GTM events, hashed and…

    Learn more

    same use case

    BigCommerce to Meta CAPI

    Meta Conversions API for BigCommerce: Signals sends every browser checkout to Meta…

    Learn more

    generic

    Meta Web CAPI

    Datahash is a Meta Business Partner. We set up Meta Conversions API on your website…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM Meta 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 Meta on that cadence. Each run forwards each event as it arrives, so browser purchases Meta can still optimize on holds up on browser-to-server deduplication. The live debugger confirms every delivery inline.

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

    NEXT STEP

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

    Talk to our team All Server-side GTM use cases