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

    CONNECTIONS / Google Drive / Google Drive to Google Customer Match

    Your Google Drive files, wired to Google Customer Match.

    Signals reads your Google Drive files through read-only OAuth access to the Google Drive folder 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

    google-drive -> google-customer-match :: live

    1. ● google drive → google.match :: live
    2. > read segments rows=39,113
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 34,028 matched

    WHAT THIS ENABLES

    Google Drive to Google Customer Match

    Google Customer Match for Google Drive: Signals projects your segments into Google Ads as Customer Match lists straight from your Google Drive files, hashed and consent-screened each time a new file lands.

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

    WHAT FLOWS WHERE

    Google Drive to Customer Match, mapped.

    Signals reads the customer segments from your Google Drive files each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    Signals reads the customer segments from your Google Drive files each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    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 Google Drive folders and shared exports.

    Teams sharing exports via Google Drive who need Customer Match lists that add joiners and drop lapsed members each sync out of Google Drive files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Google Drive folder you name, mapped to Google Ads' Customer Match API and tuned for the serving-size threshold.

    2. Map

      Columns from your Google Drive files 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 Google Drive files 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 Google Drive files, delivered each time a new file lands.

    Lists that self-maintain across syncs out of your Google Drive files, 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 Google Drive files.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=google-drive.segments
    3. operation ADD · user_list "segment_90126"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 39,113 · members_matched 34,028
    6. ✓ accepted match=87%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Google Drive

    Google Drive to Meta Custom Audience

    Meta Custom Audience for Google Drive: Signals keeps Meta audiences synced as adds and…

    Learn more

    from Google Drive

    Google Drive to TikTok Custom Audience

    TikTok Custom Audience for Google Drive: Signals delivers first-party segments to TikTok as…

    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 Google Drive Google Customer Match sync run?

    Delivery tracks Google Drive, run by teams sharing exports via Google Drive: a near-real-time or scheduled sync of your Google Drive files 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 Google Drive-sourced Google Customer Match batch expect?

    Coverage of hashed identifiers across your Google Drive files decides it, and teams sharing exports via Google Drive own that inside Google Drive. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the serving-size threshold, which teams sharing exports via Google Drive then raise inside your Google Drive files.

    NEXT STEP

    Google Drive to Google Customer Match, in production this week.

    Talk to our team All Google Drive use cases