IAB TCF 2.2 support
The IAB TCF 2.2 is here and consentmanager is one of the first CMPs to support the new Standard . Publishers can now switch from 2.0 to 2.2 and get ready for Google’s new advertising requirements. However, currently only a few companies support the new Standard , so we recommend waiting a little longer before switching.
You can find more information about IAB TCF 2.2 in our blog: consentmanager
consentmanager certified for Google’s new CMP requirements
According to a recent announcement by Google, all partners using Google’s publisher products – Google AdSense, Ad Manager or AdMob – must use a Google-certified Consent Management Platform (CMP) that integrates the Transparency and Consent Framework (TCF). when serving ads to users in the European Economic Area (EEA) or the United Kingdom (UK).
consentmanager was one of the first CMPs to be certified by Google for this new requirement.
Read here why this is so important for users of Google products:
consentmanager
IMPORTANT: Code change required immediately / abolition of old codes
We would like to point out once again that all old codes on websites and apps must be replaced by July 1st at the latest . Old codes that still contain the domain consensu.org will no longer work from this date: the cookie banner will no longer be displayed, providers may not be blocked or not blocked correctly. Various warning messages in your account in the CMP overview will show you whether you are still using old codes.
You can read what you need to consider in the following article:
consentmanager
Improve cookie banner opt-in: 3 ways to increase opt-in rates
Cookie banner opt-in rates are of great concern to both website owners and marketers. An optimized cookie banner allows marketers to obtain user consent for cookies used for targeted advertising and analytics. With this consent, they receive valuable insights into the behavior, preferences and interests of users, which they can inform their advertising campaigns and marketing strategies.
In this article, we will share three effective strategies you can use to significantly increase cookie banner opt-in rates while ensuring compliance and user satisfaction.
Click here to read the full article
Data protection for apps (incl. cookie checklist)
The requirements for collecting cookies and complying with data protection regulations worldwide do not only apply to websites. Mobile app compliance is just as important. And to comply with mobile app regulations, app developers and app owners need to be aware of the laws that apply to them and their users when processing personal data.
Would you like to know more? Then read our blog post:
https://www.consentmanager.de/wissen/datenschutz-bei-apps/
Meta should pay a record fine of 1.2 billion euros
In a landmark case, Meta, the parent company of social media giant Facebook, has been fined a record €1.2 billion. The fine is a result of alleged privacy violations by Meta and failure to adequately protect user data. This hefty fine sends a clear message to tech companies that carelessness in handling user data will not be tolerated. The massive size of the fine underscores the growing importance of privacy and the need for stronger enforcement in the digital age. Meta now faces the task of restoring trust and demonstrating its commitment to protecting user privacy.
Avoid GDPR fines – here’s how!
Do the free cookie check
The consentmanager Cookie Crawler alerts you to vulnerabilities in the use of your cookie banner. Or take a look at our various checklists for data protection-compliant cookie banners. The checklists are available for download on our website
More optimizations and adjustments in June
In June there were, among other things, the following minor innovations and changes:
Various adjustments have been made in the new client area, such as bug fixes in the design editor, adjustments to the granting of specific user rights in the CMP and report settings. The CMP wizard for the CMP setup has also been redesigned.
In connection with the necessary code changes, an additional report on the use of the old codes ( consensu.org ) was created and a crawler bug when finding custom providers was fixed. Furthermore, an automatic assignment of www domains to providers now takes place.
Further innovations and optimizations can be found in the complete release log:
Release log
- Typo3 PHP8 compatibility for Typo3 plugin
- Design editor text editing fix (new client design)
- Legal basis for purposes & vendors not correctly displayed (new client design)
- Issue with azureedge.net connected to wrong vendor
- Lazyloading of CMPs & Designs in modal (new client design)
- Resized modal dropdown for legal basis options (new client design)
- Issue setting specific user rights for CMPs (new client design)
- Added link to change payment interval in account view (new client design)
- Added graphics/charts to CMP report (new client design)
- CMP report, issue with redirect after report is created (new client design)
- CMP report, specific error when creating report for all CMPs (new client design)
- CMP report, wrong date when choosing this month
- CMP report, back button broken
- Relaunched CMP wizard (new client design)
- Relaunched account upgrade view (new client design)
- SSOAuth issue on delete (new client design)
- Added form loader to account edit view
- TCF 2.2 support
- Additional report on use of old codes ( consensu.org )
- Opt-out logic with custom button settings
- Add option to ask for opt-in but not show the layer
- Use dataLayer with system IDs in addition to IAB IDs
- [IOS] ATT User denied by previous given consent. Purposes are deactivated but vendors are not
- Auto blocking preview hints
- Add option for custom client config supplied via cmp config
- Fix crawler does not find custom vendors
- Automatically assing www-domains to vendors
