Starting March 1, 2023, the Prior Blocking feature is always enabled on all installations of our Privacy Controls and Cookie Solution, regardless of your previous code or dashboard set-ups.
This means that the “Prior blocking and asynchronous re-activation” (server side) and “Prior consent” (priorConsent parameter) options are always active. More about these two options here.
Beyond these options, we remind you that prior blocking must then be set up by using any of the blocking methods described in this guide.
We’re also changing the behavior of our Privacy Controls and Cookie Solution for users who exceed the page views/month limit of their plan.
Instead of disabling the prior blocking for the current month, the cookie banner will be replaced by an alert (this also applies when the subscription expires). As a result, you won’t be able to get visitors’ consent and release cookies.
We’ll roll out this change across all Privacy Controls and Cookie Solution delivery channels in the following order:
As usual, if you have turned off automatic upgrades, we’ll email you when you approach or exceed the threshold covered by your Privacy Controls and Cookie Solution plan. This way you can always avoid service interruptions.
Finally, if you have enabled the Cookie and Consent Preference Log (required by many EU data protection authorities), we remind you that from January 15, 2023, the invalidateConsentWithoutLog parameter is forced to true.
Since cookie consents without proof are considered invalid by many EU data protection authorities, a new consent is requested—via the cookie banner—whenever a user’s consent is missing in the Cookie and Consent Preference Log.
No action is required, but you may want to take the chance to make sure that your cookie banner configuration is up-to-date with the latest requirements by data protection authorities.
Our configurator and scanner report can help you and automatically suggest the best configuration.
