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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Google OCI

    Your Commerce Cloud orders, wired to Google Ads offline conversion import.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it reconciles closed-won revenue to the Google Ads click through GCLID as orders complete, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    sfcc -> google-oci :: live

    1. ● commerce cloud → google.oci :: live
    2. > read closed_deals rows=29,896
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 24,515 matched

    WHAT THIS ENABLES

    Commerce Cloud to Google Offline Conversions

    Commerce Cloud to Google Offline Conversions: Signals reads your Commerce Cloud orders and reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your Commerce Cloud orders activated for Google Ads, as Signals reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Google Ads offline conversion import 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' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, reconciles closed-won revenue to the Google Ads click through GCLID, and sends only the orders that changed, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: sfcc.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=sfcc.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-15T18:36:56"
    5. conversion_value 13177 · currency_code AED
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Google Store Sales

    Commerce Cloud to Google Store Sales: Signals reads your Commerce Cloud orders and matches…

    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 OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Google OCI 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, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while enterprise retailers on Salesforce Commerce Cloud keep GCLID coverage in view. Delivery needs no export and no manual upload.

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

    NEXT STEP

    Commerce Cloud to Google OCI, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases