---
schema_version: "1"
id: 649602bdae411794f99382c057dd449b3d82d365cd4c7622af683c4f75b73336
title: Set Up PCI Compliance Alerts
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_set_up_ecdn_pci_alerts.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_set_up_ecdn_pci_alerts.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 409e677fd9da10b5dca7461abcf3b02c317428ae9a7de91e631c24c9396b52f8
description: Get alerted when an eCDN Logpush job fails on a zone that carries PCI-scoped traffic for your B2C Commerce storefront. Wiring a notification rule to your SIEM or on-call tool lets you detect a stalled PCI log stream before the audit window expires.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Set Up PCI Compliance Alerts

Get alerted when an eCDN Logpush job fails on a zone that carries PCI-scoped traffic for your B2C Commerce storefront. Wiring a notification rule to your SIEM or on-call tool lets you detect a stalled PCI log stream before the audit window expires.

[Which Salesforce Commerce Product Do I Have?](https://help.salesforce.com/s/articleView?id=commerce.comm_what_product.htm&language=en_US)

To configure the Logpush delivery targets that these alerts monitor, see [Create a Logpush Job](https://help.salesforce.com/s/articleView?id=cc.b2c_create_ecdn_logpush_job.htm&release=264.0.0&type=5 "Create a Logpush job to stream eCDN request, security, and Page Shield logs from your B2C Commerce storefront continuously to a customer-owned destination. The New Logpush Job wizard walks through destination setup and job configuration in two steps.").

Alerting on Logpush job failures for PCI-scoped zones is the most common reason teams configure notifications. This task combines a destination and a notification rule for that use case. For the full field reference, see [Create a Notification Destination](https://help.salesforce.com/s/articleView?id=cc.b2c_create_ecdn_notification_destination.htm&release=264.0.0&type=5 "Register a webhook destination that receives eCDN notification payloads for your B2C Commerce storefront, such as a Slack incoming webhook or a custom HTTPS endpoint. A destination is reusable across multiple notification rules and across zones.") and [Create a Notification Rule](https://help.salesforce.com/s/articleView?id=cc.b2c_create_ecdn_notification_rule.htm&release=264.0.0&type=5 "Create a notification rule to bind a webhook destination to one or more eCDN zones for your B2C Commerce storefront and control whether delivery is enabled. Toggling a rule off pauses delivery without deleting the rule.").

1. In the receiver of your choice (Slack incoming webhook, PagerDuty Events API endpoint, or an internal alerting service), create a webhook and copy its URL.
2. In Business Manager, on the PCI zone's **Notifications** tab, click **New Destination** and paste the URL.
    
    Give the destination a clear name, such as Slack #pci-alerts or PagerDuty PCI.
3. Click **New Notification**, and select the destination from the **Webhook** dropdown.
4. Leave **Enable Notification Upon Saving** selected, and select the PCI zone.
    
    Select all zones if you want fleet-wide coverage.
5. Click **Save**.

You now receive a notification whenever an event configured for that destination fires on the selected zones, including Logpush job failures, which is the signal you need to detect a stalled PCI log stream before the audit window expires.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_tip.png)

Tip Keep the PCI alert destination separate from your general engineering channel. PCI alerts have a different on-call rotation and a different escalation path, and mixing them with general traffic dilutes both.