Set up a pixel monitor
A pixel monitor loads your page in a real browser and checks that your tracking tags still load: GTM, GA4, Meta and every other channel on the page. Every monitor starts from the scan: it reads the page and proposes the monitors for you, each tag with the evidence it was seen by, so nothing is ever typed from memory.
Scan the page
Open Monitors and click Add Monitor
From the sidebar, click Monitors. Then hit Add Monitor in the top-right corner. The dialog first asks what you want to monitor.
Choose Pixel
Choose Pixel. Event Tracking is the other route, covered in the volume monitor guide.
What do you want to monitor?
Pixels are checked by loading the page. Event tracking watches the events your tags already send to TagWatch.
Pick the page and scan it
Pick the domain, and choose the home page or another page. Conversion tags often only fire on a checkout or thank you page, so scan the page where the money moves. Then click Scan page.
Scan your website
TagWatch opens the page like a visitor would and reports which tracking tags load, so you do not have to look them up.
Watch the scan run
A browser window opens your page on our machines, so nothing is loaded on yours. The scan accepts the cookie banner like a real visitor, waits for the page to settle, and watches which tags fire. Up to 90 seconds.
Accepting the cookie banner
This runs on our machines, so nothing is loaded here.
Tick the tags and create the monitors
Every tag the scan saw is listed with its ID and the proof it was seen. The important ones come ticked. Pick the check frequency, click create, and TagWatch makes one monitor per channel. Notes about the setup, such as a tag that fires before consent, appear on the row they belong to.
What TagWatch found
Tags found on this page
4 found
Done: 3 monitors created for yourshop.com, one per channel. Every monitor runs each morning, at a moment TagWatch picks, so overnight breakage is caught before the workday starts.
Many sites at once: Bulk setup
Managing more than a handful of sites? Bulk setup on the Monitors page runs the same scan across every site you pick. The batch scans itself, two sites at a time, while you review one site’s findings and step through to the next; by the third site the rest is usually already done. Each site gets its own real results, consent findings included, and one click creates its monitors.
Scan your sites, one after another
Tips for reliable monitoring
Scan the page where the money moves
Tags often differ per page type. A checkout or thank you page catches breakage that homepage monitoring misses.
Cookie banners are handled for you
The check accepts the consent banner like a real visitor and reloads once, because some tags only fire on the next page view after consent. Pages behind a login still fail by design.
Server-side setups are found by themselves
The scan detects tagging servers and encoded loaders and points the checks at them. The server-side GTM guide is for when you want to find the domain by hand.
One check a day, at a moment we pick
Every monitor runs each morning. TagWatch spreads the fleet across the window so no check is judged by a browser that was busy with twenty others.
A changed tag ID is a two-field edit
Open the pencil on the monitor row: the ID and, for the Google platforms, the server-side URL are editable in place. The page and the platform stay what the scan established.
Ready to set up your first monitor?
Start your 14-day free trial. No credit card required.
Start free trial →