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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Google EC Web

    Your Commerce Cloud orders, wired to Google Enhanced Conversions for web.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it recovers checkout conversions with hashed first-party identifiers matched to the Google click as orders complete, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    sfcc -> google-ec-web :: live

    1. ● commerce cloud → google.web :: live
    2. > read web_orders rows=72,602
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 54,452 matched

    WHAT THIS ENABLES

    Commerce Cloud to Google Enhanced Conversions

    Commerce Cloud to Google Enhanced Conversions: Signals reads your Commerce Cloud orders and recovers checkout conversions with hashed first-party identifiers matched to the Google click, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your Commerce Cloud orders 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 Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to EC Web, mapped.

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

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; 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 Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Google Enhanced Conversions for web straight from Commerce Cloud orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to Commerce Cloud, reading only your Commerce Cloud orders to feed Google Ads' Enhanced Conversions (Google Ads API), sized for hashed-identifier enhancement.

    2. Map

      Signals reads your Commerce Cloud orders, 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 Commerce Cloud orders, recovers checkout conversions with hashed first-party identifiers matched to the Google click, and sends only the orders that changed, 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 Commerce Cloud orders and sends only the orders that changed.

    Checkout conversions recovered for Search and Shopping from your Commerce Cloud orders, with API call volume steady because Signals sends only the orders that changed.

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

    ON THE WIRE

    What EC Web actually receives.

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

    1. ● signals :: event payload
    2. > POST /enhanced_conversions source=sfcc.web_orders
    3. hashed_email sha256 "b13f0a…" · hashed_phone_number sha256 "71cd8e…"
    4. order_id "ord-54848" · conversion_value 4584.00 · currency_code AED
    5. conversion_date_time "2026-07-14T06:00:48"
    6. ✓ accepted · enhancement applied
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta CAPI

    Commerce Cloud to Meta Conversions API: Signals reads your Commerce Cloud orders and sends…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta CTM

    Commerce Cloud to Meta Click-to-Message: Signals reads your Commerce Cloud orders and…

    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 Commerce Cloud Google EC Web sync run?

    The pace follows your Commerce Cloud orders: Signals sends changes from Commerce Cloud to Google Ads as orders complete. Because it sends only the orders that changed, conversion accuracy restored where cookies alone fall short stays current while enterprise retailers on Salesforce Commerce Cloud keep hashed-identifier enhancement in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Commerce Cloud orders decides it, and enterprise retailers on Salesforce Commerce Cloud own that inside Commerce Cloud. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags hashed-identifier enhancement, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Google EC Web, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases