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

    CONNECTIONS / Clickhouse / ClickHouse to LinkedIn Offline CAPI

    From ClickHouse tables to LinkedIn account-revenue reporting.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then reports closed B2B deals so LinkedIn optimizes on account revenue so LinkedIn sees offline conversions without an export.

    Talk to our team Explore the setup

    clickhouse -> linkedin-offline-capi :: live

    1. ● clickhouse → linkedin.capi :: live
    2. > read closed_deals rows=22,387
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 19,701 matched

    WHAT THIS ENABLES

    ClickHouse to LinkedIn Offline CAPI

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

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your ClickHouse tables each time the read runs.
    • Account revenue attached to the sourcing campaign, with no export step out of your ClickHouse tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn Scheduled read sync recorded in Clickhouse 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, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of ClickHouse tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the ClickHouse tables you name, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

      Columns from your ClickHouse tables align to LinkedIn's Conversions API in the visual mapper, hashed as the read runs and checked for long B2B attribution windows.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and reports closed B2B deals so LinkedIn optimizes on account revenue, reads only the records changed since the last run, with long B2B attribution windows watched 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 Clickhouse records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Google OCI

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

    Learn more

    from Clickhouse

    ClickHouse to Google Store Sales

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

    The pace follows your ClickHouse tables: Signals sends changes from ClickHouse 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 analytics engineers on ClickHouse keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

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

    In ClickHouse, match rate tracks the email and phone quality your ClickHouse tables carry. Clean identifiers land for LinkedIn; blank ones never will. The first Conversions API report shows analytics engineers on ClickHouse where long B2B attribution windows needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Clickhouse use cases