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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Google Customer Match

    Your Commerce Cloud orders, wired to Google Customer Match.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it projects your segments into Google Ads as Customer Match lists as orders complete, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    sfcc -> google-customer-match :: live

    1. ● commerce cloud → google.match :: live
    2. > read segments rows=27,188
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 24,469 matched

    WHAT THIS ENABLES

    Commerce Cloud to Google Customer Match

    Commerce Cloud to Google Customer Match: Signals reads your Commerce Cloud orders and projects your segments into Google Ads as Customer Match lists, hashed and consent-checked as orders complete.

    • Customer segments from your Commerce Cloud orders activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to Customer Match, mapped.

    Signals reads the customer segments from your Commerce Cloud orders; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    Signals reads the customer segments from your Commerce Cloud orders; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Google Customer Match 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' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, projects your segments into Google Ads as Customer Match lists, and sends only the orders that changed, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Commerce Cloud orders and sends only the orders that changed.

    Lists that self-maintain across syncs 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' Customer Match API on the serving-size threshold, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: sfcc.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=sfcc.segments
    3. operation ADD · user_list "segment_94107"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 27,188 · members_matched 24,469
    6. ✓ accepted match=90%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta Custom Audience

    Commerce Cloud to Meta Custom Audience: Signals reads your Commerce Cloud orders and keeps…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to TikTok Custom Audience

    Commerce Cloud to TikTok Custom Audience: Signals reads your Commerce Cloud orders and…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Google Customer Match 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, Customer Match lists that add joiners and drop lapsed members each sync stays current while enterprise retailers on Salesforce Commerce Cloud keep the serving-size threshold in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Google Customer Match 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 the serving-size threshold, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Google Customer Match, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases