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

    CONNECTIONS / MinIO / MinIO to Google OCI

    From MinIO objects to Google Ads offline conversion import.

    Signals reads your MinIO objects through a read-only access key scoped to the MinIO bucket you name, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    minio -> google-oci :: live

    1. ● minio → google.oci :: live
    2. > read closed_deals rows=47,544
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 38,511 matched

    WHAT THIS ENABLES

    MinIO to Google Offline Conversions

    MinIO to Google Offline Conversions: Signals reads your MinIO objects and reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked each time a new file lands.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your MinIO objects each time a new file lands.
    • A clean line from click to closed revenue, with no export step out of your MinIO objects.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in MinIO S Signals hash · dedupe Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, working out of MinIO buckets and object prefixes.

    Platform teams self-hosting MinIO who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy 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 Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your MinIO objects align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the file lands and checked for GCLID coverage.

    3. Deliver

      Each time a new file lands, Signals reads your MinIO objects and reconciles closed-won revenue to the Google Ads click through GCLID, processes only the newly dropped file, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: minio.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=minio.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-18T22:56:19"
    5. conversion_value 30622 · currency_code SAR
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MinIO

    MinIO to Google Store Sales

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

    Learn more

    from MinIO

    MinIO to Meta Offline CAPI

    MinIO to Meta Offline CAPI: Signals reads your MinIO objects and credits dealer, branch,…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MinIO Google OCI sync run?

    Delivery tracks MinIO, run by platform teams self-hosting MinIO: a near-real-time or scheduled sync of your MinIO objects feeds Google Ads on that cadence. Each run processes only the newly dropped file, so a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.

    What match rate should a MinIO-sourced Google OCI 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 Google Ads; neither, and it will not. First-run feedback flags GCLID coverage, which platform teams self-hosting MinIO then raise inside your MinIO objects.

    NEXT STEP

    MinIO to Google OCI, in production this week.

    Talk to our team All MinIO use cases