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

    CONNECTIONS / BigCommerce / BigCommerce to LinkedIn Offline CAPI

    Your BigCommerce orders, wired to LinkedIn account-revenue reporting.

    Connect BigCommerce and point Signals at your BigCommerce orders; it reports closed B2B deals so LinkedIn optimizes on account revenue as orders complete, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    bigcommerce -> linkedin-offline-capi :: live

    1. ● bigcommerce → linkedin.capi :: live
    2. > read closed_deals rows=37,963
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 29,991 matched

    WHAT THIS ENABLES

    BigCommerce to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for BigCommerce: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your BigCommerce orders, hashed and consent-screened as orders complete.

    • Offline and in-store sales from your BigCommerce orders activated for LinkedIn, as Signals reports closed B2B deals so LinkedIn optimizes on account revenue.
    • Pipeline revenue tied to the LinkedIn campaigns that sourced it, drawn from your BigCommerce orders by merchants running BigCommerce.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off LinkedIn, away from any pixel. Here is how BigCommerce closes the loop.

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn B Order sync recorded in BigCommerce S Signals hash · dedupe Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    B2B teams whose deals close long after the impression, with the records already in BigCommerce orders, customers, and catalog.

    Merchants running BigCommerce activating LinkedIn account-revenue reporting straight from BigCommerce orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Signals reads your BigCommerce orders, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.

    3. Deliver

      On each run, Signals pulls your BigCommerce orders, reports closed B2B deals so LinkedIn optimizes on account revenue, and sends only the orders that changed, with long B2B attribution windows in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment BigCommerce records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: bigcommerce.linkedin-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=bigcommerce.closed_deals
    3. conversion "urn:lla:llaPartnerConversion:87449"
    4. conversionHappenedAt 1783968449000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
    6. ✓ accepted · conversionValue 45044 USD
    RELATED USE CASES

    Adjacent moves on the same stack.

    from BigCommerce

    BigCommerce to Google OCI

    Google Offline Conversions for BigCommerce: Signals reconciles closed-won revenue to the…

    Learn more

    from BigCommerce

    BigCommerce to Google Store Sales

    Google Store Sales for BigCommerce: Signals matches in-person transactions to Google…

    Learn more

    same use case

    ActiveCampaign to LinkedIn Offline CAPI

    ActiveCampaign to LinkedIn Offline CAPI: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    LinkedIn Offline CAPI

    Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the BigCommerce LinkedIn Offline CAPI sync run?

    The pace follows your BigCommerce orders: Signals sends changes from BigCommerce to LinkedIn as orders complete. Because it sends only the orders that changed, pipeline revenue tied to the LinkedIn campaigns that sourced it stays current while merchants running BigCommerce keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

    What match rate should a BigCommerce-sourced LinkedIn Offline CAPI batch expect?

    Coverage of hashed identifiers across your BigCommerce orders decides it, and merchants running BigCommerce own that inside BigCommerce. A live email or phone matches into LinkedIn; neither, and it will not. First-run feedback flags long B2B attribution windows, which merchants running BigCommerce then raise inside your BigCommerce orders.

    NEXT STEP

    BigCommerce to LinkedIn Offline CAPI, in production this week.

    Talk to our team All BigCommerce use cases