Skip to main content

Cookie Manager

The Cookie Manager lets you design the consent banner for each of your websites and keep an inventory of the cookies each site uses, all from the dashboard. The hosted widget picks up your settings automatically; there is nothing to change in your page code beyond the usual widget snippet.

One banner per site​

Register each website in the dashboard (www.example.com, or *.example.com to cover every subdomain). The widget works out which site it is running on and shows that site's banner. A site with no banner of its own gets your default banner. Until you publish a banner, the widget keeps its built-in look.

For each site you can set: layout (bar, corner box or centered popup), position, colors, corner radius, font, logo, button labels, whether Reject appears on the first screen, whether purposes are listed on the first screen, how long a decision lasts before the visitor is asked again, and which notice group the site shows. Changes are saved as a draft and only go live when you publish.

tip

Keep Reject on the first screen. Regulators treat a banner where rejecting takes more clicks than accepting as a dark pattern, and the dashboard warns you if you turn it off.

By default a visitor's decision applies only to the site where they made it. To share one decision across several of your sites, put them in a consent group in the dashboard. Sharing needs a common visitor identifier from your own site (for example the logged-in user ID), since a browser cannot share storage between domains.

Every consent record stores which site collected it, which page, and how: through the cookie banner or the preference center. It also stores which version of your banner the visitor saw. These appear in the consent records screen, the consent report, and exports.

Visitors are not registered until they decide​

The widget does not create a data principal when a page loads. A principal is created the first time the visitor accepts, rejects or saves their preferences.

The widget reports the names of cookies and storage keys it sees in a visitor's browser (never their values), at most once a day per browser. They appear in the dashboard under the site:

  • Cookies that match a built-in database of well-known cookies (Google Analytics, Meta, Hotjar and others) are pre-filled with provider, description and duration. If your notice has a matching purpose, they are approved automatically.
  • Everything else waits for you to review it and pick a purpose.
  • Third-party cookies the page cannot see can be added by hand.

Approved cookies are listed under their purpose in the preferences panel, and the widget removes them automatically when the visitor declines that purpose. A cookie with no purpose is treated as strictly necessary and is never removed. You no longer need data-cookie-names for cookies you have declared in the inventory.

Global Privacy Control​

If a visitor's browser sends the Global Privacy Control signal, the widget keeps non-essential purposes off until the visitor chooses otherwise, and tells them so. You can turn this off per banner in the dashboard.

Turn on Block known tracking scripts until the visitor agrees in the Banner step and add data-auto-block="true" to the widget tag. The widget then holds back well-known trackers (Google Analytics, Meta Pixel, Hotjar, YouTube embeds and similar) until the visitor allows the matching purpose, so you don't have to tag each script. A tracker is matched to the purpose its cookies are assigned to in the cookie inventory, or otherwise to the purpose whose code reads like analytics, marketing or functional. A tracker with no matching purpose stays blocked.

Keep the widget script first in <head>. Blocking is best effort:

  • A script the browser has already started running can't be stopped.
  • A held-back script or embed can still be downloaded by the browser before the widget reaches it. It does not run, set cookies or track the visitor until they agree. To stop the download as well, mark the tag by hand with type="text/plain" data-consent-purpose="...".
  • Cookies that were set before the visitor decided are removed once their purpose is declined.

Turn on Send Google Consent Mode signals and add data-google-consent-mode="true" to the widget tag. Google tags start in the denied state and are updated with each visitor decision: analytics purposes control analytics_storage, marketing purposes control ad_storage, ad_user_data and ad_personalization, and functional purposes control functionality_storage and personalization_storage. An explicit data-consent-mode-map still overrides this mapping.

Put <div data-bytemonk-cookie-declaration></div> on the page where the list should appear. The widget fills it with your approved cookies grouped by purpose, so it stays current as you approve more.

Automatic rescans​

Each website can be rescanned automatically every week or every month (Websites step). The last result is shown next to the website. A scan opens up to 25 pages of the website in a real browser, the way a first-time visitor would, without accepting the banner. It runs the pages' JavaScript, so it also sees cookies that scripts create, tags loaded by a tag manager, and links in single-page apps. It stays on your website, never follows a page to another site, and refuses internal addresses. It does not log in, so pages behind a login are found as visitors browse. A scan stops opening new pages after about a minute, so it can take up to two minutes. If the scanning browser is unavailable (for example on a server without it), the scan falls back to reading the pages without running JavaScript and says so in its result.

Results​

The Results step shows, per website and period, how often the banner was shown and how many visitors accepted all, rejected all or chose their own settings. Only counts are kept; nothing identifies a visitor.

Compliance check​

The top of the Banner step lists what regulators and DPDP expect of a consent banner, judged on what visitors of that website will actually get (its own settings over the default banner's). It is advice; nothing blocks a publish. It flags:

  • Reject All hidden on the first screen, which is treated as a dark pattern (DPDP section 6(4): refusing must be as easy as accepting). This is the only one shown as an error.
  • Reject drawn less prominently than Accept. By default both buttons look the same; the "Draw Reject like Accept" switch turns that off.
  • No Privacy Policy link (set it in CMP Settings → Legal Links). The rights and Data Protection Board links there are optional and not checked.
  • Auto-blocking off, Global Privacy Control ignored, and consent that never expires or lasts more than a year.

The check uses the saved draft, so save to refresh it after a change.

  • Translated labels: the Banner step lets you word the four buttons differently for each notice language.
  • Version history: every publish keeps a copy. Load an older version into the draft and publish it to roll back.
  • Consent cookie: the visitor's choice is also saved in a first-party cookie, bytemonk_cmp_consent, holding only purpose codes and yes/no. Set a consent cookie domain (for example example.com) to share one choice across your subdomains, and your own server can read the cookie on every request.

The Privacy Policy, Cookie Policy and Terms of Service links you set in CMP Settings apply to every website by default. If a website has its own page for any of them, open CMP Settings → Legal Links, find that website under "Links for a specific website" and enter it; the banner on that website then shows its own link and falls back to the organisation-wide link for any you leave empty. The links come back with the notice from the notice API, so a custom banner or mobile app built on the API gets them too (pass host if the request has no browser origin). Only full http:// or https:// addresses are accepted. The privacy policy version label, which asks visitors for consent again when it changes, stays organisation-wide.

Language switcher​

When the notice has more than one language turned on (Notices and Purposes in the dashboard), the banner shows a globe and a language list at the top. Each language appears in its own script next to its English name, for example "हिन्दी (Hindi)", so visitors can find theirs. The choice is remembered on that browser. With only one language turned on the switcher stays hidden. Button labels can be translated per language in the Banner step.