free · no signup
X (Twitter) Pixel checker
Check if the X (Twitter) Pixel is installed on your site, spot duplicate or render-blocking loads, and verify conversion events in X Ads.
Scans the page's HTML in seconds. It also reports every other tracking script it finds.
about X Pixel
Why it breaks quietly.
The X Pixel loads from static.ads-twitter.com and is configured with twq('config') and your pixel ID. It records site visits and conversion events for X Ads attribution and audiences.
Many sites still run the older twq('init') base code or conversion events that were never wired up. The pixel loads, Events Manager shows little or nothing, and campaigns optimize without conversion data.
what the free scan checks
Whether X Pixel is in the page
The scan fetches the page's HTML and matches the vendor's script URL and install snippet.
Whether it blocks rendering
A script tag without async or defer delays the page from painting. Marketing scripts never need to.
Whether it's installed more than once
Duplicate installs usually send every event twice and inflate conversions.
How exposed the page is to blockers
A server-side readiness grade: whether tags load from domains blocklists target, and whether conversions have a server-side path.
It reads the HTML, so tags injected later (inside GTM, for example) don't show up, and it can't see events fire. That's what verification is for.
common failures
How X Pixel goes dark.
Conversion events are defined but never sent
Each conversion needs a twq('event') call with its event ID on the right action. If the call is missing, the event shows no activity in Events Manager.
An outdated base code
Older installs use a legacy base code. Check X's current setup instructions to see whether your snippet still matches what Events Manager expects.
The pixel ID belongs to another account
An agency or old ads account's pixel is still on the site, so data goes to an account you no longer use.
The pixel is installed twice
A hardcoded snippet plus a GTM tag, or two base codes from different accounts, can send events twice.
by hand
Check it yourself, step by step.
- 1
In X Ads, open Tools, then Events Manager, and check the status and last activity for your pixel and each conversion event.
- 2
In Chrome DevTools, filter the Network tab for twitter.com or ads-twitter.com while you complete a conversion and confirm a request goes out.
- 3
View the page source and confirm the ID in twq('config') matches the pixel ID in Events Manager.
questions
Asked and answered.
Can this check tell me if X Pixel events are firing?+
No. It reads served HTML and can see whether the X Pixel script is present, duplicated or render-blocking. It cannot see a pixel injected by GTM or confirm events reach X. TracerKit's Verification tier watches real fires and alerts when a tag goes silent.
Is the Twitter pixel the same as the X Pixel?+
Yes. It is the same pixel under X's branding, still loaded from ads-twitter.com.
Why does Events Manager say no recent activity?+
The event call is missing, firing on a page nobody reached, or using an event ID from another account.
check other tags
Know X Pixel is firing, every hour of every day.
Verification watches each tag on real traffic and emails you the moment one goes silent. 14-day trial, no card.