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

    CONNECTIONS / Attio / Attio to LinkedIn Offline CAPI

    Your Attio workspace lists, wired to LinkedIn account-revenue reporting.

    Connect Attio and point Signals at your Attio workspace lists; 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

    attio -> linkedin-offline-capi :: live

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

    WHAT THIS ENABLES

    Attio to LinkedIn Offline CAPI

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

    • Offline and in-store sales from your Attio workspace lists 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 Attio workspace lists by RevOps teams running Attio.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn CRM record sync recorded in Attio 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 Attio records, lists, and workspace objects.

    RevOps teams running Attio activating LinkedIn account-revenue reporting straight from Attio workspace lists.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Attio, reading only your Attio workspace lists to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals reads your Attio workspace lists, 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 Attio workspace lists, 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 Attio records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Attio

    Attio to Google OCI

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

    Learn more

    from Attio

    Attio to Google Store Sales

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

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

    The pace follows your Attio workspace lists: Signals sends changes from Attio to LinkedIn as records change. Because it sends only the records that changed, pipeline revenue tied to the LinkedIn campaigns that sourced it stays current while RevOps teams running Attio keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Attio to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Attio use cases