X Ads

Overview

X Ads (formerly Twitter Ads) is the advertising conversion tracking and audience building pixel for ad campaigns running on the X platform (formerly Twitter). Advertisers embed the pixel to measure the effectiveness of X ad campaigns by attributing website actions — purchases, signups, page views — back to ad clicks or impressions. The pixel also enables the construction of custom retargeting audiences and lookalike audiences from site visitors.

What This Script Does

The X Ads pixel loads the Universal Website Tag (UWT) from static.ads-twitter.com or analytics.twitter.com. It executes the following tracking operations:

Conversion tracking

• Fires a base pixel event on every page load, logging a page view attributed to X ad traffic where applicable
• Fires discrete conversion events when users complete defined actions: purchases, account registrations, newsletter signups, content downloads, app installs, or custom events defined by the advertiser
• Attributes conversions to X ad clicks (click-through) or ad impressions (view-through) within configurable attribution windows (typically 1-day view, 7-day click)

Audience building

• Sets the muc third-party cookie (cross-site, persistent, up to 2 years) to identify browsers across sites within the X advertising network
• Sets first-party cookies on the advertiser's domain for attribution and deduplication
• Builds website custom audiences: lists of users who have visited specific pages, completed specific events, or taken no action (for exclusion audiences)
• Shares hashed user data (hashed email addresses) with X for deterministic audience matching when the advertiser implements the Advanced Matching feature

Lookalike and behavioral targeting

• Audience data is used to create lookalike audiences on X modeled on converter or visitor characteristics
• Data feeds into X's ad targeting system for interest and behavioral targeting of X users

Consent & Compliance

• Category: Marketing
• GDPR: Requires consent under GDPR Article 6. The pixel sets persistent cross-site tracking cookies and builds behavioral profiles for advertising purposes, which are not covered by legitimate interests. IAB TCF purposes involved: Purpose 1 (Store/access information), Purpose 3 (Create personalised ads profile), Purpose 4 (Select personalised ads), Purpose 7 (Measure ad performance).
• IAB TCF: X (Twitter) is a registered IAB TCF vendor (Vendor ID 21). Consent for X Ads should be captured via an IAB TCF-compliant CMP.
• Data transfers: X Corp is a US company. Data is processed in the US. X participates in the EU-US Data Privacy Framework for EU-to-US data transfers.
• DPA enforcement: X (Twitter) has faced regulatory scrutiny in Europe over data practices. The Irish Data Protection Commission has investigated Twitter/X under GDPR, resulting in fines related to data breach notification and transparency obligations.
• Cookies set: muc (3rd party, up to 2 years), personalization_id (3rd party, 2 years), advertiser-domain first-party cookies for attribution

Should You Block This Without Consent?

Yes — with marketing consent only. The X Ads pixel requires explicit marketing consent before loading. It must not fire for visitors who have declined advertising cookies. Block the pixel entirely until marketing consent is granted. For IAB TCF deployments, X (Twitter) Vendor ID 21 must have valid consent signals before the pixel activates.