Note
This is a cached result from 18 Sept 2026. A new scan will be available on 16 Oct 2026.

washingtonpost.com

140.9s 18 Sept 2026
Verdict

1 finding · 2 warnings · 6 checks passed

Advertising assessment: Non-Compliant Grade B
80% Technical score

Vendors

8
Google Tag Manager functional
GTM-WHNNX8B
Compliant

Violations

5
Critical
New tracking cookies were created after consent was rejected GCM_005

Cookies: _fbp

Ensure no tracking cookies are set when consent is denied.

Critical
Consent Mode does not update in place after the consent choice GCM_008

Affected: broken

Call gtag('consent', 'update') immediately after the visitor's choice, with the correct values for both accept and reject. Do not rely on a page reload: it creates duplicate pageviews and breaks session attribution.

Critical
Non-compliant tracking after consent was rejected GCM_010

Affected: Google Analytics 4, Meta Pixel, Google Universal Analytics

After a rejection the affected vendors must stop setting identifiers and sending measurement, or run only in a verified cookie-less mode.

Warning
Consent Mode default is missing GCM_001

Call gtag('consent', 'default') with denied values before GTM or GA4 loads, so the initial consent state is explicit.

Warning
Consent state was not updated after the banner choice GCM_003

Make both the accept and the reject button update the consent state through the GTM Consent API or gtag('consent', 'update').

Overview

Consent Banner Exists 15/15
Consent Banner Functional 10/10
Reject Option Available 10/10
No Tracking Before Consent 20/20
Consent Mode Implemented 7.5/15
Consent Mode Correct States 2/10
No Tracking Cookies Before Consent 10/10
Consent Persists Correctly 5/5
No Tracking After Reject 0/5

Consent Mode

Consent Mode Implemented
Has Default Values
Updates on Accept
Updates on Reject
Persists Across Pages
GCS Configuration Valid

Have your measurement monitored every day.

Create a free project for permanent results, scheduled monitoring, and email alerts.

Get Full Access
Back to homepage