<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pages on pxta.com</title>
    <link>https://pxta.com/pages/</link>
    <description>Recent content in Pages on pxta.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://pxta.com/pages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://pxta.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/about/</guid>
      <description>&lt;p&gt;pxta.com is the home of PXTA, short for Pixel Tracking Audit. It&amp;rsquo;s a free command-line tool that crawls a website in a real browser and writes down what every tracking pixel sends, where it goes, and whether it went before the visitor answered the cookie banner. The report it produces is a list of findings, each one a plain sentence with the request that proves it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-name&#34;&gt;The Name&lt;/h2&gt;&#xA;&lt;p&gt;PXTA is &lt;strong&gt;P&lt;/strong&gt;i&lt;strong&gt;X&lt;/strong&gt;el &lt;strong&gt;T&lt;/strong&gt;racking &lt;strong&gt;A&lt;/strong&gt;udit. &amp;ldquo;px&amp;rdquo; has been shorthand for pixel for as long as screens have had them, from CSS widths to image editors, and a tracking pixel is where this whole kind of tracking started: a one-by-one image, invisible on the page, whose only job was to make the browser call home with some details attached. Today most &amp;ldquo;pixels&amp;rdquo; are scripts, but the name stuck, and marketing teams still talk about &amp;ldquo;installing the pixel&amp;rdquo;. So the tool that checks them borrows the old shorthand, then says what it does: tracking, audited. &lt;a href=&#34;https://pxta.com/pxta-means-pixel-tracking-audit-named-after-the-one-pixel-image-that-started-web-tracking/&#34;&gt;The post about the name&lt;/a&gt; has the longer story.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://pxta.com/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/contact/</guid>
      <description>&lt;p&gt;pxta.com would like to hear from:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Anyone who ran PXTA on a site.&lt;/strong&gt; What it found, what it missed, and what you&amp;rsquo;d want in the report.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Anyone who found a bug.&lt;/strong&gt; A banner it couldn&amp;rsquo;t answer, a tracker it didn&amp;rsquo;t recognise, a finding that&amp;rsquo;s wrong.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Privacy teams, lawyers and agencies&lt;/strong&gt; with an audit PXTA nearly fits.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Write to &lt;strong&gt;&lt;a href=&#34;mailto:info@pxta.com&#34;&gt;info@pxta.com&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Bug reports are also welcome on &lt;a href=&#34;https://github.com/softdevstudio/pxta/issues&#34;&gt;GitHub&lt;/a&gt;. It helps to include what &lt;code&gt;pxta version&lt;/code&gt; prints, your operating system and browser, and the &lt;code&gt;findings.json&lt;/code&gt; of the audit. Please remove any personal data the audited site leaked before you send a report.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Download PXTA</title>
      <link>https://pxta.com/download/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/download/</guid>
      <description>&lt;p&gt;The &lt;code&gt;pxta&lt;/code&gt; command is one file with nothing else to install. It uses the Chrome, Chromium or Edge you already have. Each archive below holds it with its license files, and the links always point to the latest release.&lt;/p&gt;&#xA;&lt;div style=&#34;overflow-x:auto&#34;&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;System&lt;/th&gt;&#xA;          &lt;th&gt;Download&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Linux, x86-64&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/pxta_linux_amd64.tar.gz&#34;&gt;pxta_linux_amd64.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Linux, ARM64&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/pxta_linux_arm64.tar.gz&#34;&gt;pxta_linux_arm64.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;macOS, Apple silicon&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/pxta_darwin_arm64.tar.gz&#34;&gt;pxta_darwin_arm64.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;macOS, Intel&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/pxta_darwin_amd64.tar.gz&#34;&gt;pxta_darwin_amd64.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Windows, x86-64&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/pxta_windows_amd64.zip&#34;&gt;pxta_windows_amd64.zip&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;/div&gt;&#xA;&lt;p&gt;&lt;em&gt;Checksums are in &lt;a href=&#34;https://github.com/softdevstudio/pxta/releases/latest/download/SHA256SUMS&#34;&gt;SHA256SUMS&lt;/a&gt;. Every release is listed on &lt;a href=&#34;https://github.com/softdevstudio/pxta/releases&#34;&gt;GitHub&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;install&#34;&gt;Install&lt;/h2&gt;&#xA;&lt;p&gt;On Linux or macOS:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Quick Start</title>
      <link>https://pxta.com/quick-start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/quick-start/</guid>
      <description>&lt;p&gt;PXTA audits the tracking on a website and writes a report you can read, file or send on. This page takes you from nothing to your first report in a few minutes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-get-pxta-and-a-browser&#34;&gt;1. Get PXTA and a Browser&lt;/h2&gt;&#xA;&lt;p&gt;Download the archive for your system from &lt;a href=&#34;https://pxta.com/download/&#34;&gt;the download page&lt;/a&gt;, unpack it and put &lt;code&gt;pxta&lt;/code&gt; somewhere on your PATH. PXTA drives a browser you already have: Google Chrome, Chromium or Microsoft Edge. Check it&amp;rsquo;s all there:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reference</title>
      <link>https://pxta.com/reference/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/reference/</guid>
      <description>&lt;p&gt;This page lists what PXTA looks for, how it rates what it finds, and every option. The same reference is in the &lt;a href=&#34;https://github.com/softdevstudio/pxta#readme&#34;&gt;README on GitHub&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-three-passes&#34;&gt;The Three Passes&lt;/h2&gt;&#xA;&lt;p&gt;When a site shows a consent banner, PXTA loads every page three times, with a fresh browser profile for each pass:&lt;/p&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Pass&lt;/th&gt;&#xA;          &lt;th&gt;What PXTA does first&lt;/th&gt;&#xA;          &lt;th&gt;A tracker sending data here means&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Banner not answered&lt;/td&gt;&#xA;          &lt;td&gt;Nothing: the banner is left alone&lt;/td&gt;&#xA;          &lt;td&gt;it fired before consent&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;After reject&lt;/td&gt;&#xA;          &lt;td&gt;Rejects on the start page&lt;/td&gt;&#xA;          &lt;td&gt;it ignored the visitor&amp;rsquo;s &amp;ldquo;no&amp;rdquo;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;After accept&lt;/td&gt;&#xA;          &lt;td&gt;Accepts on the start page&lt;/td&gt;&#xA;          &lt;td&gt;this is what the site sends with consent&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;With no banner, each page is loaded once, and the report says the site never asked.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sample Reports</title>
      <link>https://pxta.com/sample-reports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/sample-reports/</guid>
      <description>&lt;p&gt;These are real PXTA reports, made by the release&amp;rsquo;s own tests against four made-up businesses. The sites, the banners and the tags are stand-ins built for testing PXTA, so nothing here describes a real company. Each one is the unedited &lt;code&gt;report.html&lt;/code&gt;, with its &lt;code&gt;findings.json&lt;/code&gt; and &lt;code&gt;requests.har&lt;/code&gt; next to it in the &lt;a href=&#34;https://github.com/softdevstudio/pxta/tree/main/test/results/gallery&#34;&gt;test results on GitHub&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Site&lt;/th&gt;&#xA;          &lt;th&gt;Banner&lt;/th&gt;&#xA;          &lt;th&gt;What the report shows&lt;/th&gt;&#xA;          &lt;th&gt;Story&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/sample-reports/harbor-pine-outfitters/report.html&#34;&gt;Harbor &amp;amp; Pine Outfitters&lt;/a&gt;, an outdoor-gear shop&lt;/td&gt;&#xA;          &lt;td&gt;OneTrust&lt;/td&gt;&#xA;          &lt;td&gt;Tags pasted into the template ignore the banner. The order confirmation page puts the customer&amp;rsquo;s email in its address, and three trackers send it.&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/an-order-confirmation-page-sent-the-customers-email-to-meta-google-and-pinterest-before-the-cookie-banner-was-answered/&#34;&gt;The order confirmation page&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/sample-reports/cedar-valley-clinic/report.html&#34;&gt;Cedar Valley Clinic&lt;/a&gt;, a family practice&lt;/td&gt;&#xA;          &lt;td&gt;Cookiebot&lt;/td&gt;&#xA;          &lt;td&gt;Google Analytics waits for consent. TikTok and LinkedIn don&amp;rsquo;t, and get the condition pages and a search for &amp;ldquo;anxiety medication&amp;rdquo;.&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/a-clinics-condition-pages-went-to-tiktok-and-linkedin-while-google-analytics-waited-for-consent/&#34;&gt;The clinic&amp;rsquo;s condition pages&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/sample-reports/marlow-home-loans/report.html&#34;&gt;Marlow Home Loans&lt;/a&gt;, a lender&lt;/td&gt;&#xA;          &lt;td&gt;Usercentrics, in a closed shadow root&lt;/td&gt;&#xA;          &lt;td&gt;Tags wait for an answer, then load on &amp;ldquo;Deny&amp;rdquo; too. Consent Mode reports granted after the reject.&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/a-lenders-reject-button-loaded-the-ad-tags-anyway-and-google-consent-mode-reported-granted/&#34;&gt;The lender&amp;rsquo;s reject button&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/sample-reports/tidewater-bakery/report.html&#34;&gt;Tidewater Bakery&lt;/a&gt;, a bakery&lt;/td&gt;&#xA;          &lt;td&gt;Didomi&lt;/td&gt;&#xA;          &lt;td&gt;Set up correctly: quiet before an answer, quiet after reject, sends after accept.&lt;/td&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://pxta.com/what-a-correctly-set-up-cookie-banner-looks-like-in-a-pxta-report-from-the-tidewater-bakery-sample/&#34;&gt;The correct setup&lt;/a&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;h2 id=&#34;how-to-read-one&#34;&gt;How to Read One&lt;/h2&gt;&#xA;&lt;p&gt;Start with the tiles at the top: how many findings are high, medium, low and for information. Then read the box under them, which says which banner PXTA found and how it answered it in each pass.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
