CONNECTIONS / Salesforce Commerce Cloud
Commerce Cloud orders, credited across every site.
Salesforce Commerce Cloud's native LINK cartridges cover pixel tracking for a single site on the standard SFRA checkout. Signals adds server-side delivery to every platform you buy on across every site and locale, Order Management refunds reconciled automatically, and hashed audiences from customer segments.
- ● sfcc :: signals live
- > Order placed value=612.00 USD
- > Basket submitted step=payment
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · snap · linkedin
- ✓ 5 destinations synced · match 86%
The signal Salesforce Commerce Cloud yields.
Every kind of signal that moves between Salesforce Commerce Cloud and the platforms, through one hashed, deduplicated route.
- Web conversions
- Every basket submitted and order placed across a site's storefront, SFRA or a Composable Storefront on PWA Kit, reaches Meta, Google, TikTok, Snap, and LinkedIn server-side, deduped against whichever pixel is already installed.
- Offline conversions
- In-store and call-center orders entered through Salesforce Order Management post as offline conversions, matched by hashed identifier instead of a click.
- Custom audiences
- A refund or exchange processed through Order Management is reconciled against the original order so reported revenue reflects what was actually kept.
Pick your platform. Every use case for it, in one place.
Every way Salesforce Commerce Cloud data moves, grouped by platform and ranked by how many use cases Salesforce Commerce Cloud supports.
Google 4 
Meta 4 
Snap 3 
TikTok 3 
LinkedIn 2 
OpenAI 2 
Pinterest 1 
Reddit 1 
X 1 - Web conversions Google Enhanced Conversions Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Meta Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Web conversions Meta Messenger Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Snapchat Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions TikTok Events API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
From authorization to delivered signal.
-
Deploy
Signals cartridge added to the site's cartridge path, with Commerce API client credentials scoped to basket, order, and customer objects.
-
Map
Basket, order, and customer events mapped to each destination's event or audience schema in the visual mapper, per site, including refund and exchange events where they apply.
-
Hash and dedupe
Identifiers hashed with SHA-256 and deduped against any existing pixel or tag before anything leaves Commerce Cloud.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
Salesforce Commerce Cloud questions, answered.
Do we remove Salesforce Commerce Cloud's native Google and Meta LINK cartridges?
No. Keep them for catalog feeds and basic pixel coverage on a single site. Signals adds server-side delivery to every platform you buy on across every site and locale, Order Management revenue, and audience sync on top, deduped against whatever pixel is already installed so nothing double counts.
Does this work with a Composable Storefront on PWA Kit instead of SFRA?
Yes. Capture reads from Commerce API basket and order data rather than a script tied to a specific reference architecture, so a PWA Kit storefront and a classic SFRA site fire the same events, and migrating from one to the other does not break delivery to any destination.
We run multiple sites and brands on one Commerce Cloud instance. Supported?
Yes. Events carry the site ID, so each site or brand can route its baskets, orders, and customer events to its own destinations and ad accounts instead of one shared feed, even across regions or locales running on the same instance.
Does this integrate with Salesforce Order Management for returns and exchanges?
Where Order Management is connected, yes. A processed return or exchange is reconciled against the original order so reported revenue reflects what the customer actually kept, not the original order total, whether the adjustment happens in-store, online, or through a call center.
Are refunds reported back to the ad platforms?
Where a destination supports it, yes. A refunded order is reconciled against the original event so reported revenue reflects what was actually kept, not what was briefly charged at checkout, whether the refund is processed online or through Order Management.
NEXT STEP
See your Salesforce Commerce Cloud data working in every ad platform.
Ready to enable a use case, or still mapping what Salesforce Commerce Cloud data could do? Our team helps you find the right place to start.
