Set up your cookie banner and tracker controls

A banner in 45 languages, known-tracker blocking in opt-in, four categories and a preference centre, per-region modes, Google Consent Mode v2, a monthly scan of 10 pages and a 3-month consent log. The paid add-on lifts the limits: weekly scans of up to 30 pages and a 12-month log; the price is in the extensions catalogue.

In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site. For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.

Consent Mode v2, GTM dataLayer events and UET, Meta and Clarity signals are sent. Tags must be configured to handle them; sending a signal does not verify your advertising-account setup.

If enabled and the scan report contains only necessary cookies, the first layer can inform instead of asking. A scan reports what it found on scanned pages and in tested states. It does not prove that other trackers are absent; manually check dynamic elements, category settings and results.

In the scan report, unrecognised cookies have a “✨ Suggest categories with AI” button: the model receives only their names and the page’s list of third-party hosts and proposes one of our four categories, the provider, the purpose and the reason for its choice. The suggestion lands in the declaration as a draft — you can change the category in the select, and nothing applies until you press “Save”. The call is paid and billed to the account’s AI balance; the scan itself still runs on the built-in database, without a model.

The widget lets you configure modes and text for audiences, including Russia. It does not automatically determine whether data processing is lawful; check your site’s terms and selected mode.

The categories the visitor chose and the time of the decision — anonymously, without IP or full user agent. It is a history of decisions rather than a guarantee of compliance: it shows that consent was collected and how it was arranged.

In a separate section of the same widget’s panel: a threshold of 18 or 21, confirmation buttons or a birth-year field, memory from 1 to 365 days (30 by default). The birth year is never stored anywhere, and a refusal is deliberately not remembered. An age question can precede the banner. It is the visitor’s own answer, not identity or document-based age verification, and does not permit restricted-product sales.

For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.You can link the WordPress plugin to an account; standalone mode has no log. Check script order on pages using other plugins too.

The synchronous tag enables early interception, so loading affects the first screen. Configuration, language packs and an enabled age gate need additional files. Test network use and speed on your site; neither a fixed size nor zero load after a decision is guaranteed.

An account, your website domain and permission to insert code. Prepare the selected widget’s data and test your published page. Follow the separate cookie banner instructions for early tracker blocking.

Style isolation reduces conflicts but does not replace testing. Check buttons, forms, mobile layout and other scripts on your site.

Set your own texts separately; built-in labels fall back to English where translations are missing. Core data is stored in the brand’s cloud. Connected AI, telephony and other services have separate processing terms.