Install WebDecoy on Salesforce Commerce Cloud
Salesforce Commerce Cloud (SFCC) serves storefronts through its own Cloudflare zone, called the eCDN, where you cannot add anything. Cloudflare’s Orange-to-Orange (O2O) setup puts your own Cloudflare zone in front of it. Your zone runs first, so the WebDecoy edge sensor can run there and see every request to the storefront: AI crawlers, price and catalog scrapers, search crawlers and curl, including requests SFCC answers from its cache.
Before you begin
Section titled “Before you begin”- A Cloudflare Enterprise zone for your domain, with Cloudflare running its DNS.
- An SFCC Proxy Zone for the storefront. Salesforce’s help explains the difference and how to migrate from a Legacy Zone.
- A WebDecoy account with the storefront added under the address shoppers use, for example
https://www.example.com. Create a free account.
1. Point your hostname at SFCC through Cloudflare
Section titled “1. Point your hostname at SFCC through Cloudflare”In SFCC Business Manager, find the CNAME target for the storefront hostname. It looks like commcloud.prod-abcd-example-com.cc-ecdn.net: the environment (prod, stg or dev), your realm ID and your domain with hyphens.
In your Cloudflare zone, open DNS → Records and create a record for each storefront hostname:
- Type:
CNAME - Name: the hostname, for example
www - Target: the CNAME from Business Manager
- Proxy status: Proxied (orange cloud)
Each record must target the SFCC CNAME directly. A record that points at another of your proxied records (for example preview → www) does not get O2O, and the sensor will not run for it.
2. Apply Cloudflare’s recommended zone settings
Section titled “2. Apply Cloudflare’s recommended zone settings”Cloudflare’s SFCC guide lists settings for hostnames that point at SFCC. The ones that matter most:
- Bypass cache on the SFCC hostnames with a Cache Rule. SFCC caches in its own zone; caching in yours as well causes stale pages when SFCC purges.
- Match the Security Level set in Business Manager, and turn off Browser Integrity Check for those hostnames.
- Minimum TLS version 1.2.
3. Deploy the edge sensor
Section titled “3. Deploy the edge sensor”- In WebDecoy, select the storefront.
- Open Integrations → Cloudflare and choose Connect with Cloudflare, then approve the scopes on Cloudflare’s consent screen.
- Open Edge Sensor, choose the zone, and set the route to cover each storefront hostname, for example
www.example.com/*. - Select Deploy edge sensor.
No code and no cartridge are involved. The edge sensor guide covers the details, including Worker usage and the static-file paths it skips.
4. Fire a test request
Section titled “4. Fire a test request”curl -A "WebDecoy-Test/1.0" https://www.example.com/Swap in your own address. Within a minute a detection labelled Test appears, and Sensors shows the Edge Worker row as Reporting.
Things to know
Section titled “Things to know”- The sensor does not block. It reports, and it lets the request through on any error of its own. Cloudflare notes that a Worker on an O2O hostname can interfere with traffic; the sensor only changes a response when you turn on enforcement for a path. Test enforcement on a staging hostname first.
- Zone hold. If SFCC reports “The hostname is associated with a held zone”, release the hold temporarily (for a subdomain, turn off Also prevent Subdomains), then refresh the hostname in SFCC.
- Certificates. If you have CAA records, they must allow a certificate authority Cloudflare supports, or HTTPS can fail.
- One edge sensor per organization, today. Other sites in the same WebDecoy organization can report through an SDK or the browser script.
- Support. For problems in your own Cloudflare zone, your Cloudflare account team or Cloudflare Support helps and consults Salesforce where needed.
Next step
Section titled “Next step”Verify the install, then see what crawlers did in your storefront’s first report.