Documentation

All instructions about how to set up Cookie-Script properly

Some of popular content management systems generate session cookies with random names. This means the session cookie name is different for every visitor. This guide will help you to set up those cookies properly. 

For example, WooCommerce can set up a session cookie which looks like this:

wp_woocommerce_session_f919208d949256bc062e5c23e02ba9a2

where f919208d949256bc062e5c23e02ba9a2 is just a random string unique for each user. Such cookies are not suitable for the cookie report since the actual cookie name of every visitor will be different.

Another issue with random name cookies is that every scanning of website cookies will generate an additional random name cookie. This will make the cookie report grow with time and fill the report with junk cookie names.

By default, Cookie Scanner will automatically detect most of those random cookies and save them as patterns

You can also use the same pattern to add your own random name cookies. 

The following pattern format should be used: 

  • range of possible characters is listed in square brackets: [ ]
  • a number of characters from square brackets is listed in curly brackets: {  }
  • all other characters should remain the same

Examples: 

Simple hash value cookie

98913e1d6a7b94cb0f55994f679f5956

will be listed as 

[abcdef0123456789]{32}

16 random digit value with SE_ in front and _YT in the end

SE_32697552412547638_YT

will be listed as

SE_[0123456789]{16}_YT

WooCommerce session cookie

wp_woocommerce_session_f919208d949256bc062e5c23e02ba9a2

will be listed as: 

wp_woocommerce_session_[abcdef0123456789]{32}