Integrations
An alert nobody sees is not an alert. Most of the value here is getting a change into the place your team already looks.
Where alerts go
| Destination | Typical use |
|---|---|
| Slack and Microsoft Teams | The channel the team already watches. Most customers start and stay here. |
| PagerDuty and Opsgenie | For the narrow set of changes that should wake someone. Choose this set carefully. |
| Jira and Linear | A change that needs a decision from the tag manager's owner becomes a ticket with the evidence attached. |
| Digest or immediate. Still how most compliance-side recipients prefer it. | |
| Webhook | Anything else. The payload is documented and versioned. |
Where evidence goes
| Destination | Typical use |
|---|---|
| Splunk, Datadog, Elastic | Change records alongside the rest of your telemetry |
| S3 or GCS export | Long retention for assessment evidence, on your own storage |
| SIEM via syslog or webhook | For teams whose evidence workflow already lives there |
What we read from
Tag manager inventories, where you grant read access — useful because it tells us who has edit rights, which is frequently more revealing than the script list itself. CDN and WAF logs, optionally, for corroboration on the account side.
Installation
One script tag, or a tag manager container, or a CDN worker if you would rather not touch the page template. Most teams are collecting within an afternoon; the inventory conversation afterwards is what takes the week. See the documentation.