ConsentLens
MarketingHigh consent risk

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.

26%

Of scanned sites

98 of 384 public sites include X (Twitter) Pixel.

1%

Fire before consent

1 detected sites fired it before a user could consent.

1%

Seen after rejection

1 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

98

X (Twitter) Pixel bypasses consent banner

1

X (Twitter) Pixel continues tracking after consent rejection

1

Example public scans detecting X (Twitter) Pixel

DomainScoreConsent timing
eetgroup.com59/100Before consent
zazz.io20/100No early fire
beewebsystems.com20/100No early fire
angrynerds.co20/100No early fire
isbx.com20/100No early fire
ulansoftware.com20/100No early fire
feecreative.com20/100No early fire
kogifi.com20/100No early fire
Report issue