Jump to a popular page, or start typing.

    CONNECTIONS / MinIO

    MinIO + Datahash: self-hosted exports become signals.

    MinIO runs S3-compatible object storage entirely on infrastructure you control, from a single server to a Kubernetes cluster. Signals connects to your MinIO endpoint, reads files as they land, and delivers hashed events to your ad platforms.

    minio :: live

    1. ● minio :: signals live
    2. > object arrived s3://minio-cluster/exports/orders-2026-07-18.csv
    3. > parse rows=45,018 schema=orders
    4. hash sha256(email,phone)
    5. route meta · google · tiktok · snap
    6. ✓ 4 destinations synced · match 79%
    WHAT FLOWS THROUGH MINIO

    The signal MinIO yields, and receives.

    Every kind of signal that moves between MinIO and the platforms, through one hashed, deduplicated route.

    What flows Every platform Offline conversions Lead conversions Custom audiences Lead generation Signals hash · dedupe· route Google Meta Snap TikTok LinkedIn OpenAI
    Offline conversions
    A bucket on your self-hosted MinIO cluster is watched the same way any S3-compatible endpoint would, so an export job running inside your own network reaches Signals without exposing the cluster to the public internet.
    Lead conversions
    The column mapper translates whatever layout your internal export writes into consistent event fields, so teams running MinIO for full infrastructure control are not forced to standardize file formats first.
    Custom audiences
    Identifiers are SHA-256 hashed as the file is read from your endpoint, and the object is discarded after processing, which fits teams who chose self-hosted storage specifically to keep data off shared infrastructure.
    Lead generation inbound
    Row-level status comes back per file, so a team running its own storage cluster can confirm exactly what was read and processed without checking cluster logs separately.
    USE-CASE LISTING

    Pick your platform. Every use case for it, in one place.

    Every way MinIO data moves, grouped by platform and ranked by how many use cases MinIO supports.

    Google 5 Meta 4 Snap 4 TikTok 4 LinkedIn 3 OpenAI 1
    HOW IT CONNECTS

    From authorization to delivered signal.

    1. Connect

      Connect MinIO with scoped, read-only credentials to your endpoint.

    2. Watch

      Choose the bucket and file pattern on your cluster to watch.

    3. Map

      Map columns to events and identifiers in the visual mapper.

    4. Go live

      Verify sample rows in the live debugger and go live.

    FAQ

    MinIO questions, answered.

    Which file formats are supported?

    Delimited files such as CSV and TSV with configurable headers are the common case, and fixed-width layouts from internal systems can be handled through the column mapper. Point Signals at a bucket and file pattern on your MinIO endpoint, and any matching object is parsed as it lands, with no change needed to how your cluster is run.

    Is customer PII stored by Datahash?

    Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, with the source file discarded once processed. Since MinIO is usually chosen to keep storage fully self-hosted, a self-hosted Core deployment is available so the hashing step itself runs inside your own network rather than reaching out to Datahash Cloud.

    Does Signals need network access to our MinIO cluster?

    Yes, Signals needs read access to the specific bucket and endpoint you configure, scoped to a read-only credential. If your MinIO cluster is air-gapped or otherwise not reachable from outside your network, a self-hosted Core deployment runs the entire read-hash-route pipeline inside your own environment instead.

    NEXT STEP

    See your MinIO data working in every ad platform.

    Ready to enable a use case, or still mapping what MinIO data could do? Our team helps you find the right place to start.