TakesNo

the report

Sample report

Demo report · real scan output · v1 ·

scan 01a179ea

What follows is a real report, produced by a real scan of a site we built for the purpose. We built the demo to ignore the reject choice, so the record shows a divergence; nothing else about it is arranged. The target name is the demo's own; account identifiers and share tokens are removed; the time is kept, because the time is evidence.

Read it the way you would read your own: the five stages in order, the four-state results with their coverage line, then each finding — observation, rule, source, classification. Where the scan could not see, the report says so.

the record

Recorded browser evidence

Browser check report

After Reject, the check recorded requests to tracking services. A request shows that the page contacted the service; it does not show what was sent.

The banner provider was not identified.

Banner layer 1

A Reject control was observed on this layer.

  • Accept All
  • Reject All

Evidence recorded by choice

  • unknown · Cookie · demo_pref_seen · Before a choice
  • unknown · Cookie · demo_pref_seen · After Reject
  • Google Analytics · Cookie · _ga · After Reject
  • Google Analytics · Cookie · _ga_DEMO4TAKESNO · After Reject

Requests in the evidence excerpts

This table shows requests included in evidence excerpts attached to findings. A request missing from these excerpts may still have been recorded elsewhere.

Third-party requests

Company · host and pathBefore a choiceAfter AcceptAfter Reject
unknown · demo.takesno.com/––+
Google Analytics · region1.google-analytics.com/g/collect––+
unknown · demo.takesno.com/consent.js––+
unknown · demo.takesno.com/style.css––+
Google Tag Manager · www.googletagmanager.com/gtag/js––+

What the check recorded

! Needs attention

! Needs attention

Tracking requests after Reject

After Reject, the check recorded requests to tracking services. A request shows that the page contacted the service; it does not show what was sent.

What to do next: Review what sent this request and how it responds to the banner choice. If it should wait for consent, adjust the tag or banner settings, then run the check again.

Technical details

EU_POST_REJECT_002_TRACKING_AFTER_REJECT

post_reject

After Reject, the scan recorded tracking activity.

The scan observed attributed tracking network activity or a classified tracking pixel in requests made after the reject action. These are captured forms of activity within Article 5(3)'s technical scope.

? Worth a look

? Worth a look

No Google consent update after Accept

After Accept, the check saw no consent update sent to Google tags, so those tags may not learn the choice.

What to do next: Check that the banner tool's Google Consent Mode setting sends an update when a visitor accepts.

Technical details

EU_GCM_006_NO_CONSENT_UPDATE_AFTER_ACCEPT

state_unattributed

No Google Consent Mode consent update observed after the accept interaction: consent_update_detected=false

The scan interacted with the consent banner's accept control and then observed no Google Consent Mode consent update; the Google consent-mode source records the update call as the mechanism by which a consent platform communicates the user's choice to Google tags, so no update after an accept means the recorded choice was not signalled on this page load.

? Worth a look

No saved consent record after Accept

After Accept, the check found no consent cookie, no consent entry in local storage and no change in Google's consent state.

What to do next: Check that the banner tool saves the visitor's choice, and look at its storage settings.

Technical details

EU_GCM_012_CONSENT_NOT_PERSISTED

state_unattributed

No consent-persistence mechanism observed after the accept interaction: gcm_consent_persistence=none_detected

The scan interacted with the consent banner's accept control and then found no consent cookie, no consent entry in local storage and no change in Google's internal consent state; the Google consent-mode source records that consent mode does not itself save consent choices, so with no platform-side persistence the recorded choice is not carried beyond this page load.

? Worth a look

Cookies set after Reject

After Reject, the check recorded cookies that were not there before and are not strictly necessary. Cookies recognised as strictly necessary, such as the one that remembers the banner choice, are not counted.

What to do next: Find which tool sets these cookies after Reject and whether it listens to the banner choice. If it should not run after Reject, adjust its settings, then check again.

Technical details

EU_POST_REJECT_001_CONSENT_NOT_RESPECTED

post_reject, pre_consent

Non-exempt post-reject cookie additions observed: count=2

The scan observed non-exempt cookies added after the reject action; this indicates storage activity continuing after a recorded reject signal per the Article 5(3) source.

– Not observed

No findings in this group.

Not used on this site

4 checks do not apply to this site.

Could not determine

4 checks could not be split by reason in this saved report.

Extras and technical record

Report version 1. 9 evidence records.

This report contains technical evidence only.

scan 01a179ea

one scan