Catch broken tracking pixels before they break your data

Every ad platform ships a base snippet: Meta Pixel with fbq init and a 15–16 digit ID, TikTok Pixel with ttq.load and a 20+ character uppercase ID, Google tag with an AW-, G- or GT- identifier. The snippet belongs in the <head> of every page, loads over HTTPS, and appears exactly once — duplicates fire events twice and corrupt every report downstream.

A healthy setup also fires its base event. A Meta init without fbq('track', 'PageView'), a ttq.load without ttq.page(), a gtag script without gtag('config') — the code loads, nothing is recorded, and the ad platform optimizes against silence.

The most expensive tracking bugs are boring: a pixel ID copied with a digit missing, the same base code pasted into the header and a tag manager, a snippet that still loads over http:// and gets blocked as mixed content, a Meta pixel without the noscript fallback that loses every visitor with JavaScript disabled.

This checker is honest about its limits: it statically inspects the snippet or ID you paste. It cannot load your website, watch network requests or confirm that events reach the platform — for that, pair it with the platform pixel helpers. What it does catch is the class of mistakes that silently break tracking before a single event fires.