PXTA crawls a website in a real browser, three times: with the cookie banner unanswered, after a reject, and after an accept. It records every request each tracker sends and points to the personal data inside. You get evidence for each finding, not a score.
3 passes
Every page loaded with the banner unanswered, after reject and after accept
10 trackers
Meta, Google, TikTok, LinkedIn, Microsoft, Pinterest, Snap and X, plus unknown beacons
500 pages
Crawled with the browser killed at page 167; PXTA restarted it and recorded all 500
Apache 2.0
License for all of the code
From the recorded test results in the code repository.
use cases
Cedar Valley Clinic is a made-up family practice on PXTA’s test fixtures, and its sample report is a common story. The web team set up a Cookiebot banner and wired …
explainers
Almost every ad network now offers a way to send customer details from a website “securely hashed”. Meta calls it advanced matching, Google calls it enhanced …
use cases
Marlow Home Loans, another made-up business from PXTA’s test fixtures, did more than most sites. Its tags really do wait for the cookie banner, a Usercentrics one. …
use cases
Some pixels don’t wait for a site to hand them an email address. They read it off the page. Meta’s automatic advanced matching watches form fields, and when a …
use scenarios
A privacy team usually learns what the website sends from the marketing team’s description of it. That description is honest and almost always incomplete, because …
use scenarios
When an agency takes over a client’s site, it inherits every tag the last three agencies installed. Nobody hands over a list, because nobody has one. The first time …
use cases
Say a small outdoor-gear shop runs a OneTrust cookie banner, Google Analytics, the Meta Pixel on every page, and the Pinterest Tag on its order confirmation page. The …
use cases
Agencies move clients between consent platforms all the time: OneTrust to Cookiebot, a home-made banner to Didomi, one Usercentrics version to the next. The new banner …
use scenarios
Developers rarely add tracking pixels. They add the things that make pixels leak: a confirmation page that puts the email in the URL, a new search page, a redesigned …
If PXTA nearly fits your audit, or a tracker or banner it should know is missing, write in.