<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Consent on pxta.com</title>
    <link>https://pxta.com/tags/consent/</link>
    <description>Recent content in Consent on pxta.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pxta.com/tags/consent/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Checking a Cookie Banner Migration With Two PXTA Audits, One Before the Switch and One After</title>
      <link>https://pxta.com/checking-a-cookie-banner-migration-with-two-pxta-audits-one-before-the-switch-and-one-after/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/checking-a-cookie-banner-migration-with-two-pxta-audits-one-before-the-switch-and-one-after/</guid>
      <description>&lt;p&gt;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 gets tested by clicking it. The tags behind it usually don&amp;rsquo;t, because nobody has a list of what the old setup was doing in the first place.&lt;/p&gt;&#xA;&lt;p&gt;Two PXTA audits make that list and check it.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pxta.com/images/three-passes.png&#34; alt=&#34;PXTA&amp;rsquo;s three passes: with the banner unanswered Google Analytics is quiet while the Meta Pixel and TikTok Pixel send; after reject only the Meta Pixel still sends; after accept all three send.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>What a Correctly Set Up Cookie Banner Looks Like in a PXTA Report, From the Tidewater Bakery Sample</title>
      <link>https://pxta.com/what-a-correctly-set-up-cookie-banner-looks-like-in-a-pxta-report-from-the-tidewater-bakery-sample/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/what-a-correctly-set-up-cookie-banner-looks-like-in-a-pxta-report-from-the-tidewater-bakery-sample/</guid>
      <description>&lt;p&gt;Most of PXTA&amp;rsquo;s sample reports show things going wrong, because that&amp;rsquo;s where the findings are. This one shows the target. Tidewater Bakery, a made-up bakery from PXTA&amp;rsquo;s test fixtures, runs a Didomi banner, Google Analytics and the Meta Pixel, and loads both tags only after a visitor accepts.&lt;/p&gt;&#xA;&lt;p&gt;The report is short. That&amp;rsquo;s the point.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pxta.com/images/usecase-bakery.png&#34; alt=&#34;The Tidewater Bakery sample report: no high or medium findings, and a consent behaviour table where Google Analytics 4 and the Meta Pixel are quiet before an answer, quiet after a reject, and send data after accept, marked &amp;ldquo;respects the choice&amp;rdquo;.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>What a Tracking Pixel Sends Before You Click Accept, One Request at a Time</title>
      <link>https://pxta.com/what-a-tracking-pixel-sends-before-you-click-accept-one-request-at-a-time/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/what-a-tracking-pixel-sends-before-you-click-accept-one-request-at-a-time/</guid>
      <description>&lt;p&gt;A tracking pixel is a small piece of code an advertising or analytics company gives a website. The site pastes it into its pages, and from then on every visitor&amp;rsquo;s browser reports to that company. Meta, Google, TikTok, LinkedIn, Microsoft, Pinterest, Snap and X all have one. A typical shop runs several.&lt;/p&gt;&#xA;&lt;p&gt;What the pixel reports is decided by the pixel and by how the site set it up. The visitor never sees it. Here is what&amp;rsquo;s actually in one of those reports, and why it matters when it goes out before anyone clicks &amp;ldquo;Accept&amp;rdquo;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
