Cookie Consent Manager for Site app

More than a cookie banner — real script control before consent

Cookie Consent Manager keeps managed analytics and marketing services unloaded until the visitor grants the corresponding category. It helps website owners implement transparent cookie and personal-data workflows with consideration for Russian Federal Law No. 152.

Why a basic notification is not enough

A notification may appear only after an analytics counter or advertising pixel has already loaded and sent data. Cookie Consent Manager controls when managed services start: optional code remains inactive until the visitor makes a choice.

• Accept all grants every available category.
• Reject optional keeps only necessary cookies enabled.
• Settings opens a granular category selector.
• The saved decision can be changed or withdrawn later.

Consent categories

Each category can have its own name, description and availability. The Necessary category is protected from being disabled.

Yandex Metrika, GA4 and Google Tag Manager without pasted code

Built-in integrations let an administrator enter a service ID and assign its consent category:

• Yandex Metrika with standard counter options;
• Google Analytics 4;
• Google Tag Manager;
• Google Consent Mode v2.

For Google Consent Mode v2, the initial analytics_storage, ad_storage, ad_user_data and ad_personalization signals are set to denied and updated after the visitor's choice.

If analytics is already installed: disable the old code in the theme, application settings or another plugin, then enable one managed copy in Cookie Consent Manager. Existing executable code cannot be stopped retroactively, and duplicate counters may produce duplicate statistics.

Custom services and scripts

Add any third-party service, specify its name, category, insertion position and code. The plugin activates it only after its category is granted. Real script elements are created without using eval().

Code that must remain in a theme can use the declarative format:

<script type="text/plain" data-consent="analytics">
    // Analytics code
</script>

Inline code and external files specified with src are supported.

No-code design builder

Choose the Minimalism, Classic or Modern visual preset and configure the banner:

• top or bottom bar;
• card in any screen corner;
• required modal window;
• background, text, accent and border colors;
• width, padding, spacing, radius, shadow and font size;
• button height, style and row or column layout;
• page overlay and opacity;
• entrance animation.

The live preview displays the banner, granular settings and reopen control on desktop and mobile screens. Advanced users can add Custom CSS, which is loaded on the storefront after the plugin's base stylesheet.

Reopen and change consent

After consent is saved, the plugin can display a floating button, text link or square cookie icon. Configure its screen corner, icon color and icon size. The built-in control can also be disabled in favor of the JavaScript API.

Consent Log and CSV export

The optional log records explicit visitor actions only:

• accept all;
• reject optional cookies;
• save granular preferences;
• reset consent.

Each record contains the date and time, action, selected categories, policy version, Webasyst settlement, anonymized IP address and SHA-256 session hash. IPv4 addresses are masked to /24 and IPv6 addresses to /48; the original session identifier and full IP address are not stored. Records can be viewed in the backend and exported as CSV. Ordinary page views do not create log entries.

Policy versioning

Increase the consent version after changing the privacy policy or service composition. Visitors with an older version will be asked to make a new choice. Regular design changes and settings saves do not invalidate existing consent.

Works across Webasyst applications

The plugin is installed for the Site application, but a separate Site settlement is not required. The global frontend hook can automatically connect it to Shop-Script, Site, Blog, Hub, Photos, WCMS and other applications when the theme uses the standard {$wa->head()} call.

The Check and installation tab analyzes domains, settlements and themes in read-only mode. It reports whether automatic output works for each route and whether a theme adjustment is required. When the standard hook is missing, the interface provides an exact instruction and fallback helper.

Multiple domains and settlements

Use global defaults or overrides for individual settlements. Consent can be scoped to the current settlement or the complete first-party domain, allowing one visitor choice to work across applications on the same website.

Texts and multilingual websites

Configure the title, message, action labels, policy link, category names and descriptions. Multilingual websites can use separate settlement or locale overrides.

Lightweight and dependency-free

• Consent is read from first-party browser storage.
• No backend request is required on every page view.
• A server request is sent only after an explicit action and only when the Consent Log is enabled.
• The storefront engine uses compact JavaScript without jQuery or a heavy frontend framework.
• Third-party integration errors are isolated and should not stop the storefront.

Webasyst UI 1.3 and UI 2.0

The administrative interface supports both Webasyst UI versions. Business logic and settings remain shared, while controls use presentation appropriate for the selected backend UI.

Developer tools

• Custom CSS;
• declarative data-consent scripts;
• waBrconsent.has(), openSettings(), getConsent() and reset() methods;
• waBrconsentReady and waBrconsentChanged events;
• a manual helper for non-standard themes.

Important: Cookie Consent Manager is a technical consent-management tool. Compliance with 152-FL also depends on the connected services, processing purposes, website configuration and the contents of the website owner's privacy policy.