You are here:
Configure Notifications for an eCDN Zone
Get notified when eCDN events that matter to you happen, such as a Logpush job failure on a PCI-bound zone, a security incident, or a configuration change, without having to watch dashboards. The Notifications tab on the Configure Zone screen lets you configure webhook destinations (such as a Slack incoming webhook or your own HTTPS endpoint) and wire them up to one or more zones.
Looking for the Logpush, Logpull, Crypto, Security Rules, Speed, Customization, Page Shield Policies, or Host Header Override Rules controls on the same screen? See the companion guides for Configure Logpush and Logpull for an eCDN Zone and Configure an eCDN Zone in Business Manager.
- In Business Manager, click the App Launcher, then select .
- Locate the zone you want to configure, and select Configure Zone from the actions menu.
-
Click the Notifications tab.
The Notifications tab is split into two sections:
- Destinations - Webhook endpoints that receive notification payloads (Slack incoming webhook, custom HTTPS endpoint, and so on).
- Notifications - Notification rules that bind a destination to one or more zones and toggle delivery on or off.
A destination is reusable across multiple notification rules and across zones - register it once in the Destinations table, then reference it from any number of Notifications rows.
After you configure notification rules, eCDN sends runtime event notifications to the selected destinations for each enabled zone. Common use cases include PCI compliance alerts, security events, and configuration drift detection.
Create a Destination
A destination is a single webhook endpoint that the eCDN can POST notification payloads to. Salesforce Commerce Cloud sends a JSON body to the URL you register; what happens to that payload (Slack message, ticket, alert) is up to the receiving system.
| Field | Required | Description |
|---|---|---|
| Name | Yes | Human-readable destination label shown in notification rules and lists. |
| URL | Yes | Webhook URL. Must start with http:// or
https://. Use HTTPS for sensitive traffic. |
| Secret (Optional) | No | Shared secret used to sign the request body so your receiver can verify source and integrity. |
- In the Destinations section, click New Destination. The Create Webhook screen opens.
- Enter a Name. This is the label that will appear in the Webhook dropdown when you create a notification rule.
- Enter a URL. The field accepts only valid HTTP or HTTPS URLs.
- (Optional) Enter a Secret. The eCDN will use this value to sign request bodies; configure your receiver to verify the signature before trusting the payload.
- Click Save.
If the URL is malformed, the URL field shows an inline error and the form blocks the save until you correct it. After save, the destination appears in the Destinations table with status Active. You can select the same destination in multiple notification rules and across multiple zones.
Create a Notification Rule
A notification rule binds one destination to one or more zones, and controls whether delivery is enabled. Toggling a rule off pauses delivery without deleting the rule.
| Field | Required | Description |
|---|---|---|
| Webhook | Yes | Destination that receives notification events. |
| Enable Notification Upon Saving | No | Starts delivery immediately when you save the rule. |
| Zones | Yes | Zones covered by the rule. Select All or select a subset. |
- In the Notifications section, click New Notification. The Create Notification screen opens.
- Open the Webhook dropdown and pick the destination you registered earlier. If the destination you want isn't in the list, register it first under Destinations.
- Select Enable Notification Upon Saving if you want the rule to start delivering immediately. Leave it off to create the rule in a paused state.
- Pick the Zones the rule applies to. Select All to select every zone in the list, or select zones individually. The current zone is selected by default.
- Click Save.
If a selected zone no longer resolves after the page loads, a warning toast names the zone and saves the rule without that binding. Refresh the page and edit the rule to re-select any missing zones.
When the rule saves successfully, a confirmation toast appears and the rule shows up in the Notifications table with the Enabled toggle reflecting the choice you made on the form.
Wire Up a PCI Alert
The most common reason teams set this up is to alert on Logpush job failures for zones that carry PCI-scoped traffic to a customer SIEM. To configure Logpush delivery targets, see Configure Logpush and Logpull for an eCDN Zone.
- Create a webhook destination in the receiver of your choice (Slack incoming webhook, PagerDuty Events API endpoint, internal alerting service). Copy the URL.
- In Business Manager, on the PCI zone's Notifications tab, click New Destination and paste the URL. Give it a clear name like Slack #pci-alerts or PagerDuty PCI.
- Click New Notification, pick the destination from the Webhook dropdown, leave Enable Notification Upon Saving selected, and select the PCI zone (or All zones if you want fleet-wide coverage).
- Click Save.
You will now receive a notification whenever an event configured for that destination fires on the selected zone(s) - including Logpush job failures, which is the signal you need to detect a stalled PCI log stream before the audit window expires.
Manage Existing Notification Rules
The Notifications table shows every rule that targets the current zone, along with the destination it delivers to, the full zone list, and an Enabled toggle.
- Toggle delivery - Flip the Enabled switch on a row to pause or resume delivery without losing the rule.
- Edit - Open the row's actions menu and choose Edit to change the destination, zone selection, or enabled state.
- Delete - Open the row's actions menu and choose Delete to remove the rule entirely. Deletion asks for explicit confirmation because it cannot be undone. If you only want to mute the rule temporarily, use the Enabled toggle instead.
I Don't See the Notifications Tab
The Notifications tab is part of the new LWC Configure Zone screen. If you're on the legacy interface, switch to the new screen via your usual Business Manager navigation. If the tab still doesn't appear, contact your Salesforce Commerce Cloud administrator - the new LWC screens are rolled out per-realm and may not yet be enabled for your instance.

