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

    CONNECTIONS / MinIO / MinIO to Google Customer Match

    From MinIO objects to Google Customer Match.

    Signals reads your MinIO objects through a read-only access key scoped to the MinIO bucket you name, then projects your segments into Google Ads as Customer Match lists so Google Ads sees match-ready audiences without an export.

    Talk to our team Explore the setup

    minio -> google-customer-match :: live

    1. ● minio → google.match :: live
    2. > read segments rows=59,657
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 44,743 matched

    WHAT THIS ENABLES

    MinIO to Google Customer Match

    MinIO to Google Customer Match: Signals reads your MinIO objects and projects your segments into Google Ads as Customer Match lists, hashed and consent-checked each time a new file lands.

    • Signals projects your segments into Google Ads as Customer Match lists, reading your MinIO objects each time a new file lands.
    • Lists that self-maintain across syncs, with no export step out of your MinIO objects.

    WHAT FLOWS WHERE

    MinIO to Customer Match, mapped.

    Each sync hands the customer segments from your MinIO objects to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.

    Each sync hands the customer segments from your MinIO objects to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, working out of MinIO buckets and object prefixes.

    Platform teams self-hosting MinIO who need Customer Match lists that add joiners and drop lapsed members each sync 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' Customer Match API and tuned for the serving-size threshold.

    2. Map

      Columns from your MinIO objects align to Google Ads' Customer Match API in the visual mapper, hashed as the file lands and checked for the serving-size threshold.

    3. Deliver

      Each time a new file lands, Signals reads your MinIO objects and projects your segments into Google Ads as Customer Match lists, processes only the newly dropped file, with the serving-size threshold watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync from your MinIO objects, delivered each time a new file lands.

    Lists that self-maintain across syncs out of your MinIO objects, delivered each time a new file lands without transfer overhead climbing.

    Match feedback on the serving-size threshold from Google Ads' Customer Match API each run, tied back to your MinIO objects.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: minio.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=minio.segments
    3. operation ADD · user_list "segment_59274"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 59,657 · members_matched 44,743
    6. ✓ accepted match=75%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MinIO

    MinIO to Meta Custom Audience

    MinIO to Meta Custom Audience: Signals reads your MinIO objects and keeps Meta audiences…

    Learn more

    from MinIO

    MinIO to TikTok Custom Audience

    MinIO to TikTok Custom Audience: Signals reads your MinIO objects and delivers first-party…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MinIO Google Customer Match 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 lists that self-maintain across syncs holds up on the serving-size threshold. The live debugger confirms every delivery inline.

    What match rate should a MinIO-sourced Google Customer Match 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 the serving-size threshold, which platform teams self-hosting MinIO then raise inside your MinIO objects.

    NEXT STEP

    MinIO to Google Customer Match, in production this week.

    Talk to our team All MinIO use cases