Why breach alerts matter
Compliance is not a one-time pass. A site that scored clean last week can break this week when someone adds a pixel in the tag manager, a new embed lands on a landing page, or a vendor quietly changes their tag code. Without alerting, that regression sits silently until a regulator or a data-subject complaint surfaces it.
Breach Notifications turn the Privacy Score into a tripwire. When a scheduled scan finishes and the score has dropped below your threshold, Pulse emails the group you nominated so the right people can act before the leak compounds.
Open the Notifications panel
Edit the Pulse project and scroll to the panel headed Notifications. It sits between the Always-Active Trackers panel and the Scan Schedule panel on the project setup page.
Two settings live here: the notification group that receives the email, and the breach threshold that decides when one is sent. Both are needed for alerts to fire.
Pick a Notification Group
Use the Notification Group dropdown to choose who receives breach emails. The first option is -- None (no breach emails) --, which disables alerting entirely. Select a named group to turn alerting on. If you have not created the group yet, use the Manage notification groups link beside the label to set one up in a new tab, then return and select it.
Notification groups are shared across the company, so the same group can serve Pulse breach alerts, Observer monitoring, and other modules. That means you maintain the recipient list in one place rather than per project.
Set the Breach Threshold
In the Breach Threshold (%) field, enter the compliance score below which an email should be sent. The value accepts 1 to 100 and defaults to 80. An email goes out only when the score is strictly below this percentage, so a score exactly at the threshold does not trigger one.
Save the project to apply. From then on, every scheduled scan compares its score to the threshold. No email is sent if no group is selected, or if the score lands at or above the threshold.
The threshold is a strict cutoff. A score exactly equal to the threshold does not send an email, so if you want to be alerted right at the boundary, set the threshold one point higher than the score you care about.
Troubleshooting
No email arrived after a low score
Check three things in order. First, confirm the Notification Group is set to a real group and not None. Second, confirm the score was strictly below the threshold, not equal to it. Third, confirm the group has at least one valid recipient. If all three are correct and email still does not arrive, the scan may not have completed, so verify it reached a finished state.
Too many alert emails
A threshold set too high relative to the site's normal score will fire on every scan. Raise the site's score by fixing the underlying findings, or lower the threshold so it only flags genuine regressions rather than the site's steady state.