/
Flutter CMP - How to use your own CMP

Flutter CMP - How to use your own CMP

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

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.

  1. To disable CMP, use the method below before calling the R89SDK.initialize(...) method.

R89SDK.disableCMP()
  1. Use R89SDK.initialize() just after the user interaction of your CMP ends.
    A CMP user interaction ends when the user accepts consent, rejects consent, saves custom consent settings, consent fails to show or to resolve consent, you could identify this happening because the Consent Screen/layer closes/dismisses, you need to have an event/callback that tells you this has just happened and inside that callback call the initialize method. Make sure you call the initialize method in the UI Thread.

How to know if everything is correct

To tell If you did everything correctly you should use the R89SDK.setLogLevel(LogLevel.debug) to see these logs in this order in the Logcat

  1. CMP is disabled → This Means R89 CMP is not going to show

  2. CMP was used previously to initializing the R89 Monetization → We detected a CMP compatible with TCF 2.0 is being used

  3. CMP data is up to date → Consent is updated within the regulatory year

If you don’t see 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 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