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

    CONNECTIONS / FTP / FTP to LinkedIn Offline CAPI

    Your FTP drops, wired to LinkedIn account-revenue reporting.

    Signals reads your FTP drops through read-only credentials scoped to the SFTP path 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

    ftp -> linkedin-offline-capi :: live

    1. ● ftp → linkedin.capi :: live
    2. > read closed_deals rows=34,626
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 29,086 matched

    WHAT THIS ENABLES

    FTP to LinkedIn Offline CAPI

    FTP to LinkedIn Offline CAPI: your FTP drops, hashed and consent-checked, feed LinkedIn as Signals reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands.

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

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn F File drop sync recorded in FTP 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 FTP and SFTP drop folders.

    Teams exporting nightly to SFTP who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of FTP drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only credentials scoped to the SFTP path you name, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

      Columns from your FTP drops 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 FTP drops 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 FTP records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from FTP

    FTP to Google OCI

    FTP to Google Offline Conversions: your FTP drops, hashed and consent-checked, feed Google…

    Learn more

    from FTP

    FTP to Google Store Sales

    FTP to Google Store Sales: your FTP drops, hashed and consent-checked, feed Google Ads 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 FTP LinkedIn Offline CAPI sync run?

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

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

    Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP 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 teams exporting nightly to SFTP tune against.

    NEXT STEP

    FTP to LinkedIn Offline CAPI, in production this week.

    Talk to our team All FTP use cases