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

    CONNECTIONS / Freshsales / Freshsales to Google EC for Leads

    Your Freshsales deals and lifecycle stages, wired to Google Enhanced Conversions for Leads.

    Signals reads your Freshsales deals and lifecycle stages through scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, 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

    freshsales -> google-ec-leads :: live

    1. ● freshsales → google.leads :: live
    2. > read lead_pipeline rows=64,526
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 56,138 matched

    WHAT THIS ENABLES

    Freshsales to Google EC for Leads

    Google EC for Leads for Freshsales: Signals sends down-funnel lead milestones matched to the originating Google click straight from your Freshsales deals and lifecycle stages, hashed and consent-screened as records change.

    • Signals sends down-funnel lead milestones matched to the originating Google click, reading your Freshsales deals and lifecycle stages as records change.
    • Lead-value signals matched to the paid click, with no export step out of your Freshsales deals and lifecycle stages.

    WHAT FLOWS WHERE

    Freshsales to EC for Leads, mapped.

    Signals reads the qualified-lead and pipeline signals from your Freshsales deals and lifecycle stages; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions API accepts the lead conversions for GCLID and hashed-email matching.

    Signals reads the qualified-lead and pipeline signals from your Freshsales deals and lifecycle stages; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions API accepts 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 Freshsales deals, contacts, and lifecycle stages.

    Sales teams running Freshsales who need lead-value bidding fed by the stages your pipeline actually reaches out of Freshsales deals and lifecycle stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, mapped to Google Ads' Enhanced Conversions API and tuned for GCLID and hashed-email matching.

    2. Map

      Columns from your Freshsales deals and lifecycle stages 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 Freshsales deals and lifecycle stages 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 Freshsales deals and lifecycle stages, delivered as records change.

    Lead-value signals matched to the paid click out of your Freshsales deals and lifecycle stages, 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 Freshsales deals and lifecycle stages.

    ON THE WIRE

    What EC for Leads actually receives.

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

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

    Adjacent moves on the same stack.

    from Freshsales

    Freshsales to Meta Conversion Leads

    Meta CAPI for CRM for Freshsales: Signals reports lead-stage progress so Meta bids toward…

    Learn more

    from Freshsales

    Freshsales to TikTok CRM

    TikTok CRM Integration for Freshsales: Signals reports pipeline-stage changes to TikTok as…

    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 Freshsales Google EC for Leads sync run?

    The pace follows your Freshsales deals and lifecycle stages: Signals sends changes from Freshsales 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 sales teams running Freshsales keep GCLID and hashed-email matching in view. Delivery needs no export and no manual upload.

    What match rate should a Freshsales-sourced Google EC for Leads batch expect?

    In Freshsales, match rate tracks the email and phone quality your Freshsales deals and lifecycle stages carry. Clean identifiers land for Google Ads; blank ones never will. The first Enhanced Conversions API report shows sales teams running Freshsales where GCLID and hashed-email matching needs work, a data-quality task handled in Freshsales.

    NEXT STEP

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

    Talk to our team All Freshsales use cases