Skip to content

Why does the cookie list need to be kept up to date?

A cookie list should help the visitor understand which cookies the website sets, why they are used and what choices are available.

It is an important part of a transparent and user-friendly consent experience. The visitor needs to receive information about necessary cookies that are set, and be able to make a choice about functional cookies, statistics and marketing.

That is why it is not enough to create a cookie list once and then leave it unchanged. Websites change, and when the website changes, the cookies used on the website may also change.

Websites change over time

New cookies can be added without anyone explicitly thinking, “now we are adding a cookie”.

This can happen when you, for example:

  • add a new form
  • embed video or other external content
  • install a plugin
  • make changes in Google Tag Manager
  • start a new campaign
  • add an analytics or marketing tool
  • change CMS, theme or technical provider

This means that the cookie list needs to be followed up over time.

The cookie list needs to reflect reality

A cookie list is only useful if it reflects the cookies that the website actually uses.

If the list is missing cookies, contains old cookies or describes cookies in the wrong category, it becomes harder for the visitor to understand what happens on the website and what consent is being requested.

An up-to-date cookie list helps the visitor make a more informed choice. It also makes consent management more transparent and helps the website owner see which cookies need to be handled.

The categories need to remain correct

It is not enough for a cookie to be included in the list. It also needs to be placed in the right category.

Necessary cookies need to be separated from functional cookies, statistics and marketing. The website owner should inform the visitor about the necessary cookies that are set. Cookies in the other categories should wait for the visitor’s consent before they are set.

If a cookie is placed in the wrong category, both the information and the technical implementation can become incorrect.

New scripts can affect consent

The cookie list is closely connected to the scripts used on the website.

If a new script is added, it may start setting cookies. You then need to assess what the script does, which cookies it sets and which consent category it belongs to.

Scripts that belong to functional cookies, statistics or marketing need to be conditioned against the right consent category. It is therefore not enough to update the text in the cookie list. The implementation and the information need to work together.

Some cookies only appear during use

Not all cookies are set on the first page load.

Some cookies may only appear when the visitor does something specific, such as submitting a form, logging in, starting a video, completing a purchase or using an embedded service.

That means a simple check of the start page can miss cookies that are used in other parts of the website. The cookie list needs to be followed up with regard to how the website is actually used.

Automatic scanning helps, but does not replace responsibility

Automatic scanning can help detect cookies and keep the information more current.

But the website owner still needs to review the information. This may include assessing what a cookie is used for, whether it is necessary, which category it belongs to and how it should be described to the visitor.

Scanning is a support. It does not replace the need to understand which services the website uses.

Follow-up creates better control

An up-to-date cookie list makes it easier to see when something has changed.

It helps you detect new cookies, review the categories and make sure that scripts are conditioned correctly. It also makes the information shown to the visitor more transparent and current.

When the visitor receives clear and current information, it becomes easier to make an informed choice. This strengthens both consent management and trust in the website.

Summary

The cookie list needs to be kept up to date because websites change.

When new functions, scripts, plugins or third-party services are added, new cookies may appear. The website owner then needs to follow up which cookies are set, why they are used and which category they belong to, so that the visitor receives correct and current information.

A working cookie list should help you:

  • inform the visitor about which cookies are set
  • separate necessary cookies from cookies that require consent
  • keep the categories up to date
  • detect new cookies when the website changes
  • connect the information in the cookie list to the technical implementation
  • condition scripts against the right consent category

A cookie list is not just static text. It is part of consent management and helps the visitor understand what the choice actually applies to. That is why it needs to be followed up when the website changes.

Do you need help reviewing your cookie banner?

CookieTractor helps you handle the cookie dialog, consent, cookie list, documentation and follow-up.

If you are unsure whether your current solution is enough for the requirements you need to consider in the EU or EEA, we can help you review how cookies, consent and scripts work on your website.

Feel free to contact us at info@cookietractor.com.