Install and switch on the banner

  1. In the menu, under Configuration, click Plugins, find CookieConsent in the App Store and click Install.
  2. Open the app’s settings. If another consent banner is still on, a message at the top names it: keep only one.
  3. Under Collect your visitors’ consent, tick Show the consent banner.
  4. Click Save Changes. The banner shows on your storefront from the next page a visitor opens.

In the same section:

  • Automatic blocking: known trackers wait for consent even when nobody marked them. On by default.
  • Google Consent Mode v2: Google tags follow the visitor’s choice: Google Analytics and Google Ads start in “denied” mode and adapt to the answer, without being held back. On by default.
  • Ask again after: how long a choice is kept, from 1 to 12 months. The CNIL recommends six.
  • Ask every visitor again on their next visit: tick it after adding or changing a tracker, so that everyone answers again.

Hold back the scripts you added

Google Analytics and the Facebook pixel set in your marketplace’s settings already wait for consent. For a script you pasted yourself, in your custom code or in your theme, tell the banner which category it belongs to:

<script type="text/plain" data-cookieconsent="statistics">
  // your script
</script>

The category is preferences, statistics or marketing. The script runs as soon as the visitor accepts it. Scripts already marked for Cookiebot use the same markup and work as they are.

Let visitors change their choice

Add a link to #cookies in your footer, for example “Manage cookies”: a click on it reopens the banner. Show a small button that reopens the banner, bottom left does the same on every page.

Choose the look and the texts

Under Look and texts:

  • Position: Box, bottom left or Bar, across the bottom.
  • Button colour: your brand colour. Refuse all and Accept all share the same style, as the CNIL requires.
  • Title and Message: leave them empty to use the default texts, shown in your visitor’s language.
  • Link to your cookie policy: a page of your site, such as /cookies, or an https:// address.

The Consent log lists every answer to the banner: its Date, the Answer (Accepted all, Refused all or Chose), the Categories accepted, the Page and the Consent ID.

  • A visitor finds their consent ID in the banner’s cookie settings. Type it in the search field and click Find to show their answers.
  • Export the log (CSV) downloads the whole log, for a control or a request from a visitor.

The Cookie declaration is what the banner tells visitors about each cookie, category by category. It fills itself: visitors’ browsers report the names of the cookies your site sets, never their content, and the cookies we know are described at once.

  1. Find the cookies marked To describe.
  2. Choose their Category, then fill in Set by, Purpose and Lasts.
  3. To declare a cookie the banner cannot see, type its name in Add a cookie and choose its category.
  4. Click Save the declaration.

Click Remove on a cookie your site no longer sets.

What your users see

  • Visitors see the banner on their first page: Accept all, Refuse all or Customize to choose category by category. Their choice is kept for the duration you set, then the banner asks again.
  • Under Customize, each category shows its cookies, with who sets them, what for and for how long.
  • An embedded YouTube video, map or social post that waits for consent shows a short notice in its place until its category is accepted.
  • Sellers and buyers signed in see the same banner as any visitor.

Edge cases and limits

  • Not a certified CMP: CookieConsent is not on Google’s list of certified consent platforms and does not use the IAB TCF framework. Google Consent Mode v2 works; ad networks that require a TCF consent string do not read it.
  • Google tags with Consent Mode on: they load before the answer, in denied mode, as Google allows. Switch Consent Mode off to hold them back entirely.
  • Trackers outside the known list: automatic blocking does not hold them back. Mark their tags yourself.
  • Cookies the browser hides: a cookie set by your server for its own use cannot be seen by the banner. Add it to the declaration by hand.
  • Masked addresses: the log stores visitors’ IP addresses masked, and deletes answers after 13 months.