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

    CONNECTIONS / IBM DB2 / IBM DB2 to LinkedIn Offline CAPI

    Db2 tables into LinkedIn, built for LinkedIn account-revenue reporting.

    Connect IBM DB2 and point Signals at your Db2 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

    ibm-db2 -> linkedin-offline-capi :: live

    1. ● ibm db2 → linkedin.capi :: live
    2. > read closed_deals rows=68,945
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 61,361 matched

    WHAT THIS ENABLES

    IBM DB2 to LinkedIn Offline CAPI

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

    • Offline and in-store sales from your Db2 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 Db2 tables by enterprise data teams on IBM DB2.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Enterprise data teams on IBM DB2 activating LinkedIn account-revenue reporting straight from Db2 tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      A scheduled read pulls your Db2 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 Db2 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 IBM DB2 records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: ibm-db2.linkedin-offline-capi :: wire

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

    Adjacent moves on the same stack.

    from IBM DB2

    IBM DB2 to Google OCI

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

    Learn more

    from IBM DB2

    IBM DB2 to Google Store Sales

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

    The pace follows your Db2 tables: Signals sends changes from IBM DB2 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 enterprise data teams on IBM DB2 keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    IBM DB2 to LinkedIn Offline CAPI, in production this week.

    Talk to our team All IBM DB2 use cases