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

    CONNECTIONS / Kommo / Kommo to LinkedIn Offline CAPI

    Your Kommo messenger pipelines, wired to LinkedIn account-revenue reporting.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it reports closed B2B deals so LinkedIn optimizes on account revenue as records change, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    kommo -> linkedin-offline-capi :: live

    1. ● kommo → linkedin.capi :: live
    2. > read closed_deals rows=73,124
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 60,693 matched

    WHAT THIS ENABLES

    Kommo to LinkedIn Offline CAPI

    Kommo to LinkedIn Offline CAPI: your Kommo messenger pipelines, hashed and consent-checked, feed LinkedIn as Signals reports closed B2B deals so LinkedIn optimizes on account revenue as records change.

    • Offline and in-store sales from your Kommo messenger pipelines 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 Kommo messenger pipelines by conversational-sales teams on Kommo.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn CRM record sync recorded in Kommo 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 Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating LinkedIn account-revenue reporting straight from Kommo messenger pipelines.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Kommo, reading only your Kommo messenger pipelines to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals reads your Kommo messenger pipelines, 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 Kommo messenger pipelines, reports closed B2B deals so LinkedIn optimizes on account revenue, and sends only the records 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 Kommo records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google OCI

    Kommo to Google Offline Conversions: your Kommo messenger pipelines, hashed and…

    Learn more

    from Kommo

    Kommo to Google Store Sales

    Kommo to Google Store Sales: your Kommo messenger pipelines, hashed and consent-checked,…

    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 Kommo LinkedIn Offline CAPI sync run?

    Delivery tracks Kommo, run by conversational-sales teams on Kommo: a near-real-time or scheduled sync of your Kommo messenger pipelines feeds LinkedIn on that cadence. Each run sends only the records that changed, so account revenue attached to the sourcing campaign holds up on long B2B attribution windows. The live debugger confirms every delivery inline.

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

    Match rate follows identifier coverage in your Kommo messenger pipelines, which conversational-sales teams on Kommo control, not Kommo 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 attribution windows, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Kommo use cases