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

    CONNECTIONS / MinIO / MinIO to Meta Offline CAPI

    From MinIO objects to Meta's offline optimization.

    Signals reads your MinIO objects through a read-only access key scoped to the MinIO bucket 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

    minio -> meta-offline-capi :: live

    1. ● minio → meta.capi :: live
    2. > read closed_deals rows=33,171
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 28,859 matched

    WHAT THIS ENABLES

    MinIO to Meta Offline CAPI

    MinIO to Meta Offline CAPI: Signals reads your MinIO objects and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked each time a new file lands.

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

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta File drop sync recorded in MinIO 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 MinIO buckets and object prefixes.

    Platform teams self-hosting MinIO who need in-store and phone revenue joining Meta's optimization loop out of MinIO objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only access key scoped to the MinIO bucket you name, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

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

    What Offline CAPI actually receives.

    signals :: minio.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=minio.closed_deals
    3. event_name "Purchase" · event_time 2026-07-17T02:01:25
    4. value 16310.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-52685"
    6. ✓ accepted match=87%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MinIO

    MinIO to Google OCI

    MinIO to Google Offline Conversions: Signals reads your MinIO objects and reconciles…

    Learn more

    from MinIO

    MinIO to Google Store Sales

    MinIO to Google Store Sales: Signals reads your MinIO objects and matches in-person…

    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 MinIO Meta Offline CAPI sync run?

    Delivery tracks MinIO, run by platform teams self-hosting MinIO: a near-real-time or scheduled sync of your MinIO objects 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 MinIO-sourced Meta Offline CAPI batch expect?

    Coverage of hashed identifiers across your MinIO objects decides it, and platform teams self-hosting MinIO own that inside MinIO. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which platform teams self-hosting MinIO then raise inside your MinIO objects.

    NEXT STEP

    MinIO to Meta Offline CAPI, in production this week.

    Talk to our team All MinIO use cases