Tag error notifications make sure you hear about critical tag errors right away, without being flooded by repeated alerts. They cover both client-side and server-side tags.
How it works
Every day at 9:00 AM, Code-Cube.io automatically checks your data for new errors and for errors that have increased significantly.
Notification | When you receive it |
Error alert | A new error is detected, or an existing error occurs significantly more often |
Weekly summary | Every Monday: an overview of all errors detected in the previous week |
No repeated alerts for the same issue
Code-Cube.io uses deduplication: you're alerted about new or escalated errors only, not about the same issue every day.
Tip: Because you only receive new or escalated errors, every alert is worth a quick look.
Settings in the portal
Setting | What it controls |
Threshold for first-time notifications | The minimum error percentage that triggers an alert |
Deduplication sensitivity | How often you're notified about recurring errors |
What to do with an error alert
Open the error in Tag Monitor. The Tag Debug Assistant shows the severity of each broken tag, its plausible root cause, the possible business impact, and potential fixes. See 
Tag Debug Assistant.
Related pages
What is considered an error?: when a tag counts as failed
Tag volume notifications- Tag anomaly notifications
Setup notification channel: choose where you receive alerts