How to succeed with CookieTractor

Test the implementation in a private window

When you have installed CookieTractor according to the instructions, testing the implementation and checking that the correct cookies are set is recommended. View instructions on how to review cookies in Chrome. When testing cookies, you should always do so in a private/incognito window in the browser. By using that mode, it is ensured that no cookies from related services "bleed through" to the ones you use. Cookies from services unrelated to the ones you use, but from the same provider, may appear to belong to your website if you do not use private browsing. Private browsing thus means that the visit to the website will be as if it were the first time you ever visited it.

Worth noting is that if you already have a private browser window open there is a risk that both windows will share information with each other, make sure to close any private windows before you start.

Use the cookie list where you inform about cookies

Do you have a privacy policy or similar where you explain how you collect personal data and mention cookies? Then it might be appropriate for you to add our Cookie list as a widget. It is fully synced with the cookie list the cookie banner. The widget is rendered in raw HTML that follows the site's style sheets. If you want to adapt the styling of it, you can find a CSS editor inside our tool. The widget also prints information about the visitor's current consent after the cookie list.

Hide the banner on a specific page

On pages you link to from within the cookie banner, you may want to disable it. Suppose you link from the cookie banner to a page with a privacy policy. In that case, it is reasonable that the visitor should not have to consent before they can read about how the personal data is handled.

Hide the banner on a page by adding the CSS class cc-hidden anywhere on the page. It can be put on an HTML element used in the framework or in connection with a piece of text from the website's editor interface.

Our script will load as usual, including our triggers, variables (also through tag manager) and our SDK. Therefore, you can open the banner from a button, or save a consent through the SDK in a form or similar form.

A consequence of the banner not being displayed to the visitor is that CookieTractor has no other consent to condition against than Only Necessary. When the visitor navigates to other pages on the website, the banner will be displayed, given that no consent was previously collected.