If your Consent Mode cookie scanner still reporting tracking without consent, the issue typically stems from an incorrect implementation. Many website owners assume that a cookie banner alone is sufficient. However, Google Consent Mode v2 must also be properly configured so that all tags only fire after the user grants permission. Furthermore, third-party scripts loaded outside the Tag Manager can also cause these alerts.

Why the Consent Mode Cookie Scanner Still Reporting Tracking

In most cases, the problem arises because certain scripts are embedded directly in the source code and therefore bypass the Consent Mode entirely. As a result, cookies are set before the user has made any decision. Additionally, the default status of consent parameters may not be set to ‘denied’. Consequently, Google interprets the missing configuration as implicit consent. You can find more details in our FAQ about cookies before consent.

Third-Party Scripts as a Common Error Source

Moreover, many websites load external scripts such as Facebook Pixel, Hotjar, or chat widgets without using Google Tag Manager. Therefore, these scripts are not captured by Consent Mode. As a result, the cookie scanner continues to report tracking without consent. Google consequently recommends managing all marketing tags through the GTM. Further details are available in the Google Consent Mode documentation.

Our Recommendation

We recommend first migrating all scripts into Google Tag Manager. Afterwards, you should set the default consent status to ‘denied’ and correctly forward consent signals from your CMP to the GTM. In addition, it is advisable to run regular cookie scanner checks to detect new violations early. This way, you ensure that your Consent Mode cookie scanner still reporting tracking issues are fully resolved.

Conclusion

In summary, a properly configured Consent Mode forms the foundation for GDPR-compliant tracking. If you need assistance with the setup, contact us for a professional analysis.