Compliance Reports & Notifications¶

The Waulter dashboard provides compliance reports and notifications to help you maintain GDPR/ePrivacy compliance across your web properties. These reports synthesise information from cookie detection, consent statistics, and configuration health checks.

Compliance status overview¶

Each configuration in the dashboard displays a compliance status indicator:

What compliance reports show¶

Per-configuration health¶

Per-purpose breakdown¶

For each purpose category, the report shows:

• Number of cookies assigned to this purpose
• Consent rate (what percentage of visitors grant this purpose)
• Whether the GCM signal mapping is correct

Historical trends¶

• Compliance status over time (weekly/monthly)
• Changes in detected cookies
• Consent rate trends per purpose

Notifications¶

The dashboard displays notifications when issues are detected:

Interpreting findings¶

Uncategorised cookies¶

What it means: Cookies were detected on your site that are not assigned to any purpose category in your Waulter configuration.

Action: Review each uncategorised cookie:

1. Identify which script sets it (check the detection results for the source).
2. Determine its purpose (analytics, marketing, functionality, etc.).
3. Assign it to the correct purpose category in the dashboard.
4. If the cookie is unnecessary, remove the script that sets it.

Cookies set before consent¶

What it means: One or more cookies are being set before the visitor has given consent.

Action:

1. Check your tag firing order — ensure all non-essential tags use consent triggers.
2. Verify that the Waulter SDK fires on the Consent Initialization trigger (before other tags).
3. Review any inline scripts that set cookies without waiting for consent.

GCM signals not detected¶

What it means: The detection scan did not find Google Consent Mode default or update signals on your page.

Action:

1. Verify useGtm: true is set in your WaulterConfig.
2. Check that the SDK loads correctly (no script errors in the browser console).
3. Ensure your GTM container is published with the Waulter tag.

Acting on findings¶

For developers¶

• Review the cookie detection diff view after deployments
• Ensure new integrations use consent-dependent triggers
• Verify GCM signals in GTM Preview mode

For DPOs / compliance officers¶

• Review compliance reports regularly (weekly recommended)
• Escalate uncategorised cookies to the development team
• Keep legal documents up to date
• Use consent statistics to demonstrate compliance during audits

For agency managers¶

• Monitor compliance status across all client configurations
• Use batch reporting to identify clients that need attention
• Share compliance reports with clients as part of your service

Re-verifying after fixes¶

After addressing findings:

1. Make the necessary changes (update configuration, fix tag firing order, etc.).
2. Wait for the next detection scan or trigger a manual re-scan.
3. Check that the findings have been resolved.
4. Verify the compliance status has improved.