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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Google Store Sales

    Your Commerce Cloud orders, wired to Google Store Sales matching.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it matches in-person transactions to Google accounts as store-sales conversions as orders complete, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    sfcc -> google-store-sales :: live

    1. ● commerce cloud → google.sales :: live
    2. > read closed_deals rows=47,669
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 39,565 matched

    WHAT THIS ENABLES

    Commerce Cloud to Google Store Sales

    Commerce Cloud to Google Store Sales: Signals reads your Commerce Cloud orders and matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your Commerce Cloud orders activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how Salesforce Commerce Cloud closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google S Order sync recorded in Salesforce Co… S Signals hash · dedupe Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Google Store Sales matching 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' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, matches in-person transactions to Google accounts as store-sales conversions, and sends only the orders that changed, with the store-sales match rate in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Store Sales reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Salesforce Commerce Cloud records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: sfcc.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=sfcc.closed_deals
    3. transaction_time 2026-07-20T03:40:45 · transaction_amount_micros 20043000000
    4. currency_code USD
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Google OCI

    Commerce Cloud to Google Offline Conversions: Signals reads your Commerce Cloud orders and…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta Offline CAPI

    Commerce Cloud to Meta Offline CAPI: Signals reads your Commerce Cloud orders and credits…

    Learn more

    same use case

    ActiveCampaign to Google Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders stays current while enterprise retailers on Salesforce Commerce Cloud keep the store-sales match rate in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Google Store Sales 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 store-sales match rate, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Google Store Sales, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases