Twitter/X Engagements Used Instead of Conversions
The active events on this X Pixel are all Tweet engagement style metrics (Tweet engagements, Retweets, Likes, Replies) rather than website conversion events. Engagement metrics measure activity on X itself. They do not measure what people do on the site after the click. With no website conversion event configured, campaigns cannot optimise toward Purchase, Lead, SignUp, or any business outcome.
Why It Matters
X Ads supports two parallel measurement surfaces. Tweet engagement metrics come from the platform itself and describe interactions with the ad creative (a Retweet, a Like, a profile visit). Website conversion events come from the X Pixel and describe what the user did after landing on the site (PageView, ContentView, Search, AddToCart, AddToWishlist, CheckoutInitiated, Purchase, Lead, SignUp, Subscribe). Optimising a campaign against an engagement metric tells X to find people who tend to engage with Tweets. That is a different audience from people who tend to convert on a site, and the gap shows up immediately in ROAS once the campaign runs at scale. The account looks instrumented because events are firing, but the events that are firing have no relationship to the business outcome the spend is supposed to produce. The usual cause is a setup that started with engagement objectives, kept the engagement events live, and never added a website conversion event when the goal shifted to performance. The pixel is installed, the JavaScript loads, but the configured event tags in Events Manager are still the engagement set.
How To Fix It
- Decide which website action you want X to optimise toward: Purchase, Lead, SignUp, Subscribe, or another supported event type.
- In Ads Events Manager, create the matching event tag and copy its `tw-XXXXX-XXXXX` ID.
- Wire the tag on the site so the conversion fires with parameters appropriate to the event (`value`, `currency`, `conversion_id`, plus event-type-specific fields).
- Let the event accrue at least the minimum volume X recommends for stable optimisation, typically a few dozen events per week per ad group, before relying on it for bidding.
- Switch any active campaign optimisation goal from the engagement metric to the new website conversion event, and monitor for at least one full learning phase before re-tuning bids.
Example
Active events: Tweet engagements, Likes, Retweets
Missing: Purchase, Lead, SignUp, Subscribe
Campaign optimisation goal: Tweet engagements
Result: bidder targets engagers, not buyers; ROAS sits below baseline.This X Pixel has only Tweet engagement metrics active and no website conversion events configured. Per X Ads Help Center documentation on the X Pixel and conversion tracking for websites, engagement metrics are platform-side measurements of interaction with the ad creative and are distinct from website conversion events such as Purchase, Lead, SignUp, Subscribe, AddToCart, CheckoutInitiated, ContentView, and PageView, which are emitted by the X Pixel on the destination site. Optimising a campaign against an engagement metric tells X to find users who engage with Tweets rather than users who convert on the site, which is a different audience and produces poor ROAS once spend scales. Fix: create the website conversion event that matches the business outcome in Ads Events Manager, wire the corresponding `tw-XXXXX-XXXXX` event tag on the site with the right parameters, let the event accrue volume, and switch campaign optimisation goals from the engagement metric to the new conversion event. Source: business.twitter.com/en/help/campaign-measurement-and-analytics/twitter-pixel.html.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit