Cookie Consent Banner Generator

Consent is a signal, not a popup

The visible banner is the smallest part of a consent implementation. What matters is what happens to your tags. This tool generates the consent plumbing: the default state your tags start in, the mechanism that blocks scripts until permission arrives, and the events your other code can listen for when a visitor changes their mind.

Google Consent Mode v2

If you run Google Analytics 4, Google Ads or the Floodlight tags, Consent Mode v2 is effectively mandatory for EEA and UK traffic. Rather than blocking Google tags outright, Consent Mode has them load in a restricted state and adjust behaviour based on four signals: analytics_storage, ad_storage, ad_user_data and ad_personalization. The critical detail is ordering. The default command must run before the gtag.js library loads, otherwise the tag briefly operates in granted state and the implementation is invalid. The generated snippet places the default call in the correct position and sets everything except security storage to denied.

Blocking non-Google tags

Consent Mode only governs Google's own tags. A Meta pixel, a LinkedIn insight tag, a Hotjar recording script or an intercom widget will each fire regardless unless you block them yourself. The generated approach converts those into inert script blocks with type="text/plain" and a data-consent-category attribute; the consent library swaps the type and re-inserts the node once its category is granted. That is the same technique commercial CMPs use, without the subscription.

The consent API

The output exposes a small global. window.rdtConsent.get() returns the current category state, window.rdtConsent.open() reopens the preference panel for a withdrawal link, and a rdt:consent-change event fires on the document whenever the state changes so your own code can react without polling.

Test it properly

Load the site in a private window, open developer tools, and check the Application panel before touching the banner. If any non-essential cookie already exists, your blocking is not working. Then accept only analytics and confirm marketing cookies stay absent. Most broken implementations pass a visual inspection and fail this two-minute test.