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

    CONNECTIONS / Close / Close to Google EC for Leads

    Close smart-view opportunities into Google Ads, built for Google Enhanced Conversions for Leads.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then sends down-funnel lead milestones matched to the originating Google click so Google Ads sees lead conversions without an export.

    Talk to our team Explore the setup

    close -> google-ec-leads :: live

    1. ● close → google.leads :: live
    2. > read lead_pipeline rows=40,422
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 29,508 matched

    WHAT THIS ENABLES

    Close to Google EC for Leads

    Close to Google EC for Leads: your Close smart-view opportunities, hashed and consent-checked, feed Google Ads as Signals sends down-funnel lead milestones matched to the originating Google click as records change.

    • Signals sends down-funnel lead milestones matched to the originating Google click, reading your Close smart-view opportunities as records change.
    • Lead-value signals matched to the paid click, with no export step out of your Close smart-view opportunities.

    WHAT FLOWS WHERE

    Close to EC for Leads, mapped.

    Each sync hands the qualified-lead and pipeline signals from your Close smart-view opportunities to Signals, which hashes and filters every record, then Google Ads' Enhanced Conversions API logs the lead conversions for GCLID and hashed-email matching.

    Each sync hands the qualified-lead and pipeline signals from your Close smart-view opportunities to Signals, which hashes and filters every record, then Google Ads' Enhanced Conversions API logs the lead conversions for GCLID and hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Google lead-gen advertisers bidding past the first form submit, working out of Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need lead-value bidding fed by the stages your pipeline actually reaches 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' Enhanced Conversions API and tuned for GCLID and hashed-email matching.

    2. Map

      Columns from your Close smart-view opportunities align to Google Ads' Enhanced Conversions API in the visual mapper, hashed as the sync runs and checked for GCLID and hashed-email matching.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and sends down-funnel lead milestones matched to the originating Google click, sends only the records that changed, with GCLID and hashed-email matching watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lead-value bidding fed by the stages your pipeline actually reaches from your Close smart-view opportunities, delivered as records change.

    Lead-value signals matched to the paid click out of your Close smart-view opportunities, delivered as records change without API call volume climbing.

    Match feedback on GCLID and hashed-email matching from Google Ads' Enhanced Conversions API each run, tied back to your Close smart-view opportunities.

    ON THE WIRE

    What EC for Leads actually receives.

    signals :: close.google-ec-leads :: wire

    1. ● signals :: event payload
    2. > POST /conversion_action source=close.lead_pipeline
    3. gclid "Cj0KCQjw…" · conversion_action "sql_reached"
    4. conversion_value 7 · currency GBP
    5. hashed_email sha256 "9c41af…"
    6. ✓ accepted match=gclid+hashed_email
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Meta Conversion Leads

    Close to Meta CAPI for CRM: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to TikTok CRM

    Close to TikTok CRM Integration: your Close smart-view opportunities, hashed and…

    Learn more

    same use case

    ActiveCampaign to Google EC for Leads

    ActiveCampaign to Google EC for Leads: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Enhanced Conversions for Leads

    Datahash pushes hashed user data from your CRM back to Google Ads so lead-based campaigns…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Close Google EC for Leads 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, lead-value bidding fed by the stages your pipeline actually reaches stays current while inside-sales teams running Close keep GCLID and hashed-email matching in view. Delivery needs no export and no manual upload.

    What match rate should a Close-sourced Google EC for Leads 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 Enhanced Conversions API report shows inside-sales teams running Close where GCLID and hashed-email matching needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Google EC for Leads, in production this week.

    Talk to our team All Close use cases