# X Pixel conversions that X can count, and page visits inside your app

26 October 2026. Conversions sent to the X (Twitter) Pixel now reach X under the code it counts, whichever form of the ID you pasted, and carry only what X reads. Every move to another page inside your app records a visit with X, and the console checks X conversion IDs as you type and points out conversion labels left blank.

## Improved

- **Tracking:** A conversion sent to X carries only what X reads: the value, currency and items of a purchase, a description, status or search string when your app sets one, and the event ID it uses to drop a duplicate. The visitor's Google and Meta click IDs, UTM tags and your own event fields no longer reach X. From @buildbase/sdk 1.0.0.
- **Console:** Settings > Tracking & tags checks X conversion IDs as you type and refuses a code copied from another pixel's event. Editing a Google Ads, X or LinkedIn tag names the sign-up, trial and purchase events it would not report, and a tag with no conversion labels at all is marked in the list.
- **Tracking:** The Providers page lists the two hosts X sends its data to, t.co and analytics.twitter.com, for a site whose Content-Security-Policy would otherwise block every X hit while the page looks fine.

## Fixed

- **Tracking:** X Pixel conversions are counted. An ID pasted the way X Events Manager lists it, such as o4d5e6, went out without its pixel, so X credited it to nothing; it is now sent as the full tw- code X expects, and a code pasted whole still works. From @buildbase/sdk 1.0.0.
- **Tracking:** X records a page visit each time someone moves to another page inside your app, not only on the first page they load, so an X audience built on pages visited, such as everyone who opened pricing, fills up. From @buildbase/sdk 1.0.0.

Source: https://www.buildbase.app/changelog/x-pixel-conversions
