Starting with what exists
Before even talking about banners or buttons, it is necessary to know what is actually loaded on the site.
A CMP does not block “everything”. It blocks what it knows and what is properly configured.
Implementation defines compliance
GDPR compliance relies on strict technical implementation. Loading the CMP after the scripts it should block makes no sense.
This issue frequently appears in integrations, as explained in how service loading works.
A truly balanced choice
Refusal must be as easy as acceptance. This is not optional.
Greyed buttons or misleading paths are non-compliant, even if widely used.
Widespread confusion
Many sites believe they are compliant when they are not. This confusion is maintained by tolerated but questionable practices.
This also explains why some CMPs report unusually high consent rates. tarteaucitron have a global consent rate of 51%-54%.
