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

    CONNECTIONS / AWS S3 / AWS S3 to LinkedIn Offline CAPI

    S3 exports into LinkedIn, built for LinkedIn account-revenue reporting.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket 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

    aws-s3 -> linkedin-offline-capi :: live

    1. ● aws s3 → linkedin.capi :: live
    2. > read closed_deals rows=54,746
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 47,082 matched

    WHAT THIS ENABLES

    AWS S3 to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for AWS S3: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your S3 exports each time a new file lands.
    • Account revenue attached to the sourcing campaign, with no export step out of your S3 exports.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn A File drop sync recorded in AWS S3 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 S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of S3 exports.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only IAM key scoped to the one S3 bucket you name, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

      Columns from your S3 exports align to LinkedIn's Conversions API in the visual mapper, hashed as the file lands and checked for long B2B attribution windows.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and reports closed B2B deals so LinkedIn optimizes on account revenue, processes only the newly dropped file, 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 AWS S3 records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: aws-s3.linkedin-offline-capi :: wire

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

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Google OCI

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

    Learn more

    from AWS S3

    AWS S3 to Google Store Sales

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

    You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into LinkedIn. Since Signals processes only the newly dropped file, pipeline revenue tied to the LinkedIn campaigns that sourced it keeps pace and data teams landing exports in S3 watch long B2B attribution windows. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 itself. A record with a current hashed email or phone matches for LinkedIn; one missing both cannot. First-run feedback from Conversions API pinpoints long B2B attribution windows, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to LinkedIn Offline CAPI, in production this week.

    Talk to our team All AWS S3 use cases