Can PluginView detect Meta Pixel without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Meta Pixel — typically vendor endpoints. It does not bypass authentication or paywalls.

How many fingerprint rules cover Meta Pixel?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Meta Pixel?

Illustrative public indicators for Meta Pixel include connect.facebook.net/*/fbevents.js; facebook.com/tr. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Meta Pixel?

For Meta Pixel, start with: All pages; trigger pageview/event.

Detect Meta Pixel

Advertising, Attribution & Visitor Identification

PluginView detects Meta Pixel, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Meta Pixel include connect.facebook.net/*/fbevents.js, facebook.com/tr. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Meta Pixel

Loading website list…

Signal classes

PluginView evaluates public page signals in these classes when identifying Meta Pixel. Individual fingerprint rule bodies are proprietary and are not published.

Vendor endpoints

Example public indicators for Meta Pixel

Illustrative indicators derived from public catalog metadata for Meta Pixel. A live scan may match additional proprietary rules beyond these examples.

connect.facebook.net/*/fbevents.js
facebook.com/tr

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: All pages; trigger pageview/event

How to check a site for Meta Pixel

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Meta Pixel signals (prefer: All pages; trigger pageview/event).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Meta Pixel signature set (2 rules).
3. Review the confidence score and text explanation for Meta Pixel on the results page.

FAQ: detecting Meta Pixel

Can PluginView detect Meta Pixel without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Meta Pixel — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Meta Pixel?: Meta Pixel is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Meta Pixel?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Meta Pixel?: Illustrative public indicators for Meta Pixel include connect.facebook.net/*/fbevents.js; facebook.com/tr. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Meta Pixel?: For Meta Pixel, start with: All pages; trigger pageview/event.