Consent banner

The consent banner editor controls the copy, colours, font, and position of the cookie consent banner your visitors see. You configure one banner per site, from that site's Consent settings, and it is delivered to your pages by the cookie consent script you install on the site. The editor is split into four cards: Copy, Style, Font, and Behavior.

Opening the editor

The banner is configured per site. Open a site's detail page, find the Consent banner card, and click Configure. That opens the site's consent settings on the Banner tab; a sub-nav along the top switches between Banner, Scripts, and Cookies.

When a site has no saved banner configuration, the editor loads a set of defaults. The first time you save, Analytics writes a new configuration row for the site; saving again updates it in place.

Copy: headline, body, and button labels

The Copy card holds the text on the banner:

• Headline: the banner title. Defaults to "We value your privacy." Up to 512 characters.
• Body: the explanatory paragraph. Defaults to "We use cookies to improve your experience. You can choose which categories to allow." Up to 2048 characters.
• Privacy policy URL: the address the banner's privacy-policy link points to. Accepts a URL up to 2048 characters.
• Accept button, Decline button, and Preferences button: the three button labels, defaulting to "Accept all," "Decline," and "Preferences." Each label is capped at 128 characters.

Style and font

The Style card sets four colours, each with a colour wheel and a hex text input that stay in sync: Banner background (default #ffffff), Banner text (default #111111), Button background (default #000000), and Button text (default #ffffff).

The Font card takes raw CSS values. Font size accepts a CSS length such as 14px or 1rem and defaults to 14px. Font family takes a CSS font-family value such as 'Inter', sans-serif and defaults to inherit, which uses your site's own font.

Behavior: position and where the banner shows

The Position selector offers three options: Bottom (the default), Top, and Center (modal).

The GDPR / CCPA zones only toggle limits where the banner appears. It is off by default, so the banner shows to every visitor. When you turn it on, the cookie consent script checks the visitor's resolved timezone against a built-in list of covered jurisdictions.

What the categories mean

Visitor consent is granted or declined per category, not as one yes-or-no choice. Analytics defines four:

• Necessary: cookies required for the site to function, such as session management, security tokens, and load balancing. Always on; visitors cannot decline it.
• Analytics: page views, session duration, referrers, scroll depth, and form interactions. No personal data is shared with third parties.
• Marketing: ad-platform attribution (for example Google Ads or Meta Pixel) and retargeting. GDPR jurisdictions require explicit opt-in.
• Personalization: visitor preferences such as language, theme, and previously dismissed messages, remembered across sessions.

These four categories are what the script catalog gates against: each registered script names one category, and the visitor's banner choice for it decides whether the script loads. Run a cookie scan to see what is running on your site today and how it lines up with your registered categories.

Every consent decision a visitor makes is written durably to your account's consent records, rather than inferred after the fact from the sampled event stream, so you have a record of exactly what a given visitor agreed to.

Saving and when changes apply

Click Save banner config to persist your changes; the editor confirms with "Banner config saved." If a save fails, an error appears in red, with the fallback message "Failed to save banner config." Cancel returns to the site detail page without saving.

The banner configuration reaches your pages through the consent script, so a saved change applies on the visitor's next page load. The editor has no live preview: load your site in a fresh browser session to see the update.