Salesforce Commerce Cloud

We have not shipped a Salesforce Commerce Cloud install. This is the shape we would expect, and the specific things we would confirm with you, starting with the real shape of your basket and confirmation URLs.

Not done: no Salesforce Commerce Cloud store has been through a real install

Nothing on this page is a report from a live install. It follows from how the tag behaves, not from anything we have watched it do on Salesforce Commerce Cloud. Treat every "likely" below as a question, not a promise. The two platforms we have proven end to end are Shopify and custom / headless; where we stand puts all six in one table.

What we can tell you without hedging is how the tag itself behaves. Nothing in it is Salesforce Commerce Cloud-specific, and only one path in it is Shopify-specific: the cart-attribute writer, which is off unless you are on Shopify with the order-email channel enabled. Page detection, the three cart adapters, the click id, the claim URL and the gwp:selection hook are all platform-neutral. That is why we can describe the shape below with some confidence, and still not claim we have walked it.

The shape we would expect

Tag placement	Likely an ISML include in the site's base template (SFRA htmlHead/footer), or your existing Tealium/GTM container
Adapter	datalayer if you run Tealium or GTM (most SFCC sites do); window is attractive here, since an ISML template can render window.gwp.cart directly. Remember to refresh it on AJAX cart updates and dispatch gwp:cartchange
Page detection	An SFRA /{locale}/cart URL already matches our defaults. SiteGenesis-style Cart-Show and /on/demandware.store/... URLs do not, so those need patterns set explicitly. Send us the real URLs
Claim moment	Order-Confirm is your page, so the on-page card should work. Your own order-confirmation email via the generic hook is the alternative
We would confirm	The exact basket and confirmation URL shapes (including any /on/demandware.store/... form and locale segments); whether the cart total is in your data layer or only in the DOM; your CSP, which on SFCC is often strict

Where next

• What to bring to that conversation. Three answers get an unproven platform scoped in a single call. Bring a staging URL if you have one; the tag runs there as soon as the hostname is registered.
• Shopify: a platform we have actually installed, written up end to end. The best way to judge the size of the job.
• Install the tag, the platform-agnostic guide: snippet, page registration, adapters, verification, troubleshooting and CSP.
• Ask us something. Email support@gwpingenuity.com with [INTEGRATION] in the subject, saying you are on Salesforce Commerce Cloud. We would rather scope it than have you find the gaps. (/support is the shopper help page, not developer support.)