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

    CONNECTIONS / Cockroach / Cockroach to LinkedIn Offline CAPI

    From Cockroach tables to LinkedIn account-revenue reporting.

    Connect Cockroach and point Signals at your Cockroach tables; it reports closed B2B deals so LinkedIn optimizes on account revenue each time the read runs, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    cockroach -> linkedin-offline-capi :: live

    1. ● cockroach → linkedin.capi :: live
    2. > read closed_deals rows=64,427
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 53,474 matched

    WHAT THIS ENABLES

    Cockroach to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for Cockroach: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Offline and in-store sales from your Cockroach tables 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 Cockroach tables by platform teams running CockroachDB.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn Scheduled read sync recorded in Cockroach 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 Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating LinkedIn account-revenue reporting straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      A scheduled read pulls your Cockroach tables, 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 Cockroach tables, reports closed B2B deals so LinkedIn optimizes on account revenue, and reads only the records changed since the last run, 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 Cockroach records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google OCI

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

    Learn more

    from Cockroach

    Cockroach to Google Store Sales

    Google Store Sales for Cockroach: 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 Cockroach LinkedIn Offline CAPI sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to LinkedIn each time the read runs. Because it reads only the records changed since the last run, pipeline revenue tied to the LinkedIn campaigns that sourced it stays current while platform teams running CockroachDB keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Cockroach to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Cockroach use cases