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

    CONNECTIONS / Dropbox / Dropbox to Meta Offline CAPI

    Your Dropbox files, wired to Meta's offline optimization.

    Signals reads your Dropbox files through read-only OAuth access to the Dropbox folder you name, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.

    Talk to our team Explore the setup

    dropbox -> meta-offline-capi :: live

    1. ● dropbox → meta.capi :: live
    2. > read closed_deals rows=62,882
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 55,965 matched

    WHAT THIS ENABLES

    Dropbox to Meta Offline CAPI

    Meta Offline CAPI for Dropbox: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your Dropbox files, hashed and consent-screened each time a new file lands.

    • Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your Dropbox files each time a new file lands.
    • Campaign learning fed by real-world purchases, with no export step out of your Dropbox files.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta File drop sync recorded in Dropbox S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, working out of Dropbox folders and shared exports.

    Teams dropping exports in Dropbox who need in-store and phone revenue joining Meta's optimization loop 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 Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

      Columns from your Dropbox files align to Meta's Offline Conversions API in the visual mapper, hashed as the file lands and checked for Meta's 62-day event window.

    3. Deliver

      Each time a new file lands, Signals reads your Dropbox files and credits dealer, branch, and phone sales to the Meta campaigns behind them, processes only the newly dropped file, with Meta's 62-day event window 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.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=dropbox.closed_deals
    3. event_name "Purchase" · event_time 2026-07-23T08:23:39
    4. value 26765.00 · currency SAR
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-68019"
    6. ✓ accepted match=89%
    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 Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Dropbox Meta 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 Meta on that cadence. Each run processes only the newly dropped file, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a Dropbox-sourced Meta 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 Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which teams dropping exports in Dropbox then raise inside your Dropbox files.

    NEXT STEP

    Dropbox to Meta Offline CAPI, in production this week.

    Talk to our team All Dropbox use cases