Codeless events
Event Setup Tool rules: which clicks and page visits fire which standard events.
Meta Pixel
Enter a pixel ID, a GTM container or any website. We read the pixel's public configuration: codeless events, advanced matching, server-side setup and every restriction.
About the Meta Pixel Checker
Every page with a Meta (Facebook) Pixel downloads that pixel's configuration from Meta. It contains the codeless events set up in Events Manager, the customer data sent for advanced matching, server-side settings and restrictions. The Meta Pixel checker reads it and scores the setup.
Event Setup Tool rules: which clicks and page visits fire which standard events.
Which customer fields (email, phone, name) the pixel sends to improve matching.
Conversions API Gateway and first-party setups found in the configuration.
A 0–100 score with the biggest improvements to make next.
Type any website, a GTM container, or a numeric pixel ID.
TagSpy finds the pixel and downloads its public configuration from Meta.
Rules, matching fields, restrictions and a prioritised list of fixes.
Enter the website in the Meta Pixel checker. TagSpy finds any pixel on the page or inside its Google Tag Manager container and opens its configuration.
It answers similar questions without installing anything, and goes further: it reads the pixel's configuration directly, including codeless rules and advanced matching fields the extension doesn't list.
When the pixel's configuration shows a Conversions API Gateway or a first-party endpoint, the checker reports it. Server-to-server events sent by a backend are not visible to anyone outside.
No. The configuration is public: Meta serves it to every visitor's browser. Nothing is installed, no login is needed, and nothing you check is stored.