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

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

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

    Connect Server-side GTM and point Signals at your server-side GTM events; it reports online orders to LinkedIn so B2B revenue counts against the campaign as each event fires, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    sgtm -> linkedin-capi :: live

    1. ● server-side gtm → linkedin.capi :: live
    2. > read web_orders rows=39,152
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 32,888 matched

    WHAT THIS ENABLES

    Server-side GTM to LinkedIn Conversions API

    Server-side GTM to LinkedIn Conversions API: your server-side GTM events, hashed and consent-checked, feed LinkedIn as Signals reports online orders to LinkedIn so B2B revenue counts against the campaign as each event fires.

    • On-site purchase and checkout events from your server-side GTM events activated for LinkedIn, as Signals reports online orders to LinkedIn so B2B revenue counts against the campaign.
    • B2B web orders attributed to the LinkedIn campaign that drove them, drawn from your server-side GTM events by teams running server-side GTM.

    WHAT FLOWS WHERE

    Server-side GTM to LinkedIn 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 LinkedIn's Conversions API accepts the web conversions for long B2B consideration windows.

    Signals receives the on-site purchase and checkout events from your server-side GTM events; Signals hashes and consent-screens each record before LinkedIn's Conversions API accepts the web conversions for long B2B consideration windows.

    WHO THIS IS FOR

    Built for the teams that own the number.

    B2B stores whose LinkedIn-sourced orders finish on the site, with the records already in server-side GTM tags and event streams.

    Teams running server-side GTM activating LinkedIn'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 LinkedIn's Conversions API, sized for long B2B consideration windows.

    2. Map

      Signals receives your server-side GTM events, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B consideration windows.

    3. Deliver

      On each run, Signals pulls your server-side GTM events, reports online orders to LinkedIn so B2B revenue counts against the campaign, and forwards each event as it arrives, with long B2B consideration windows in the debugger.

    WHAT YOU GET

    What ships with this use case.

    B2B web orders attributed to the LinkedIn campaign that drove them on every run, as Signals reads your server-side GTM events and forwards each event as it arrives.

    Online B2B orders counted inside LinkedIn from your server-side GTM events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from LinkedIn's Conversions API on long B2B consideration windows, straight out of your server-side GTM events.

    ON THE WIRE

    What LinkedIn CAPI actually receives.

    signals :: sgtm.linkedin-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=sgtm.web_orders
    3. conversion "urn:lla:llaPartnerConversion:50113"
    4. conversionHappenedAt 1784131113000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "c19ef0…" }]
    6. ✓ accepted · conversionValue 2757 USD
    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 LinkedIn CAPI

    LinkedIn Conversions API for BigCommerce: Signals reports online orders to LinkedIn so B2B…

    Learn more

    generic

    LinkedIn CAPI

    Datahash implements LinkedIn CAPI with hashed identifiers, deduplication, and CRM-driven…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Server-side GTM LinkedIn 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 LinkedIn on that cadence. Each run forwards each event as it arrives, so online B2B orders counted inside LinkedIn holds up on long B2B consideration windows. The live debugger confirms every delivery inline.

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

    NEXT STEP

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

    Talk to our team All Server-side GTM use cases