Meta Pixel Detection Test
Search fetched HTML for common Meta Pixel initialization and request signals.
Run the meta pixel detection test
Public website checkWhat meta pixel detection test helps you do
Search fetched HTML for common Meta Pixel initialization and request signals. A detected pixel ID identifies a source-level installation. Test consent state and actual browser requests before deciding that Purchase or Lead events reach the correct account.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
Source detection cannot confirm event delivery, attribution, consent compliance or pixels added by a tag manager after load. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Separate source installation from observed events
A pixel initialization string can remain in a template after the marketing team stops using the associated account. Conversely, a consent-controlled tag may be absent from the initial source and appear only after a permitted browser action. Treat this check as an installation clue. Verify the intended pixel ID with the account owner, then use the appropriate browser and account diagnostics to inspect a real event. Avoid claiming that sales attribution works merely because a script name appears. Document whether the test occurred before or after consent so two people do not compare fundamentally different page states.
Verify the result and continue
Note which page state was observed before comparing results with a colleague. A consent-controlled implementation can legitimately differ between initial load and an authorized interaction. Verify the intended account identifier and an actual test event using the provider diagnostics; a source signature establishes neither event success nor consent correctness. Continue with the page request counter or explore the social & analytics tool cluster.
How this tool works
Search fetched HTML for common Meta Pixel initialization and request signals. The server fetches the submitted public URL with bounded redirects and response sizes. The result reports observed HTML, headers or network evidence for this specific check.
What the result does and does not establish
Source detection cannot confirm event delivery, attribution, consent compliance or pixels added by a tag manager after load.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow