Cookie Consent Banner Generator.

The banner provides the mechanism GDPR and the ePrivacy rules expect: clear information, a link to the policy, an accept option and an equally prominent reject option, with the choice remembered. Compliance also depends on what your site does with the answer. Non-essential cookies and tags must not be set until the visitor accepts, the policy must describe them, and visitors must be able to withdraw consent. The snippet makes those things possible but cannot enforce them; the generator is a tool, not legal advice.

Wrap the Analytics or Tag Manager code so it runs only inside the consent event. For example: document.addEventListener("cookie-consent", function(e){ if(e.detail === "all"){ /* insert the gtag or GTM snippet here */ } });. Because the banner also fires the event on later visits using the stored choice, returning visitors who accepted still get analytics without seeing the banner again. If you use Google Consent Mode, call gtag('consent','update', ...) from the same listener.

GDPR and UK GDPR require opt-in consent before non-essential cookies are set, so the GDPR style offers Accept all and Reject non-essential with equal prominence and sets nothing until the visitor chooses. The CCPA and CPRA work on an opt-out basis: cookies may be set but California residents must be offered a clear "Do Not Sell or Share My Personal Information" link, which the CCPA style provides, storing "optout" when clicked so you can disable advertising tags. If you serve both audiences, use the GDPR style; it satisfies the stricter rule.

In the browser's localStorage under the key nw-cookie-consent, with the value "all", "essential" or "optout". localStorage has no expiry, so the choice persists until the visitor clears site data or you clear the key. Many regulators suggest re-asking after six to twelve months; you can do that by changing the key name in the snippet when you update your cookie policy, which makes the banner reappear for everyone.

Yes, anywhere you can add custom HTML to the page footer. On WordPress paste it into the theme's footer template or a header-and-footer plugin; Neweb sites, which run on WordPress, accept it the same way. Shopify has a theme.liquid file, Squarespace and Webflow have footer code injection settings, and Wix has a custom code section in site settings. The snippet uses no libraries, so there is nothing to conflict with existing scripts.

Yes. The generated CSS is plain and short; edit the colours, font, padding, border radius or position directly in the snippet. The only requirements are that the element keeps the id nw-cc and the buttons keep their data-cc attributes, which the JavaScript uses. If you add a "Cookie settings" link elsewhere on the site, have it remove the localStorage key and reload the page so the banner appears again.