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

    CONNECTIONS / FTP / FTP to Google Customer Match

    Your FTP drops, wired to Google Customer Match.

    Signals reads your FTP drops through read-only credentials scoped to the SFTP path 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

    ftp -> google-customer-match :: live

    1. ● ftp → google.match :: live
    2. > read segments rows=13,202
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 11,486 matched

    WHAT THIS ENABLES

    FTP to Google Customer Match

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

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

    WHAT FLOWS WHERE

    FTP to Customer Match, mapped.

    Signals reads the customer segments from your FTP drops 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 FTP drops 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 FTP and SFTP drop folders.

    Teams exporting nightly to SFTP who need Customer Match lists that add joiners and drop lapsed members each sync out of FTP drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only credentials scoped to the SFTP path you name, mapped to Google Ads' Customer Match API and tuned for the serving-size threshold.

    2. Map

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

    Lists that self-maintain across syncs out of your FTP drops, 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 FTP drops.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=ftp.segments
    3. operation ADD · user_list "segment_56432"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 13,202 · members_matched 11,486
    6. ✓ accepted match=87%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from FTP

    FTP to Meta Custom Audience

    FTP to Meta Custom Audience: your FTP drops, hashed and consent-checked, feed Meta as…

    Learn more

    from FTP

    FTP to TikTok Custom Audience

    FTP to TikTok Custom Audience: your FTP drops, hashed and consent-checked, feed 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 FTP Google Customer Match sync run?

    You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into Google Ads. Since Signals processes only the newly dropped file, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and teams exporting nightly to SFTP watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.

    What match rate should a FTP-sourced Google Customer Match batch expect?

    Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Customer Match API pinpoints the serving-size threshold, the number teams exporting nightly to SFTP tune against.

    NEXT STEP

    FTP to Google Customer Match, in production this week.

    Talk to our team All FTP use cases