The usual way to add a cookie banner: grab a script, drop it into the template, write «We use

cookies» — and leave the tracker code exactly where it was. The visitor clicks «Reject», and by

then the session recorder has already watched them do it. The banner exists on paper; in

practice it is decoration.

EasyCookies moves the trackers out of the template and into the banner's profile. From there the

banner decides when to run them: allow analytics and Metrica starts, refuse and its cookies are

removed. It is built on CookieConsent by Orest Bida, so

the looks, the accessibility and the mobile behaviour are already sorted.

Simple banner or compliance banner

When you create a profile, the component asks which one you need.

Simple. A cookie notice with a «Got it» button and an optional «Reject». Trackers run

immediately. The form holds only the copy, the trackers and the layout.

Compliance. Nothing runs before consent: categories, a preferences modal with a cookie

table, any set of languages with their own copy, revisions and Google Consent Mode v2.

The choice is not final: one button switches the type and nothing you configured is lost.

Which banner a given site needs is decided by the laws that apply to it. EasyCookies is a tool,

not legal advice.

Trackers live in the banner, not in the template

Google Analytics, Google Tag Manager, Meta Pixel, Yandex Metrica (with the session recorder), VK

Ads, and a custom-code slot for everything else. In a compliance banner each service belongs to

a category — analytics, marketing, functionality — its cookies are listed in the preferences

modal, and they are deleted when the visitor says no.

_ym_isad and _ym_visorc are removed.

• Google Analytics — the G-XXXXXXXXXX id; _ga and _ga_* are removed on refusal.
• Google Tag Manager — the GTM-XXXXXXX id.
• Meta Pixel — the pixel id; _fbp is removed.
• Yandex Metrica — the counter number and the session recorder; _ym_uid, _ym_d,
• VK Ads — the pixel id; tmr_lvid, tmr_lvidTS and tmr_detect are removed.
• Custom code — any tags, and you list the cookies to clear behind them.

Move trackers out of templates with one button

On a live site the trackers are already in the template, and often in three different chunks.

«Find on site» searches templates and chunks for their code — both in the database and in

.tpl and .html files — reads out the counter numbers and moves them into the profile.

Tick «Remove their code» and the found `and ` blocks are cut out along with their marker

comments; otherwise the tracker would fire twice. A block that contains anything besides the

tracker is left alone. The previous content of every element is backed up, and «Restore code»

puts it back.

A preview that tells the truth

The banner is rendered right on the manager page, at the edge of the window where it will sit on

the site, and it updates as you type. It runs the very same script the site runs, so the preview

matches the result. So it never covers the form, the editor page shifts away from it: every

field stays reachable.

Layout follows the CookieConsent playground: box, cloud or bar, nine positions, a preferences

modal in the centre or on the side, themes and custom colours.

Consent log

The GDPR asks you not only to collect consent but to prove it. A compliance banner records every

answer — the first one and every later change: the decision, the allowed categories and

services, the profile, the revision, the language, the page, a truncated IP and the user agent.

The consent ID matches the one stored in the visitor's cookie, so it leads to that visitor's

whole history.

On top there is a summary for the period with a daily chart: how many answers, how many accepted

everything, rejected, or picked for themselves. Below are filters and the table; everything

under the filters exports to CSV. Old entries are deleted automatically, by default after a

year. Writing a consent record sets no cookies of its own.

Profiles and contexts

Several banners on one site, one active per context: language versions and subdomains can each

have their own. Duplicate a profile to try changes without touching the site. Export and import

as JSON to carry a profile to another site.

Server-side consent checks

Consent gates more than trackers — embedded video, maps, a reCAPTCHA form. The

EasyCookiesAllowed snippet renders a block only for visitors who allowed the category:

[[!EasyCookiesAllowed? &category=`marketing` &tpl=`youtube` &tplElse=`youtube.stub`]]

When the visitor changes their mind, the banner reloads such a page and the block appears or

disappears at once.

Google Consent Mode v2 and Global Privacy Control

Consent signals are placed right after `` — ahead of any Google tag, including ones pasted into

the template by hand — and the banner updates them once the visitor answers. For a returning

visitor the signals are correct from the first line.

Browsers sending a GPC signal («do not sell or share my data» — Firefox, Brave, DuckDuckGo) get

no marketing services, and see an explanation in the preferences modal. The CCPA requires this.

Output on the site

A plugin renders the active profile's banner on every HTML page — nothing goes into the

template. Individual pages can be excluded via a system setting. If you want to choose the spot

yourself, call the [[EasyCookies]] snippet.

Put the «change your mind» link in the site footer:

<a href="#" data-cc="show-preferencesModal">Cookie settings</a>

For your own scripts the page exposes window.EasyCookies: show(), showPreferences(),

accepted('analytics').

Languages

Ready-made copy in 14 languages: English, Russian, Ukrainian, Belarusian, Kazakh, Uzbek, Tajik,

Armenian, Azerbaijani, German, French, Spanish, Italian, Polish. The banner speaks the language

of the page, and falls back to the profile's default language.

Interface

The component page looks like a native part of the manager in both MODX 3 and MODX 2: the same

tabs, buttons, windows, notifications and colours. No ExtJS in the interface. Lexicons: English,

Russian, Tajik. Plus a «Cookie consents» dashboard widget.