Cookie Manager

The purpose of the Cookie Manager is to make it possible for you to obtain consent to storing and retrieving data using cookies. This is necessary to comply with a number of different EU directives concerning the right to privacy online.

With the Cookie Manager, you can show explicit and granular information to website users about cookies and cookie categories, before asking them to accept one or more cookies. The Cookie Manager is available from Settings > Web & HTTP > Cookie Manager (Figure 1.1).

Figure 1.1 The Cookie Manager

To use the Cookie Manager:

  • Check Enable cookie manager
  • Select either Template based warnings and a Template (recommended) or Custom. You can also select a template at the website level using the cookies button in the Websites app. This will override the template set here.

After seleting the rendering method, use the Settings (Figure 1.2) to configure the Cookie Manager.

Figure 1.2 Managing cookies

You can:

  • Specify the cookie lifetime for the cookie which stores the visitors opt-in choices
  • Check Disable HttpOnly flag on all cookies to disable the HttpOnly flag being set on all cookies – this is not recommended as it presents a possible security threat
  • Mark some of the cookies as secure cookies – these cookies are only set when the website is accessed via https

Finally, you can add custom cookies to the list – this is only necessary if your cookie is set via custom code. Cookies set via our API (using the CookieManager.SetCookie method) are added to the list automatically.

Below the general settings, a selector allows you to mark some cookies as Tracking cookies. If you need more categories (and you typically do), you can create custom cookie categories – see below.

Cookies can be categorized – as e.g. Marketing cookies, Essential cookies, and so on – which makes it possible to group them appropriately in frontend when asking users to opt-in. A category is basically just a label which is created under Settings > Web and HTTP > Cookie Manager > Cookie categories.

Once the category has been created, a new cookie selector is shown in the cookie manager (Figure 2.1). Simply move cookies from the left-hand column to the right hand column to include it in the category. If a cookie is a member of two categories, both must be accepted in frontend before the cookie is set.

Figure 2.1 A selector for a Cookie Category

Here is an overview of some of the cookies set by Dynamicweb:

Cookie name




The date of the last visit to the website

Used to collect statistics


An ID assigned to the visitor by Dynamicweb

Used by statistics to recognize returning visitors


A session-ID of the current visitor

Used to show context dependent information such as shopping carts, logins, etc. Expires 30 minutes after last pageview.