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

    CONNECTIONS / FTP / FTP to Google EC for Leads

    Your FTP drops, wired to Google Enhanced Conversions for Leads.

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

    ftp -> google-ec-leads :: live

    1. ● ftp → google.leads :: live
    2. > read lead_pipeline rows=43,881
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 34,666 matched

    WHAT THIS ENABLES

    FTP to Google EC for Leads

    FTP to Google EC for Leads: your FTP drops, hashed and consent-checked, feed Google Ads as Signals sends down-funnel lead milestones matched to the originating Google click each time a new file lands.

    • Signals sends down-funnel lead milestones matched to the originating Google click, reading your FTP drops each time a new file lands.
    • Lead-value signals matched to the paid click, with no export step out of your FTP drops.

    WHAT FLOWS WHERE

    FTP to EC for Leads, mapped.

    Signals reads the qualified-lead and pipeline signals from your FTP drops each time a new file lands, hashes and screens each record, and posts the lead conversions to Google Ads' Enhanced Conversions API, keeping GCLID and hashed-email matching in view.

    Signals reads the qualified-lead and pipeline signals from your FTP drops each time a new file lands, hashes and screens each record, and posts the lead conversions to Google Ads' Enhanced Conversions API, keeping GCLID and hashed-email matching in view.

    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 FTP and SFTP drop folders.

    Teams exporting nightly to SFTP who need lead-value bidding fed by the stages your pipeline actually reaches 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' Enhanced Conversions API and tuned for GCLID and hashed-email matching.

    2. Map

      Columns from your FTP drops align to Google Ads' Enhanced Conversions API in the visual mapper, hashed as the file lands and checked for GCLID and hashed-email matching.

    3. Deliver

      Each time a new file lands, Signals reads your FTP drops and sends down-funnel lead milestones matched to the originating Google click, processes only the newly dropped file, 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 FTP drops, delivered each time a new file lands.

    Lead-value signals matched to the paid click out of your FTP drops, delivered each time a new file lands without transfer overhead climbing.

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

    ON THE WIRE

    What EC for Leads actually receives.

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

    1. ● signals :: event payload
    2. > POST /conversion_action source=ftp.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 FTP

    FTP to Meta Conversion Leads

    FTP to Meta CAPI for CRM: your FTP drops, hashed and consent-checked, feed Meta as Signals…

    Learn more

    from FTP

    FTP to TikTok CRM

    FTP to TikTok CRM Integration: your FTP drops, hashed and consent-checked, feed 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 FTP Google EC for Leads 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, lead-value bidding fed by the stages your pipeline actually reaches keeps pace and teams exporting nightly to SFTP watch GCLID and hashed-email matching. One scoped connection sets it up, cadence adjustable later.

    What match rate should a FTP-sourced Google EC for Leads 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 Enhanced Conversions API pinpoints GCLID and hashed-email matching, the number teams exporting nightly to SFTP tune against.

    NEXT STEP

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

    Talk to our team All FTP use cases