A notification group is a named list of email addresses that TagPipes alerts go to. Create it once for the company, then pick it on any audit schedule, monitor, table, export or scan that should email people.

What a group is

A notification group has a title, a list of email addresses and a scope. Modules never store their own recipient lists: each alerting item has a Notification Group field, and you pick a group there. Change who is on the group and everyone who relies on it is updated in one place.

Groups belong to the company. Observer's notification groups are the same groups; old Observer links now open this page.

Create a group

On Companies, click the gear icon next to the company, then click Notification Groups.
Click Add Group.
Fill in the fields:

Field	What it does
Title	The name you pick from in each module, for example "Analytics team". Required
Description	What the group is for and who is on it. Required
Scope	All properties (company-wide), or one property. A property group is offered only on that property; a company-wide group is offered everywhere
Email Addresses (comma delimited)	One or more addresses separated by commas, for example `ana@example.com, ops@example.com`. Required
Enabled	Whether the group is active. See below

Click Submit.

Every Notification Group field in TagPipes has a Manage notification groups link that opens this page in a new tab, so you can add a group without leaving the form you are on.

Which modules use groups

Module	Where you pick the group	When the group is emailed
Auditor	Audit schedule	A scheduled audit run finds one or more rule failures
AutoTag	Project	A sync fails
Echo	Source	The source's event volume drops to zero after a baseline of earlier traffic
Lens	Data table, and attribution setup	A sync fails, or the table goes longer than expected without a successful sync
Lens	Export	An export run fails
Observer	Dataset (Default Notification Group) and monitor	A monitor raises an alarm. A monitor uses its own group, or the dataset's default if it has none
Pulse	Monitor	A scan's privacy score falls below the alert threshold
Shield	Settings	New and overdue privacy requests

Each field also has a "none" option, such as None (no notifications) or None (alerts off), which turns that item's emails off.

Observer monitors need a group

An Observer monitor with no group of its own and no dataset default is not evaluated at all. Pick a group on the monitor, or set a default on the dataset.

Change a group's addresses

Edit the group, change Email Addresses, and click Submit.

Auditor schedules that use the group pick up the change straight away.
AutoTag projects, Echo sources, Lens tables, Pulse monitors and Shield settings keep a copy of the addresses from when they were last saved. After you change a group, open each of those items and save it again.

Enabled

On the Notification Groups list, a group that is not enabled shows with its title struck through. Auditor schedules stop emailing a disabled group. For other modules, set the item's group to "none" to stop its emails.

Delete a group

Click the trash icon on the group's row and confirm. The group disappears from every picker. An item that still points at it shows (deleted group) in its Notification Group field until you pick another group, so saving that item does not quietly change where its alerts go.

Troubleshooting

Problem	Cause	Fix
A group is missing from a module's picker	The group is scoped to a different property	Edit the group and set Scope to this property or All properties (company-wide)
"Selected notification group belongs to a different property"	Same as above, reported when you save	Same as above
A changed address still gets, or does not get, alerts	The item kept the old copy of the addresses	Open the item and save it again
The Scope column says "Unknown property"	The group's property was deleted	Edit the group and pick a current scope

Notification Groups