Skip to main content
The X Pixel records site visits for X Ads. Conversion events are optional: you create each event in X Ads Events Manager, then map its event ID in Replo. The pixel uses Replo’s consent layer. When cookie consent is enabled, it waits for marketing consent by default. Off mode does not request consent; an external consent manager still controls tracking if configured.

​
Add the X Pixel

You can add the pixel in chat or in Site settings.

​
Add it with Replo

Give Replo your Pixel ID and ask it to add the pixel, then publish.
If you also have conversion event IDs from X Ads Events Manager (tw-<pixel ID>-…), include them in the same request. Replo maps only the events you provide.

​
Add it in Site settings

  1. Open the Site Builder.
  2. Open Settings in the top bar and choose Site settings.
  3. Select the Scripts & Pixels tab and click X Pixel.
  4. Paste the pixel ID from X Ads → Tools → Events Manager (the value in twq('config', '…') in your base code).
  5. Click Connect.
  6. Publish your site to make the pixel live.
If this site’s SDK is older than X Pixel support, Replo asks you to update the site’s @replohq/sdk first and does not change your scripts. Add the pixel after that update.
Add the pixel only once. If Google Tag Manager, Elevar, or Segment already fires X, skip connecting it here. If the site already loads static.ads-twitter.com/uwt.js as custom code, reuse that pixel ID and remove the old tag so visits are not counted twice.

​
Map conversion events

The pixel ID alone records site visits and landing page views. To count conversions, create each event in X Ads Events Manager, then paste its event ID.
  1. Open X Pixel in Scripts & Pixels after it is connected.
  2. Under Conversion events, paste an event ID for each event you want Replo to send. Leave a field blank to skip that event.
  3. Click Save events.
  4. Publish your site to make the updated event mappings live.
Event IDs look like tw-<your pixel ID>-abcde. An ID from a different pixel is rejected.
  • Page view: landing page and in-site page changes, after consent allows tracking
  • Product view: a visitor opens a product. X has no product-view type; use a Custom event
  • Add to cart: a visitor adds a product to the cart
  • Checkout started: a visitor starts checkout. X has no checkout type; use a Custom event. Skipped when Shopify hosts checkout
  • Purchase: only when your site reports the order. Skipped when Shopify hosts checkout; use X’s Shopify app for those purchases
Catalog matching for Dynamic Product Ads is not supported.

​
Finding your Pixel ID

  1. Log in to X Ads.
  2. Open Tools, then Events Manager.
  3. Your Pixel ID is the value in twq('config', '…') in the base code.

​
Shopify checkout

When Shopify hosts checkout, Replo does not send checkout or purchase events from the site. Use X’s Shopify app for those purchases, and keep the same pixel ID in Replo and in Shopify.