Documentation
These pages explain how Cookiemark works and how you set it up on your site. They are written for whoever looks after the website, whether that is you or your web developer.
Start here
Most sites are set up in three steps. You add the site in the dashboard, you paste one line into the head of every page, and you publish the banner. The first page below walks you through all three.
After that, read the page on blocking. It tells you which trackers Cookiemark holds back by itself and how you mark the ones it does not recognise. If your site uses Google Analytics, Google Ads or Tag Manager, the two pages about Google come next.
Getting started
Reference
- JavaScript APIRead the choice in your own code, react when it changes, and build your own buttons.
- Cookies and the cookie listWhat the list is for, how you fill it, and the cookie Cookiemark sets itself.
- The consent logWhat each entry holds, how you find one visitor, and the CSV export.
- The scannerHow a scan visits your site, what the report checks, and what it cannot see.
- The APIList sites, read the consent log, look up a consent ID and publish, with an API key.
- Regions and privacy signalsShow the banner in chosen countries only, and respect Global Privacy Control.
Teams and moving over
- Agencies and clientsRoles for your team, a workspace per client, and your own brand in the dashboard.
- Moving from the pluginImport the settings of the CookieConsent WordPress plugin, and what to change after.
- Questions and answersShort answers to the questions that come up most, and a note on the law.