Setting up Real Cookie Banner in a GDPR-compliant way

Real Cookie Banner (devowl.io) is a consent plugin for WordPress developed in Germany. It comes with over 1,500 pre-configured service templates and blocks content via a content blocker — the configuration is still not a self-runner.

Real Cookie Banner relies heavily on pre-built service templates: for common tools such as Google Analytics, Meta Pixel or Hotjar the purpose, legal basis, storage period and opt-in code are already stored. This saves time and reduces errors in the mandatory details. The price is that you rely on the templates being up to date — when the law changes, the plugin update has to be installed.

The content blocker is the second core building block. It replaces embedded content with a preview and a consent button before iframes from YouTube, Google Maps or social platforms load. It is important that the blockers also take effect when embeds were inserted via a page builder such as Elementor or as a Gutenberg block — this can only be verified by testing in a private window.

Real Cookie Banner is a freemium product: the free version covers the basic functions, while TCF 2.2, an extended scanner and priority support are reserved for the Pro version. For a small company site without ad monetisation the free version is usually sufficient, provided the services are maintained cleanly.

Is this a risk?

The service templates cover the detected need, but a scanner only reports what it finds. Scripts from the theme, from custom code or from the tag manager do not appear automatically and have to be created as a separate service. If the entry is missing, the tracker loads despite a rejection — without a legal basis under Section 25(1) TDDDG.

What you can do

• Run the built-in scanner and check every template: is the service really in use, is the category correct?
• For every service that is not detected (theme scripts, GTM tags, custom integrations) create a service with opt-in code manually.
• Enable the content blocker for all embeds (YouTube, Maps, Instagram) and test the visual preview.
• Enable Google Consent Mode v2 in the plugin settings if Google Ads/Analytics is used.

Häufige Fragen

Are the pre-configured templates legally sufficient?

They cover the mandatory details under Article 13 GDPR for standard cases. The specific privacy policy and the actual use of the service still have to be checked yourself.

Does the scanner detect all trackers?

No. It finds what loads during the scan. Theme scripts, tag manager tags and conditionally loaded scripts have to be created as a service manually.

Do I need the Pro version for GDPR compliance?

No. The blocking logic is complete in the free version. Pro mainly adds TCF 2.2 for ad marketers, a more extensive scanner and support.

Does Real Cookie Banner work with Google Consent Mode v2?

Yes, it is enabled in the settings. It adds the consent signals to Google to the script blocking, but does not replace it.

How consentglass helps

The free scan checks the delivered HTML and shows which services are embedded, whether a cookie banner is detected and whether privacy-policy and legal-notice links are present — with context for each finding. It is not a substitute for legal advice.