When Tagnovo opens an alert
An alert opens only after a second confirmed check agrees a tag is absent. Waiting holds the first reading. Open is two. A page we could not see never alerts.
Last reviewed September 2026.
The screen this guide means
“Alerts” is the workspace inbox at /app/alerts. It is not the store matrix and not a Google Analytics count alert. The block below is the Waiting tab — the first time a tag is silent, before anyone is told.
A finding is not an alert
A store page can show a silent tag after one check. That sentence is a finding. It does not appear on Open. If the page was observable, the same fingerprint appears on Waiting with confirm count 1. The next scheduled check either agrees and opens it, or sees the tag fire and the waiting row is resolved.
The first completed scan of a new store is the baseline. It can create a waiting row. It cannot open an alert.
Absence only
Tagnovo alerts when a tag went to zero on a page we could see — library loaded, collect never left. It does not alert on a percentage decline, a quieter day, or a count that merely dropped. A Google Analytics threshold cannot see a library that returned 200 and never collected. Why GA4 alerts miss a silent tag.
The control
If the store’s own beacon did not fire, we cannot tell a broken tag from a page we failed to observe. That page is unobservable. It does not increment confirmation and it does not close an open alert. How to tell if a pixel is actually working.
What Open can do
An open row is two confirmed checks. Acknowledge records that you saw it. Accept as intended and mute are not offered yet. Where a route would send mail is on Alert routing. The inbox is the record. Saving a route does not create a row.
Open the screen this guide means
Waiting is the first silent reading. Open is two confirmed absences. A finding on a store is not this list.