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

    CONNECTIONS / Website / Website to Google EC Web

    From Website events to Google Enhanced Conversions for web.

    Connect Website and point Signals at your website events; it recovers checkout conversions with hashed first-party identifiers matched to the Google click as each event fires, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    website -> google-ec-web :: live

    1. ● website → google.web :: live
    2. > read web_orders rows=26,918
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 23,419 matched

    WHAT THIS ENABLES

    Website to Google Enhanced Conversions

    Website to Google Enhanced Conversions: your website events, hashed and consent-checked, feed Google Ads as Signals recovers checkout conversions with hashed first-party identifiers matched to the Google click as each event fires.

    • On-site purchase and checkout events from your website events activated for Google Ads, as Signals recovers checkout conversions with hashed first-party identifiers matched to the Google click.
    • Conversion accuracy restored where cookies alone fall short, drawn from your website events by web teams instrumenting the site.

    WHAT FLOWS WHERE

    Website to EC Web, mapped.

    Signals receives the on-site purchase and checkout events from your website events; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions (Google Ads API) accepts the web conversions for hashed-identifier enhancement.

    Signals receives the on-site purchase and checkout events from your website events; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions (Google Ads API) accepts the web conversions for hashed-identifier enhancement.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google web conversions decay with cookie loss, with the records already in on-site pixel and tag events.

    Web teams instrumenting the site activating Google Enhanced Conversions for web straight from website events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Signals tag or pixel on your site to feed Google Ads' Enhanced Conversions (Google Ads API), sized for hashed-identifier enhancement.

    2. Map

      Signals receives your website events, and its columns map to Google Ads' Enhanced Conversions (Google Ads API) in the visual mapper, hashed and checked for hashed-identifier enhancement.

    3. Deliver

      On each run, Signals pulls your website events, recovers checkout conversions with hashed first-party identifiers matched to the Google click, and forwards each event as it arrives, with hashed-identifier enhancement in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Conversion accuracy restored where cookies alone fall short on every run, as Signals reads your website events and forwards each event as it arrives.

    Checkout conversions recovered for Search and Shopping from your website events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from Google Ads' Enhanced Conversions (Google Ads API) on hashed-identifier enhancement, straight out of your website events.

    ON THE WIRE

    What EC Web actually receives.

    signals :: website.google-ec-web :: wire

    1. ● signals :: event payload
    2. > POST /enhanced_conversions source=website.web_orders
    3. hashed_email sha256 "b13f0a…" · hashed_phone_number sha256 "71cd8e…"
    4. order_id "ord-67968" · conversion_value 3696.00 · currency_code AED
    5. conversion_date_time "2026-07-23T07:32:48"
    6. ✓ accepted · enhancement applied
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Website

    Website to Meta CAPI

    Website to Meta Conversions API: your website events, hashed and consent-checked, feed Meta…

    Learn more

    from Website

    Website to Meta CTM

    Website to Meta Click-to-Message: your website events, hashed and consent-checked, feed…

    Learn more

    same use case

    BigCommerce to Google EC Web

    Google Enhanced Conversions for BigCommerce: Signals recovers checkout conversions with…

    Learn more

    generic

    Google Enhanced Conversions Web

    Datahash configures Enhanced Conversions Web with server-side user-data collection and…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Website Google EC Web sync run?

    You set the cadence, from near-real-time to a nightly Website sync of your website events into Google Ads. Since Signals forwards each event as it arrives, conversion accuracy restored where cookies alone fall short keeps pace and web teams instrumenting the site watch hashed-identifier enhancement. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Website-sourced Google EC Web batch expect?

    In Website, match rate tracks the email and phone quality your website events carry. Clean identifiers land for Google Ads; blank ones never will. The first Enhanced Conversions (Google Ads API) report shows web teams instrumenting the site where hashed-identifier enhancement needs work, a data-quality task handled in Website.

    NEXT STEP

    Website to Google EC Web, in production this week.

    Talk to our team All Website use cases