Skip to main content

X (Twitter) Pixel

What is the X Pixel?

The X Pixel — formerly known as the Twitter Pixel or Universal Website Tag — is a piece of JavaScript that X Ads asks you to install on your storefront. Once it's live, it reports visitor activity and conversions back to your X Ads account so you can measure which Promoted Posts and campaigns actually drive sales, retarget visitors who didn't buy, and build lookalike audiences based on your best customers.

If you're running paid campaigns on X, the Pixel is the only way X Ads can connect an ad click to a conversion on your store. Without it, reports are essentially traffic counts with no conversion attribution.

The Pixel collects the visitor's browser events, IP address, user agent and cookies. It doesn't send personal data from the browser.

How Nevuto handles X (Twitter) Pixel

  • Nevuto injects the official X Pixel (the twq / Universal Website Tag) into every page of your storefront as soon as you save the integration, configured with your Pixel ID.
  • X's own SDK handles all tracking — page views and conversion events are fired directly by the Pixel, not by Nevuto.
  • Conversion events (Purchase, Download, Sign up, custom events) are configured inside X Ads Events Manager. Nevuto only makes sure the base Pixel is loaded so those events can be associated with it.
  • You can disable the integration at any time from the admin panel.

Add X (Twitter) Pixel to your Nevuto store

  1. Log in to your Nevuto admin panel.
  2. Go to Settings → Integrations.
  3. Click the Add button next to X (Twitter) Pixel.
  4. Paste your Pixel ID into the input field.
  5. Toggle the status to Active and click Save.

Done — the X Pixel starts loading on your storefront immediately.

Where to find your Pixel ID

  1. Sign in to ads.x.com with your X advertiser account.
  2. Open Tools → Events Manager (sometimes labeled Conversion tracking).
  3. If you don't have a Pixel yet, click Add event source → Website and follow the setup wizard.
  4. Select Universal Website Tag → Install manually.
  5. In the generated snippet, look for twq('config', '...') — the short alphanumeric string inside the quotes is your Pixel ID.
  6. Copy just the ID (not the full snippet) and paste it into Nevuto's Pixel ID field.

Test that it's working

  • Install the official X Pixel Helper Chrome extension (or the generic Twitter Pixel Helper).
  • Open your storefront in the same browser — the extension should detect your Pixel and show it as firing on every page load.
  • Back in X Ads Events Manager, open your Pixel. The status should change to Active with a "Last received" timestamp reflecting your recent visit within a few hours.
  • Trigger a test event (e.g. a test checkout if you have a Purchase event configured) and watch it appear in the Events Manager activity feed.

Troubleshooting

  • "X (Twitter) Pixel is not configured correctly" on save: the Pixel ID must be 5–20 alphanumeric characters. Paste only the ID, not the full snippet or any quotes.
  • Pixel Helper doesn't detect the Pixel: confirm the integration status toggle is Active in Nevuto and hard-refresh the storefront.
  • Conversions not recording: conversion events are configured inside X Ads Events Manager. For events like Purchase, you may need to push them via twq.event() from your theme's custom code. Nevuto only loads the base Pixel.
  • Ad blockers: X's tracking is blocked by most privacy extensions. Test in a clean incognito window with no extensions.

Related articles