Pxta on pxta.com

How PXTA Was Tested, From Fourteen Banner Setups to a 500-Page Crawl With the Browser Killed Halfway

Sun, 25 Oct 2026 00:00:00 +0000

A tool that says “this tag fired before consent” has to be right, or its reports are worse than nothing. So PXTA’s tests run real Chrome against real pages, and the results of the release run are kept in the code repository, next to the code they tested. Every number on this site comes from those files.

The run behind version 0.1 used Chrome for Testing 153 on Linux, with Go 1.24.7. All 70 tests and subtests passed. One was skipped by design: the sample report gallery, which the same script runs on its own afterwards.

PXTA Means Pixel Tracking Audit, Named After the One-Pixel Image That Started Web Tracking

Sun, 25 Oct 2026 00:00:00 +0000

PXTA is short for Pixel Tracking Audit. Take the P and the X from pixel, the T from tracking, the A from audit. Say it letter by letter, or “pix-ta” if you prefer. Both work, and the site lives at pxta.com either way.

The X needs explaining, and so does the pixel. “px” has stood for pixel for decades: it’s the unit in every CSS width and every image editor’s ruler, so a developer reads PX and thinks of screens. The pixel part needs a little history, because a tracking pixel was once literally one pixel.

The First PXTA Release Is Out, a Free Command-Line Audit of What Tracking Pixels Send and When

Sun, 25 Oct 2026 00:00:00 +0000

The first PXTA release, version 0.1, is out. It’s a free, open-source command that loads a website in a real browser and writes down what every tracking pixel sends, where it goes, and whether the visitor had answered the cookie banner at the time.

You give it an address. It visits up to 20 pages, three times each if there’s a banner: once with the banner left alone, once after rejecting, once after accepting. Then it writes one HTML report, a JSON file of the findings and the raw capture as a HAR file.