Is your tracking actually firing?
Check any URL for real: live HTTP status, TLS certificate expiry, redirect chain, and whether your GA4, Meta Pixel, GTM and TikTok tags are present. A real request from our server — not a simulation.
Uptime & status
The real HTTP status code and response time, following redirects to the final URL.
TLS certificate
Whether the certificate is valid and how many days until it expires.
Tracking pixels
Detects GA4, Meta Pixel, Google Tag Manager and TikTok tags in the page.
Redirects
The full redirect chain, so you catch tracking-dropping 301s.
Why tracking silently breaks
A pixel that stops firing doesn't throw an error — it just quietly stops sending data, and you only notice weeks later when reporting looks wrong and campaigns have been optimizing on nothing.
A deploy drops the tag
A template change or a new consent wrapper removes the snippet from a page. The site works; the pixel is gone.
A redirect strips it
A marketing 301 (trailing slash, http→https, geo split) lands on a page that never had the tag — so paid clicks arrive untracked.
The certificate expires
An expired TLS cert blocks the page in modern browsers; every tag on it stops with it. Days-left warnings catch this early.
Frequently asked questions
HTTP status, TLS expiry and tracking-pixel detection — answered.
What does the Pixel Health Checker do?
It makes a real request to your URL from our server and reports the live HTTP status, response time, TLS certificate expiry, the full redirect chain, and which analytics/ads tracking pixels are present in the page — GA4, Meta Pixel, Google Tag Manager and TikTok.
Which tracking pixels does it detect?
GA4 / gtag.js, the Meta (Facebook) Pixel via fbq or fbevents.js, Google Tag Manager (GTM-XXXX / gtm.js), and TikTok (ttq / analytics.tiktok.com). It looks at the HTML the server returns.
Why would a pixel show as missing when I know it's installed?
The most common reasons: the tag is injected later by a consent/cookie banner or by GTM after user interaction, or it only loads client-side after events this one-shot fetch doesn't trigger. Check the page source and your tag manager's trigger conditions.
Does it check my SSL/TLS certificate?
Yes — it reports whether the certificate is valid and how many days until it expires, so you catch an expiry before it takes the site (and your tracking) down.
Is this a real check or a simulation?
A real HTTP request from our server, following redirects to the final URL. It is not a client-side guess — that's the whole point of the tool.
More free tools
Same deal — instant, no signup.