Frequently Asked Questions

Cookies raise many questions. Here we try to give answers to the ones we get about CookieTractor and cookies in general.


Why does the cookie question block the entire website? Is it not enough with a list?

There are several reasons why a blocking cookie query is better than simply displaying a list that the user does not need to decide on to interact with the website.

Previously, it was common to have a list at the top or bottom of the page, which only informed that the page sets cookies, but without a choice to control which cookies are set. This is not enough to comply with the legislation; you must not save data on the device before you have collected consent to this.

There are also cookie consent solutions that present cookie choices to the visitor in a list. This is clumsy and disturbing for users that do not make a choice. It is also in the website owner's interest to get the consent of which cookies the visitor accepts before interacting with the website – statistics and marketing functions cannot otherwise be activated. It is easier to consider the loss of visitors who only accept the necessary cookies if you know how large that proportion is of all visitors, which is otherwise unknown.


Instead of "Only Necessary", can you have "Settings" with more choices?

Under the law, it must be as easy to limit your choices as it is to accept all. If the visitor needs to click Settings and then choose to restrict the consent, it is not as easy as accepting all. Therefore, we have chosen not to have this option.


Does CookieTractor support Cross Domain Consent?

Cross-Domain Consent or Bulk Consent means that the same consent is valid on multiple domains. CookieTractor supports this for subdomains to the main domain.

To support Cross-Domain Consent between different main domains requires a third-party cookie to be placed and read from all connected domains. Some competitive services have functionality for this, but it does not work in practice for most visitors. That is because Chrome and Safari no longer accept third-party cookies for integrity reasons. We see no point in trying to bypass the limitations of the browsers; it contradicts the whole point of playing by the book. 


Can we see statistics on what consents have been collected?

Yes. The settings tool contains statistics on how many consents have been collected for each choice in absolute numbers and percentages.


What percentage of visitors accept all cookies with CookieTractor?

We see that it varies between different websites. The difference is probably due to several factors, including:

  • How much credibility the sender has, that is, how much visitors trust the site.
  • Which target groups visit the website and how inclined they are to accept cookies.

The proportion of visitors who accept all cookies is between 70-93% on CookieTractor implementations.


Can you add your own font and colors?

Absolutely! We have developed CookieTractor to make it easy to adjust the appearance of the cookie issue. In the settings tool, you can enter the name of the font used on your website and the color of the main button "Accept all". If you want more customizations of the appearance of the cookie question, you can add your own CSS to your website, which replaces the default look.


Does CookieTractor comply with WCAG 2.1?

Yes, accessibility is essential to us. CookieTractor complies with WCAG 2.1 AAA.


Do you have to pay extra for subdomains?

Unlimited subdomains are included for free. Subdomains can also be scanned for cookies; both the main domain's and subdomain's cookies are then listed in the cookie modal. The visitor only needs to consent for one of the domains. It is then valid for both the main domain and the subdomains. 


How often is the website scanned for cookies?

When a new website is added to CookieTractor, it is scanned for cookies directly. The website is then scanned every 30 days, whereupon an email with the results of the scan is sent to you. New/deleted cookies are published automatically.


Can CookieTractor search pages behind a login?

No. The search for cookies takes place only on public pages. If you put more cookies in a logged-in mode, these need to be added manually in the settings tool.


Can CookieTractor be used in an internal test environment?

You can implement CookieTractor in a test environment if it's connected to the internet. You need to add the domain name to the internal test environment in the settings tool.


What data about consent do you store?

It is required by law to prove that consent has been given. CookieTractor saves an anonymized key for each consent collected on a website. This is not personal data and cannot be traced to a particular visitor or IP number. A visitor who has given consent can find their key in the consent modal at the bottom of the cookie list. You can, on request, see the consents given for a specific key.


Where do you store data?

We store the anonymized data about consent on Cygate (Telia) servers in Sweden.


Can data pass outside the EU?

By default, CookieTractor uses a Cloudflare CDN with servers worldwide, including Sweden, to always ensure fast loading times. This means that data is always delivered from a server close to the visitor. However, for visitors from the EU, this means that in rare cases data can be delivered from a server outside the EU. Domain name lookups of CookieTractor's standard CDN are done with Cloudflare in the US.

For organizations with requirements that data must never pass outside the EU, we have a CDN solution from Swedish Beebyte that meets this requirement, including domain name lookups. The additional cost of this service is 20% per year.


More questions?

Do not hesitate to contact info@cookietractor.com!