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

    CONNECTIONS / Dropbox / Dropbox to LinkedIn Offline CAPI

    Your Dropbox files, wired to LinkedIn account-revenue reporting.

    Signals reads your Dropbox files through read-only OAuth access to the Dropbox folder 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

    dropbox -> linkedin-offline-capi :: live

    1. ● dropbox → linkedin.capi :: live
    2. > read closed_deals rows=73,433
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 58,746 matched

    WHAT THIS ENABLES

    Dropbox to LinkedIn Offline CAPI

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

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

    The click, the conversion, and the credit.

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

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

    Teams dropping exports in Dropbox who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of Dropbox files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Dropbox folder you name, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

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

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Dropbox

    Dropbox to Google OCI

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

    Learn more

    from Dropbox

    Dropbox to Google Store Sales

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

    Delivery tracks Dropbox, run by teams dropping exports in Dropbox: a near-real-time or scheduled sync of your Dropbox files feeds LinkedIn on that cadence. Each run processes only the newly dropped file, so account revenue attached to the sourcing campaign holds up on long B2B attribution windows. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your Dropbox files decides it, and teams dropping exports in Dropbox own that inside Dropbox. A live email or phone matches into LinkedIn; neither, and it will not. First-run feedback flags long B2B attribution windows, which teams dropping exports in Dropbox then raise inside your Dropbox files.

    NEXT STEP

    Dropbox to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Dropbox use cases