Skip to content
TagSentry

Event monitoring

See every event and the tags it fired, live, with the fields each one sent, and get one email when something stops.

The short answer

The same line that runs your banner watches what your pages send. Connect Tag Manager to see which tag sent each event. You get one email when something breaks and one when it recovers.

Turn it on

The one-line tag already reports events from your pages, including pixels pasted outside Tag Manager. To see which Tag Manager tag sent each event, press Add to your Tag Manager on the monitoring page. It adds our monitoring template to your container through your Google connection. Nothing is published until you press publish.

Events

Events lists every event your site sent in the chosen window, with a status, a count and when it was last seen.

  • Firing: arriving as usual.
  • Broken: it used to arrive and has stopped. This is what triggers an alert.
  • Recovered: it stopped, and it's arriving again.
  • Quiet: not seen in this window, which can be normal for an event like a refund.

If every event on the site stops at once, the site shows as Stopped: usually the code was removed or the site is down.

Pick your key events (your conversions, such as purchase or generate_lead), and we watch those more closely.

Flow

Flow follows one event to the tags that fired from it and the hosts each tag sent to, for example purchase to Google Analytics 4 to region1.google-analytics.com. "Sent" means the browser made the request to that host.

Inspect

Open any event to see why it might have stopped, the tags that fired from it, and the fields in its newest payload, each with its name and type, like ecommerce.value <number:float>. Copy for my developer copies a plain-text summary to paste into a ticket.

What we record

We store the field names and types in each payload, plus destination hosts, URL paths and parameter names. Values aren't stored.

The one exception is the event name a known tracker sends in its own request: Meta Pixel's ev, GA4's en and Pinterest's event. That's how we can say "Meta Pixel sent Purchase ×3" for a pixel pasted into your theme. We keep it only if it looks like an event name, and we check it again on our side.

Monitoring follows the same rules as your banner. In ask-first places like the EU and UK, it runs only after the visitor agrees. In opt-out places like California, it runs until the visitor opts out or their browser sends a privacy signal (GPC). If most of a site's visitors refuse analytics, it will show few events. That's correct.

Alerts

Alerts go to the site owner by email, on by default. We send one when something breaks and one when it recovers, and that's all for that problem.

AlertPlan
An event or tag stops arrivingFree
A new tracker appears on your siteFree
A key event arrives with empty or missing fieldsEvery plan
A key event drops below its usual volumePro
Alerts to Slack or a webhookPro

History

Free keeps 14 days of events. Paid sites keep 30, 90 or 365 days, following the site's level, and you choose when that level moves down. You can also choose a shorter window in the site's settings. See Billing.