The iubenda Cookie Solution counts the number of pageviews generated by the website in order to establish the price of the Cookie Solution and provides the user with useful information regarding the collection of the consent, such as the percentage of consent on the total visits, the manner in which the consent was collected and so on.
All sites generating less than 25,000 pageviews/month are always free and are not counted in your account quota, ie. pageviews are only counted for sites that go beyond that threshold.
The count of the pageviews is carried on by counting the number of executions of the Cookie Solution script. Whenever the Cookie Solution code runs, our software records a pageview.
In order to find out the number of generated pageviews:
The number of pageviews calculated by our software may differ from those calculated using other statistical software such as Google Analytics, ShinyStat or Matomo/Piwik. This difference is due to the fact that the Cookie Solution automatically excludes from the counting, the pageviews generated by bots.
Once the consent has been collected, the banner will disappear and the scripts/cookies that were subjected to the prior consent are immediately released. This is possible because the Cookie Solution script continues working behind the scenes, recognizing the users who have already given their consent.
For this reason the pageview is not recorded only at the first visit of each user, but also during all subsequent visits. The Cookie Solution script, in fact, runs continuously – even if the banner is not displayed and the blocking of scripts not executed.
Yes, simply deselect the Prior blocking and asynchronous re-activation checkbox in the Cookie Solution configurator:
This will add
"priorConsent":false to your Cookie Solution snippet:
"priorConsent":false, pageviews will not be counted and prior blocking will not be performed. Since we strongly advise against deselecting prior blocking if you want to be in compliance with EU legislation, be sure to remove
"priorConsent":false (or switch it to its default value,
true) once you publish your website.
Please note that if the prior blocking setting has been disabled server side (via the checkbox on the flow page), this parameter will be ineffective whether it’s set to