| Note |
|---|
We do not recommend using your own CMP since we already provide good options that comply with the most common consent and user privacy laws around the world and also use the common standards that are require to optimize the Monetization. And also we are offering to manage it for you so you avoid complications in implementation and customization |
| Info |
|---|
Before moving on with this feature, remember that you can request cosmetic & technical changes to your assigned R89 CMP by contacting your technical account manager or you account manager. |
Use Disable CMP methodTo disable CMP, use the method below before calling the
R89SDK.initialize(...)method.
| Code Block | ||
|---|---|---|
| ||
R89SDK.disableCMP() |
...
To tell If you did everything correctly you should use the R89SDK.setLogLevel(LogLevel.debug) to see this these logs in this order in the Logcat
CMP is disabled → This Means R89 CMP is not going to show
CMP was used previous previously to initializing the R89 Monetization → we We detected a CMP compatible with TCF 2.0 is being used
CMP data is up to date → consent Consent is updated with in within the regulatory year
If you don’t see this these logs you are probably seeing this one of these:
“CMP data is outdated, you should call the CMP Again” → which means that you have very old consent, consent choices should be provided to the user every year and a an industry-standard is every 6 months, or you didn’t wait for the CMP to finish
“No CMP was used previous to initializing the R89 Monetization, it should” → which means that you are not using a TCF2.0 compatible CMP or you didn’t wait for the CMP to finish
...