What a Correctly Set Up Cookie Banner Looks Like in a PXTA Report, From the Tidewater Bakery Sample

Most of PXTA’s sample reports show things going wrong, because that’s where the findings are. This one shows the target. Tidewater Bakery, a made-up bakery from PXTA’s test fixtures, runs a Didomi banner, Google Analytics and the Meta Pixel, and loads both tags only after a visitor accepts.

The report is short. That’s the point.

Quiet, Quiet, Sends

PXTA loaded each page three times. Before an answer: no tracker sent anything. After clicking “Disagree and close”: still nothing. After “Agree and close”: Google Analytics and the Meta Pixel sent their page views. The consent behaviour table shows exactly that, and marks both trackers “respects the choice”.

The site does it with one small pattern. The tags aren’t in the page template at all. The banner’s “accepted” event adds them, and Google Consent Mode is updated to granted at the same moment, so Google’s tags never report a state that disagrees with the visitor.

The One Finding Left

There is one low-severity finding. On the cake-order page, after the visitor accepted, the Meta Pixel read the email field and sent a hash of the address PXTA typed into it. With consent given that’s allowed, which is why it’s rated low. It’s still worth a look. A visitor who clicked “Agree” on a cookie banner probably didn’t expect an address they hadn’t submitted to go to Meta. Turning off automatic advanced matching in Meta’s settings would clear it.

Use It as a Baseline

A report like this is worth keeping. Tags change every time someone in marketing touches the site, and the quickest way to notice is to run the same audit again and compare. If the behaviour table ever shows “fires before an answer” or “ignores reject”, something new was pasted in the wrong place.