Jump to a popular page, or start typing.

    CONNECTIONS / Microsoft Excel / Microsoft Excel to Google EC for Leads

    Your Excel workbook rows, wired to Google Enhanced Conversions for Leads.

    Signals reads your Excel workbook rows through read-only access to the Excel workbook you name, then sends down-funnel lead milestones matched to the originating Google click so Google Ads sees lead conversions without an export.

    microsoft-excel -> google-ec-leads :: live

    1. ● microsoft excel → google.leads :: live
    2. > read lead_pipeline rows=10,489
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 9,335 matched

    WHAT THIS ENABLES

    Microsoft Excel to Google EC for Leads

    Microsoft Excel to Google EC for Leads: your Excel workbook rows, 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 Excel workbook rows each time a new file lands.
    • Lead-value signals matched to the paid click, with no export step out of your Excel workbook rows.

    WHAT FLOWS WHERE

    Microsoft Excel to EC for Leads, mapped.

    Signals picks up the qualified-lead and pipeline signals from your Excel workbook rows; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions API accepts the lead conversions for GCLID and hashed-email matching.

    Signals picks up the qualified-lead and pipeline signals from your Excel workbook rows; 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 Excel worksheets and named ranges.

    Finance and ops teams working in Excel who need lead-value bidding fed by the stages your pipeline actually reaches out of Excel workbook rows.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only access to the Excel workbook you name, mapped to Google Ads' Enhanced Conversions API and tuned for GCLID and hashed-email matching.

    2. Map

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

    Lead-value signals matched to the paid click out of your Excel workbook rows, 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 Excel workbook rows.

    ON THE WIRE

    What EC for Leads actually receives.

    signals :: microsoft-excel.google-ec-leads :: wire

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

    Asked on almost every call.

    How often does the Microsoft Excel Google EC for Leads sync run?

    You set the cadence, from near-real-time to a nightly Microsoft Excel sync of your Excel workbook rows 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 finance and ops teams working in Excel watch GCLID and hashed-email matching. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your Excel workbook rows, which finance and ops teams working in Excel control, not Microsoft Excel 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 finance and ops teams working in Excel tune against.

    NEXT STEP

    Microsoft Excel to Google EC for Leads, in production this week.