Pro-active monitoring

How AdPage watches a client's tracking setup around the clock and alerts you the moment something breaks — instead of finding out weeks later.

What does Pro-active Monitoring do?

Most tracking problems aren't discovered by looking at a dashboard — they're discovered when a client asks why their reported revenue looks wrong, sometimes weeks or months after a tag quietly stopped firing. Pro-active Monitoring closes that gap: AdPage continuously scans a container's tracking setup and automatically alerts the right people the moment something looks off, instead of waiting for someone to notice.

	Without Pro-active Monitoring	With Pro-active Monitoring
Checking	Manual, occasional	Automated, continuous
Detection time	Weeks to months	Within minutes
Alerting	None — someone has to notice first	Automatic, sent straight to the inbox

What gets scanned:

• Tag activity and status

• Incoming_requests from platforms

• Platform delivery outgoing_requests

• Webhook matching

Pro-active Monitoring is a Performance package feature.

Where to find it

Alerting is configured per container, under Proactieve Monitoring (next to Basis Monitoring, History and Alert Logbook on the container's monitoring page).

Setting up Pro-active Monitoring

1

Turn on alerts

Flip Alerts activate to on. This is the master switch — with it off, none of the settings below send anything, no matter how they're configured.

2

Choose the alert frequency

Frequency	What it sends	Availability
Hourly	A short summary	Performance package only
Daily	A daily overview	Performance package only
Weekly	A weekly report	Available on any package — an admin can enable this manually for a client without Performance

Only one frequency is active at a time.

3

Choose which alert types to send

Two toggles, independent of each other:

• Critical Alerts — tracking has completely stopped, or there's a serious data issue.

• Warnings — potential problems that need attention but aren't (yet) breaking anything.

A client can be on Critical-only if they only want to hear about the fires, or have both on for earlier warnings too.

4

Manage email recipients

Under Email receivers, each recipient has an on/off toggle so you can pause someone's alerts without removing them. One recipient is marked Primary and can't be deleted, only toggled — every other recipient can be removed with the trash icon. Add someone new by typing their address in the field at the bottom and clicking Add.

5

Save

Click save to apply the configuration. A green Alerts active confirmation summarises what the client will now receive.

Testing your alert configuration

There are two ways to test, and they check different things:

• Send test email — fires an unconditional test email to the current recipient list, regardless of the container's actual tracking status. Use this to confirm the alert emails actually arrive and aren't landing in spam.

• Full validation + alert test — runs a real check against the container and only sends an alert if it actually finds an issue. Use this to confirm the detection logic itself is working, not just email delivery.

Run the full validation after any tracking change you'd expect Pro-active Monitoring to catch, to confirm it actually gets flagged.

You can also setup Slack and Teams as delivery channels in addition to email.

If a client's alerting needs don't fit contact [e-mail] with the container ID.