There can be a number of factors the results in our scanner returning 0 cookies.
Here are the TOP 5 reassons:
- Our scanners IP is being blocked.
- The website contains redirects
- Wrong domian whitelisted
- Scanner looping.
- Popup not visible on website.
1. Our scanners IP is being blocked.
Our scanner is set up to emulate a very efficient user to go through the website and scan for cookies.
This results in requests sent to the website's servers. This can in some cases be seen by the server as an attack, like DDOS.
In these cases the server may block our scanners IP-address.
Please consult your hosting-provider to unblock / whitelist our IP
The IP may change over time, so a better method is whitelisting our user agent header
The scanner uses a certain `User Agent` header, which allows anyone to identify the traffic that is coming from us
The header is:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36(KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 CookieInformationScanner
So it can also be possible to whitelist us by user agent header:
2. The website contains redirects
A redirect is a know and widely used practise, but in some small cases a redirect can result in our scanner either looping or timing out.
If the solution is set up to scan a specific domain, but this domain is being redirected to another, this will also stop the scan.
3. Wrong domian whitelisted
If the domain provided for the consent solution is not the same as the domain / website you have implemented the policy on that will also result in an empty policy or a 404 error in the console.
Please check the url for the solution is the same as the website you want to use the solution on.
4. Scanner looping.
We sometimes see a web-widget on a website resulting in our scanner ending up in an endless LOOP.
Eg. A calender-functions with clickable links that auto-generate new links.
Turn off or remove the web-widget during the scanning process.
5. Popup not visible on website.
If our Popup-script is implemented on the website the scanner is setup to click the accept-button to by-pass our SDK.
But if for some reason the pop-up is not visible in the browser window so our scanner can't click the button, then our scanner will timeout.
Make sure the popup-template you have chosen is looking mostly the same as it is intented.
To compare templates, go to the Design Center
Still not sure if the error one of the above?
Please contact our support-team, so we may help you