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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to LinkedIn CAPI

    Your Commerce Cloud orders, wired to LinkedIn's web Conversions API.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it reports online orders to LinkedIn so B2B revenue counts against the campaign as orders complete, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    sfcc -> linkedin-capi :: live

    1. ● commerce cloud → linkedin.capi :: live
    2. > read web_orders rows=47,857
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 38,286 matched

    WHAT THIS ENABLES

    Commerce Cloud to LinkedIn Conversions API

    Commerce Cloud to LinkedIn Conversions API: Signals reads your Commerce Cloud orders and reports online orders to LinkedIn so B2B revenue counts against the campaign, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your Commerce Cloud orders 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 Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to LinkedIn CAPI, mapped.

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

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; 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 Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating LinkedIn's web Conversions API straight from Commerce Cloud orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to Commerce Cloud, reading only your Commerce Cloud orders to feed LinkedIn's Conversions API, sized for long B2B consideration windows.

    2. Map

      Signals reads your Commerce Cloud orders, 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 Commerce Cloud orders, reports online orders to LinkedIn so B2B revenue counts against the campaign, and sends only the orders that changed, 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 Commerce Cloud orders and sends only the orders that changed.

    Online B2B orders counted inside LinkedIn from your Commerce Cloud orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from LinkedIn's Conversions API on long B2B consideration windows, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What LinkedIn CAPI actually receives.

    signals :: sfcc.linkedin-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=sfcc.web_orders
    3. conversion "urn:lla:llaPartnerConversion:95715"
    4. conversionHappenedAt 1784461715000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "c19ef0…" }]
    6. ✓ accepted · conversionValue 2832 USD
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta CAPI

    Commerce Cloud to Meta Conversions API: Signals reads your Commerce Cloud orders and sends…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta CTM

    Commerce Cloud to Meta Click-to-Message: Signals reads your Commerce Cloud orders 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 Commerce Cloud LinkedIn CAPI sync run?

    The pace follows your Commerce Cloud orders: Signals sends changes from Commerce Cloud to LinkedIn as orders complete. Because it sends only the orders that changed, B2B web orders attributed to the LinkedIn campaign that drove them stays current while enterprise retailers on Salesforce Commerce Cloud keep long B2B consideration windows in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced LinkedIn CAPI batch expect?

    Coverage of hashed identifiers across your Commerce Cloud orders decides it, and enterprise retailers on Salesforce Commerce Cloud own that inside Commerce Cloud. A live email or phone matches into LinkedIn; neither, and it will not. First-run feedback flags long B2B consideration windows, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to LinkedIn CAPI, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases