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

    CONNECTIONS / Close / Close to Google Customer Match

    Close smart-view opportunities into Google Ads, built for Google Customer Match.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, 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

    close -> google-customer-match :: live

    1. ● close → google.match :: live
    2. > read segments rows=21,287
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 17,242 matched

    WHAT THIS ENABLES

    Close to Google Customer Match

    Close to Google Customer Match: your Close smart-view opportunities, hashed and consent-checked, feed Google Ads as Signals projects your segments into Google Ads as Customer Match lists as records change.

    • Signals projects your segments into Google Ads as Customer Match lists, reading your Close smart-view opportunities as records change.
    • Lists that self-maintain across syncs, with no export step out of your Close smart-view opportunities.

    WHAT FLOWS WHERE

    Close to Customer Match, mapped.

    Each sync hands the customer segments from your Close smart-view opportunities 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 Close smart-view opportunities 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 Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need Customer Match lists that add joiners and drop lapsed members each sync out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Google Ads' Customer Match API and tuned for the serving-size threshold.

    2. Map

      Columns from your Close smart-view opportunities align to Google Ads' Customer Match API in the visual mapper, hashed as the sync runs and checked for the serving-size threshold.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and projects your segments into Google Ads as Customer Match lists, sends only the records that changed, 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 Close smart-view opportunities, delivered as records change.

    Lists that self-maintain across syncs out of your Close smart-view opportunities, delivered as records change without API call volume climbing.

    Match feedback on the serving-size threshold from Google Ads' Customer Match API each run, tied back to your Close smart-view opportunities.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=close.segments
    3. operation ADD · user_list "segment_55406"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 21,287 · members_matched 17,242
    6. ✓ accepted match=81%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Meta Custom Audience

    Close to Meta Custom Audience: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to TikTok Custom Audience

    Close to TikTok Custom Audience: your Close smart-view opportunities, hashed and…

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

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to Google Ads as records change. Because it sends only the records that changed, Customer Match lists that add joiners and drop lapsed members each sync stays current while inside-sales teams running Close keep the serving-size threshold in view. Delivery needs no export and no manual upload.

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

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Google Ads; blank ones never will. The first Customer Match API report shows inside-sales teams running Close where the serving-size threshold needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Google Customer Match, in production this week.

    Talk to our team All Close use cases