Meta Pixel GDPR compliance and consent risk
Meta Pixel tracks conversions and builds audiences for Facebook ads. This page combines ConsentLens detection rules with live public scan data so you can see how often Meta Pixel appears, whether it fires before consent, and which compliance issues it tends to create.
19%
Of scanned sites
74 of 384 public sites include Meta Pixel.
0%
Fire before consent
0 detected sites fired it before a user could consent.
0%
Seen after rejection
No post-rejection evidence found in public scan data.
HIGH
Consent risk
Marketing tracker classified from ConsentLens tracker database.
How ConsentLens detects Meta Pixel
Domains
- connect.facebook.net
- www.facebook.com/tr
- facebook.com/tr
- pixel.facebook.com
Globals
- window.fbq
Script patterns
- fbevents.js
ConsentLens combines these signals with request timing. If Meta Pixel sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.
Common compliance issues
Advertising / remarketing trackers detected
74Example public scans detecting Meta Pixel
| Domain | Score | Consent timing |
|---|---|---|
| devomech.com | 20/100 | No early fire |
| zazz.io | 20/100 | No early fire |
| cybercraftinc.com | 20/100 | No early fire |
| angrynerds.co | 20/100 | No early fire |
| kogifi.com | 20/100 | No early fire |
| kernelics.com | 20/100 | No early fire |
| qualimatrix.tech | 20/100 | No early fire |
| perpetualgroup.com | 20/100 | No early fire |