X (Twitter) Pixel GDPR compliance and consent risk
X (Twitter) Pixel tracks conversions from X/Twitter ads. This page combines ConsentLens detection rules with live public scan data so you can see how often X (Twitter) Pixel appears, whether it fires before consent, and which compliance issues it tends to create.
27%
Of scanned sites
118 of 444 public sites include X (Twitter) Pixel.
1%
Fire before consent
1 detected sites fired it before a user could consent.
3%
Seen after rejection
3 detected sites show post-rejection evidence.
HIGH
Consent risk
Marketing tracker classified from ConsentLens tracker database.
How ConsentLens detects X (Twitter) Pixel
Domains
- static.ads-twitter.com
- analytics.twitter.com
- t.co
Globals
- window.twq
Script patterns
- ads-twitter.com
ConsentLens combines these signals with request timing. If X (Twitter) 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
118X (Twitter) Pixel continues tracking after consent rejection
3X (Twitter) Pixel bypasses consent banner
1Example public scans detecting X (Twitter) Pixel
| Domain | Score | Consent timing |
|---|---|---|
| eetgroup.com | 59/100 | Before consent |
| mederi.jp | 20/100 | No early fire |
| yourselfirst.com | 20/100 | No early fire |
| zazz.io | 20/100 | No early fire |
| beewebsystems.com | 20/100 | No early fire |
| angrynerds.co | 20/100 | No early fire |
| isbx.com | 20/100 | No early fire |
| ulansoftware.com | 20/100 | No early fire |