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

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

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

    Connect Server-side GTM and point Signals at your server-side GTM events; it credits store sales back to the Pinterest discovery that inspired them as each event fires, hashed and consent-checked for Pinterest.

    Talk to our team Explore the setup

    sgtm -> pinterest-capi :: live

    1. ● server-side gtm → pinterest.capi :: live
    2. > read web_orders rows=34,089
    3. hash sha256(email,phone) consent=filtered
    4. route pinterest deliver
    5. ✓ delivered · 27,953 matched

    WHAT THIS ENABLES

    Server-side GTM to Pinterest Conversions API

    Server-side GTM to Pinterest Conversions API: your server-side GTM events, hashed and consent-checked, feed Pinterest as Signals credits store sales back to the Pinterest discovery that inspired them as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for Pinterest, as Signals credits store sales back to the Pinterest discovery that inspired them.
    • Purchase signal linking Pinterest discovery to checkout, drawn from your server-side GTM events by teams running server-side GTM.

    WHAT FLOWS WHERE

    Server-side GTM to Pinterest 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 Pinterest's Conversions API accepts the web conversions for upper-funnel attribution.

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

    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands whose buyers discover on Pinterest and buy later, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating Pinterest's 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 Pinterest's Conversions API, sized for upper-funnel attribution.

    2. Map

      Signals receives your server-side GTM events, and its columns map to Pinterest's Conversions API in the visual mapper, hashed and checked for upper-funnel attribution.

    3. Deliver

      On each run, Signals pulls your server-side GTM events, credits store sales back to the Pinterest discovery that inspired them, and forwards each event as it arrives, with upper-funnel attribution in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Purchase signal linking Pinterest discovery to checkout on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Checkout sales tied to Pinterest discovery from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from Pinterest's Conversions API on upper-funnel attribution, straight out of your server-side GTM events.

    ON THE WIRE

    What Pinterest CAPI actually receives.

    signals :: sgtm.pinterest-capi :: wire

    1. ● signals :: event payload
    2. > POST /events source=sgtm.web_orders
    3. event_name "checkout" · action_source "web" · event_time 1783915795
    4. em sha256 "7bd403…"
    5. value 3324.00 · currency SAR
    6. ✓ accepted match=82%
    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 Pinterest CAPI

    Pinterest Conversions API for BigCommerce: Signals credits store sales back to the…

    Learn more

    generic

    Pinterest CAPI

    Datahash implements Pinterest Conversions API with dedupe against the Pinterest Tag and…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM Pinterest 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 Pinterest on that cadence. Each run forwards each event as it arrives, so checkout sales tied to Pinterest discovery holds up on upper-funnel attribution. The live debugger confirms every delivery inline.

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

    NEXT STEP

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

    Talk to our team All Server-side GTM use cases