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

    CONNECTIONS / Redshift / Redshift to LinkedIn Offline CAPI

    Offline and in-store sales in Redshift, activated for LinkedIn account-revenue reporting.

    Grant a scoped IAM role, name the table or materialized view, and Signals reports closed B2B deals so LinkedIn optimizes on account revenue with no UNLOAD to S3 and no file to hand off.

    Talk to our team Explore the setup

    redshift -> linkedin-offline-capi :: live

    1. ● redshift → linkedin.capi :: live
    2. > read sales.pos_fact rows=65,336
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 58,149 matched

    WHAT THIS ENABLES

    Redshift to LinkedIn Offline CAPI

    Redshift to LinkedIn Offline CAPI: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked as the materialized view refreshes.

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your Redshift tables as the materialized view refreshes.
    • Pipeline revenue tied to the LinkedIn campaigns that sourced it, fed by analytics teams maintaining Redshift tables and materialized views.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn R Scheduled read sync recorded in Redshift 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 numbers already modeled in Redshift tables and materialized views.

    Analytics teams maintaining Redshift tables and materialized views who need pipeline revenue tied to the LinkedIn campaigns that sourced it.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A scoped IAM role with SELECT on the schema you name to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      The Redshift Data API reads your Redshift tables, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.

    3. Deliver

      As the materialized view refreshes, Signals reports closed B2B deals so LinkedIn optimizes on account revenue, touches only the rows changed since the last read, 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 Redshift records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Redshift

    Redshift to Google OCI

    Redshift to Google Offline Conversions: The Redshift Data API reads the offline and…

    Learn more

    from Redshift

    Redshift to Google Store Sales

    Redshift to Google Store Sales: The Redshift Data API reads the offline and in-store sales…

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

    The refresh schedule drives it: when the materialized view rebuilds nightly, LinkedIn gets a nightly feed, and an hourly refresh runs hourly. Each read touches only changed rows, so pipeline revenue tied to the LinkedIn campaigns that sourced it stays fresh for long B2B attribution windows without RA3 load rising.

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

    The fill rate of the view matters more than Redshift itself. A clean hashed email or phone matches; a blank one never will. The first scheduled read reports quality from LinkedIn's Conversions API, the figure B2B teams whose deals close long after the impression weigh against long B2B attribution windows.

    NEXT STEP

    Redshift to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Redshift use cases