Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. Privacy
  3. The consent signal says denied, the tags behave as granted

Privacy audit

The consent signal says denied, the tags behave as granted

7 checks · 5 findings · scope: page

Audit id: privacy.conflict.consent_signal_vs_tags.

Checks

  • Consent denied but identifiers still sent denied_state_but_identifiers_sent
  • No default consent state before tags load no_default_state_set_before_tags_load
  • Browser privacy signal ignored privacy_control_signal_ignored
  • Consent string says no but vendor called consent_string_says_no_but_vendor_called
  • Signal differs between tag manager and banner signal_differs_between_tag_manager_and_banner
  • Vendor reads device before consent check vendor_reads_device_before_checking_consent
  • GDPR flag set but device data read gdpr_flag_set_but_device_read

Findings

  • The banner and the tag manager hold different consent states after the same choice
  • The consent signal says denied and requests still carry identifiers
  • The consent string records no consent for a vendor and the page calls that vendor
  • The Global Privacy Control signal is sent and advertising requests go on as before
  • A vendor reads the device before it asks the consent tool, or while it knows EU law applies

What this relies on

The signal reflects the visitor's choice; the tag is misconfigured.

How to verify by hand

The ad or analytics platform's consent diagnostics.

  • All audits
  • About sus.bot
  • Open the app
  • Contact support