Documentation

Consent log and cookie declaration

  1. A real browser opens your site
  2. It visits your pages one by one
  3. It finds and sorts the cookies
  4. Your declaration is updated

Every decision is stored with its ID, time, banner version, accepted categories, country, page and an anonymized IP address. Find a visitor by the ID shown in their preferences, or download the log as CSV (Consent log → Export) for an audit.

For the period you pick (7, 30 or 90 days, in UTC), the Consent log also shows:

  • Decision rate: the share of banner views that ended with a choice. A view is counted each time the banner is shown, not per visitor (someone who sees three pages before deciding counts three views). Refusals applied from Global Privacy Control are not banner answers, so they are left out of the rate and shown apart ("of which N via Global Privacy Control").
  • Decisions per day: Accepted all, Custom, Rejected and GPC per day, with the banner views behind them; the same numbers are available as a table.
  • Breakdowns by country, device (phone, tablet, desktop), browser and system, page (address without query string) and banner version, each with the share of "Accept all" and of refusals, so you can compare two versions of the banner. Device and browser are read from the stored user agent; iPads that ask for the desktop site look like Macs.
  • History per visitor: a decision that differs from the visitor's previous one is marked "Changed choice", and each row can show that visitor's earlier decisions. Searching for a consent ID shows the whole history, oldest first.
  • Details: click a row for everything stored about that decision, each category accepted or refused, the Google Consent Mode state it implies (derived from the categories, as bc.js sends it) and when the consent expires (from the consent lifetime of that banner version).

Nothing new is collected for these numbers: they come from the consent records and the banner view counter. The CSV export also has the browser, system, device and GPC columns.

The scanner visits your site each month (and whenever you ask) and fills the cookie declaration shown in the banner preferences:

  • Before consent: it opens the home page as a new visitor and notes what is stored and which other services are contacted before any choice.
  • After "Reject": it clicks your banner's "Reject" button (found like the free website check finds it), opens the page again and notes what is still stored or updated. Anything optional there is flagged "After refusal" in Cookies, in the scan and in the monthly report.
  • After "Accept": in a fresh visit it clicks "Accept" and follows your site's links up to your plan's pages per scan. When it finds no accept button, it grants every category with a BerryCookie consent cookie instead (this works for sites using BerryCookie) and the scan says so.

Cookies shows one row per cookie: the same name and type found on several of your own hosts (for example app.example.com and example.com) is one row with the list of hosts, and editing or removing the row applies to all of them. Each row shows whether it was set before consent or after "Reject", whether it is new since the last scan, first or third party, the storage type and, under Details, when it was first and last seen and the pages that set it. Search by name, provider or domain and filter by category (including Unclassified), party, flag and type; select several rows to set their category at once. Cookies BerryCookie recognises come with a suggested provider and purpose; storage your site sets itself is suggested as "This website". In the edit dialog, "Use the known description" takes BerryCookie's text, which visitors read in all 12 banner languages; for a purpose you write yourself, add translations per banner language (visitors see their language, else the text as written). The lifetime is set as a number and a unit (minutes to years) or as a session cookie; local and session storage have no lifetime ("Until cleared", "Until the tab is closed").

Scans lists every scan with its result. A failed scan says why in plain words (domain not found, server not answering, too slow, blocked by a firewall or bot protection, redirect loop, HTTP error, domain no longer verified…), what to check, and the technical message under "Technical details"; "Try again" starts a new scan with the same limits as "Scan now". A scan's details show who started it, how long it took, the pages visited against the page limit, what ran before consent and after "Reject", what changed since the previous scan (new, no longer found, unchanged), everything found with its number of pages, pages that answered with an error, and JavaScript errors on the home page before consent. Scan settings set the pages per scan (up to your plan), paths to follow only or never ("/shop", "/cart"), extra pages no link leads to (on your own domains) and the day of the month for the automatic scan (1–28, UTC; by default 30 days after the previous scan). The scanner's browser identifies itself as BerryCookieScanner; allow it in your firewall or bot protection if scans are blocked.

After each monthly scan, owners and administrators get the monthly scan report by email, in their language: pages and cookies found, the cookies by category with their provider, the ones not classified yet (with a button to the Cookies page), what changed since the previous scan (new and removed cookies and third-party hosts) and a warning, with how to fix it, when something optional runs before consent or still runs after "Reject". If a monthly scan fails, the email says why and what to check. Scans you start yourself send no email. Each person can turn the report off in Settings → Notifications.

Need help? [email protected]

Ready to put it on your website?

Install it with one line of code, the Google Tag Manager template or the WordPress plugin.

Free for one website, no card. Create an account, add and verify your site, then paste one line of code — about ten minutes.