` element The script tag can be replaced with a `

` if you prefer to keep scripts at the bottom. ```html

``` ### Example 5 – light theme ```html ``` ### Example 6 – minimal theme (integrate into any site) The minimal theme has almost no own styling — it inherits the page's font and text color. ```html ``` ## JavaScript API | Method | Description | |--------|-------------| | `cookieScript.accept()` | Accept all categories (or all cookies in simple mode) | | `cookieScript.acceptSelected()` | Accept only the checked categories (categories mode only) | | `cookieScript.reject()` | Accept necessary-only (categories mode) or reject all (simple mode) | | `cookieScript.close()` | Close the banner without changing the stored consent | | `cookieScript.reopen()` | Delete consent cookies and re-show the banner (use in a "Cookie settings" footer link) | ### Consent withdrawal example Add a link anywhere on your page so users can change their preferences at any time (required by GDPR Art. 7(3)). Two equivalent ways: ```html Cookie settings Cookie settings ``` Any element with `data-cw-reopen` is wired up automatically when the library loads. ## Callback The global callback function is called whenever consent is read or updated. ```js function cookieWarnCallback(accepted, categories) { // accepted – boolean: true if any non-required category accepted (or accepted in simple mode) // categories – object or null (null in simple mode) // { necessary: true, analytics: false, marketing: true } } ``` ## Google Consent Mode v2 Google Consent Mode v2 is required for Google Analytics 4 and Google Ads in the EEA. Without it, conversion modelling and cross-channel attribution are degraded and your Google Ads campaigns lose signal. The key difference from a simple callback-based script loader: **always load GA4 / GTM, but start with denied defaults, then update consent in the callback.** GA4 will model conversions even for users who decline, as long as Consent Mode is active. ### Setup ```html ``` ### Consent signal mapping | cookie-warn category | Consent Mode v2 signal(s) | |---|---| | `necessary` (always granted) | `functionality_storage: 'granted'` | | `analytics` | `analytics_storage` | | `marketing` | `ad_storage`, `ad_user_data`, `ad_personalization` | ### Notes - `wait_for_update: 500` gives cookie-warn 500 ms to fire `gtag('consent', 'update', ...)` before GA4 sends its first event. Match this to your `data-delay` value if you change it. - The callback fires on **every page load**, not just on first consent. This is correct — GA4 needs the consent update on every page. - If using **Google Tag Manager**: set the `consent default` call in a Custom HTML tag on the Consent Initialization trigger, before the GTM container fires. - For sites outside the EEA where Consent Mode is not legally required, you can still use it — it improves data quality with modelled conversions. ## Cookies | Cookie name | Value | Description | |-------------|-------|-------------| | `cookieWarn.accepted` | `true` / `false` | Set in simple mode | | `cookieWarn.categories` | `necessary,analytics` | Comma-separated accepted category keys (categories mode) | | `cookieWarn.version` | string | Stored value of `data-version` (if set); used for consent invalidation on version mismatch | | `cookieWarn.timestamp` | ISO 8601 string | UTC timestamp of the last consent action (accept / reject) | All cookies are set with `SameSite=Lax` and `Secure` (on HTTPS). ## AI Parts of this project's code and documentation have been written with the assistance of AI (Claude by Anthropic) since 2026-05-21.