Overview
Twitter (now X) provides the Universal Website Tag (UWT), an advertising pixel that tracks site visitor behavior and fires conversion events for ad campaigns running on the X/Twitter platform. The pixel is the legacy Twitter Ads implementation — it is functionally equivalent to the X Ads pixel but may appear under the Twitter branding in older deployments. Embedded Tweet buttons and Follow buttons also load Twitter's tracking scripts even when the visitor does not interact with them.
What This Script Does
Universal Website Tag (UWT)
The UWT script loads from static.ads-twitter.com. It:
- Fires a base page view event on every page load, recording the visit in Twitter's advertising attribution system
- Fires discrete conversion events (purchases, signups, add-to-cart, content views) when the advertiser configures specific event triggers
- Sets the
mucthird-party cookie (up to 2 years) andpersonalization_idcookie to identify browsers cross-site and match visitors to Twitter/X user profiles - Attributes conversions to Twitter ad clicks (click-through attribution window: typically 7 days) or ad impressions (view-through attribution window: typically 1 day)
- Builds website custom audiences for retargeting: lists of users who visited specific pages or completed specific events
- Supports hashed email matching (Advanced Matching) to deterministically link website visitors to Twitter/X user accounts
Embedded Buttons and Widgets
Embedded Tweet buttons, Follow buttons, and Timeline widgets load scripts from platform.twitter.com. These scripts:
- Load on page render even if the visitor never interacts with the button
- Set Twitter tracking cookies in the visitor's browser as a side effect of loading
- Create a cross-site tracking surface for Twitter even on sites that have not intentionally deployed the advertising pixel
Consent & Compliance
- Category: Marketing
- GDPR: Requires consent. The UWT sets persistent cross-site tracking cookies and builds behavioral advertising profiles. IAB TCF purposes: Purpose 1 (Store/access information on device), Purpose 3 (Create personalised ads profile), Purpose 4 (Select personalised ads), Purpose 7 (Measure ad performance). Twitter/X is registered as IAB TCF Vendor ID 21.
- Embedded widgets: Even passive embedded tweet buttons trigger cookie setting and should be consent-gated. Consider using click-to-activate wrappers for social embeds.
- Data transfers: X Corp processes data in the US. EU-US Data Privacy Framework applies. The Irish DPC has investigated Twitter/X under GDPR; a 2022 decision resulted in a €450,000 fine for breach notification failures.
- Cookies set:
muc(3rd party, 2 years),personalization_id(3rd party, 2 years), first-party attribution cookies on the advertiser domain
Should You Block This Without Consent?
Yes — with marketing consent only. Both the UWT pixel and embedded social widgets require marketing consent before loading. Do not fire the UWT for visitors who decline advertising cookies. For IAB TCF deployments, gate activation on valid consent signals for Twitter/X (Vendor ID 21). Note that embedded Tweet buttons will also set tracking cookies — wrap them with a consent-aware activation layer if using social embeds.
Products (1)
Consent Categories
Also Known As
Industries
Tracked Domains (3)
twitter.comMarketingads-twitter.comMarketingtwimg.comSocial MediaFrequently Asked Questions
Does the Twitter Universal Website Tag require consent?
Yes. The UWT sets persistent cross-site tracking cookies (muc, personalization_id, both up to 2 years), builds retargeting audiences, and fires conversion attribution. These activities require explicit marketing consent before the tag loads.
Do embedded Twitter buttons also set tracking cookies?
Yes. Even passive embedded Tweet buttons and Follow buttons load platform.twitter.com scripts on page render, setting tracking cookies as a side effect before any visitor interaction. These should be treated as marketing scripts and consent-gated accordingly.
How does ConsentStack handle Twitter tracking?
ConsentStack classifies Twitter as a marketing vendor and blocks both the UWT pixel and embedded social scripts until marketing consent is granted. For IAB TCF deployments, ConsentStack enforces consent for Twitter/X Vendor ID 21 before any script activates.
Related Vendors
Manage consent for Twitter
ConsentStack automatically detects and manages Twitter trackers so your site stays compliant with global privacy regulations.