MCM Alerts Overview
MCM Alerts use set criteria to determine any unusual or potentially dangerous circumstances surrounding tracking activity across your domain(s).
You can set up five types of Alerts to receive email notification either in real time or daily (depending on alert type), notifying you that a rule has been violated, detailing information and if applicable, where the vendor is located on your domain.
Once set up in MCM, you can Accept or Reject an Alert. Or Share it with a co-worker, etc. DAILY ALERTS
- There are two (2) Daily alerts: New and Missing
- Data that is pulled daily refers to the 24-hour period of 12am to 11:59 UTC, for the day before.
Nightly Alerts (New, Missing and all Summaries) are executed at 3am UTC (20 min to 4-hour process).
| |
New Tags |
| Purpose: |
Receive notification when a new tag has been detected on the selected Domain(s). |
| Data Source: |
24 Hour Period of User and Synthetic. |
| Configuration: |
Compares yesterday’s counts to the day before counts, finding new data combinations that can trigger an alert. |
| Filters: |
- Domain(s): Choose as many Domains as you have configured in your account.
- Threshold: Set the number of times a Tag must be seen (each 24 hours) in order to send an alert email to all Recipients. The system inputs 5, but if you delete that and leave it blank, it defaults to 1.
|
| Best Practice: |
Use this alert as a governance tool. Monitor a container tag, and increase awareness of what new tags come onto your site(s). |
| |
Missing Tags |
| Purpose: |
This alert notifies you when a wanted tag you want on the selected Domain(s) no longer appears |
| Data Source: |
24 Hour Period of User and Synthetic. |
| Configuration: |
Compares yesterday’s counts to the day before counts, finding missing data combinations that can trigger an alert. |
| Filters: |
- Domain(s): Choose as many Domains as you have configured in your account.
- Tag(s): Select the tag(s) that, if they don’t appear in the 24 hour period, trigger an alert email to all Recipients.
- Threshold: None
|
| Best Practice: |
This alert is useful for any tag that should be on every page. We recommend using it to support analytics. |
REAL TIMEThere are 3 Real time alerts: Blacklist, Whitelist and Non-Secure
Real Time service for Alerts (Blacklist, Whitelist, Non Secure) is always running, scanning real time data within the MCM collections.
| |
Blacklist Tags |
| Purpose: |
Create a list of tags deemed untrustworthy for any number of business reasons. |
| Data Source: |
Real Time (immediate) of User and Synthetic. |
| Configuration: |
When a data combination that triggers an alert is seen, it is saved to the customer database. Then, an alert count for tag configuration is conducted, and an email is sent if the tag count is at (or above) the threshold. |
| Filters: |
- Domain(s): Choose as many Domains as you have configured in your account.
- Tag(s): Select the tag(s) that must appear to trigger an alert email to all Recipients.
- Threshold: Set the number of times a Tag must be seen in order to send an alert email to all Recipients. The system inputs 5, but if you delete that and leave it blank, it defaults to 1. If the threshold is set to one, you will receive an email every time each tag is seen.
|
| Best Practice: |
If you have a bad experience with a vendor, and don’t want a relationship with them, set up a blacklist tag alert. This ensures they stay off your domains by notifying you when they reappear. |
| |
Whitelist Tags |
| Purpose: |
Receive notification when a tag that is NOT on your whitelist has been detected on the selected Domain(s). |
| Data Source: |
Real Time (immediate) of User and Synthetic. |
| Configuration: |
When a data combination that triggers an alert is seen, it is saved to the customer database. Then, an alert count for tag configuration is conducted, and an email is sent if the tag count is at (or above) the threshold. |
| Filters: |
- Domain(s): Choose as many Domains as you have configured in your account.
- Tag(s): Select the tag(s) that must appear to trigger an alert email to all Recipients.
- Threshold: Set the number of times a Tag must be seen in order to send an alert email to all Recipients. The system inputs 5, but if you delete that and leave it blank, it defaults to 1. If the threshold is set to one, you will receive an email every time each tag is seen.
|
| Best Practice: |
One of the easiest ways to know if you’re working with a new vendor is to create a living Whitelist of approved vendors, shared across the company.
*Note - Users can possibly experience a high volume of white list alerts if there's multiple tags that are not white listed. Black list alerts are a recommended alternative to prevent an abundance amount of email alerts.
|
| |
Non-Secure Tags |
| Purpose: |
This alert notifies you when a non-secure tag (an HTTP tag that is called on an HTTPS URL) has been detected on the selected Domain(s). |
| Data Source: |
Real Time (immediate) of User and Synthetic. |
| Configuration: |
When a data combination that triggers an alert is seen, it is saved to the customer database. An alert email is sent every time the tag is seen. |
| Filters: |
- Domain(s): Choose as many Domains as you have configured in your account.
- Thresholds: none (alert is triggered every time a Non-Secure alert is seen).
|
| Best Practice: |
Knowing if a tag is non-secure is important, as it is likely that a non-secure tag firing on a secure page will throw a mixed-content warning leading most consumers to abandon that page. It also opens you to attack and can affect SEO rankings (Google ranks completely secure sites higher). |
