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

    CONNECTIONS / Insightly / Insightly to LinkedIn Offline CAPI

    From Insightly opportunities and pipeline stages to LinkedIn account-revenue reporting.

    Connect Insightly and point Signals at your Insightly opportunities and pipeline stages; 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

    insightly -> linkedin-offline-capi :: live

    1. ● insightly → linkedin.capi :: live
    2. > read closed_deals rows=28,983
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 23,476 matched

    WHAT THIS ENABLES

    Insightly to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for Insightly: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your Insightly opportunities and pipeline stages, hashed and consent-screened as records change.

    • Offline and in-store sales from your Insightly opportunities and pipeline stages 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 Insightly opportunities and pipeline stages by RevOps teams running Insightly.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn CRM record sync recorded in Insightly 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 Insightly opportunities, projects, and pipeline stages.

    RevOps teams running Insightly activating LinkedIn account-revenue reporting straight from Insightly opportunities and pipeline stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Insightly, reading only your Insightly opportunities and pipeline stages to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals reads your Insightly opportunities and pipeline stages, 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 Insightly opportunities and pipeline stages, 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 Insightly records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Insightly

    Insightly to Google OCI

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

    Learn more

    from Insightly

    Insightly to Google Store Sales

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

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

    Delivery tracks Insightly, run by RevOps teams running Insightly: a near-real-time or scheduled sync of your Insightly opportunities and pipeline stages 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 Insightly-sourced LinkedIn Offline CAPI batch expect?

    Match rate follows identifier coverage in your Insightly opportunities and pipeline stages, which RevOps teams running Insightly control, not Insightly 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 RevOps teams running Insightly tune against.

    NEXT STEP

    Insightly to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Insightly use cases