- CMP comes first: For websites, implement the CMP in the header so that you gather users’ consent before any other tags are loaded. Most tags require consent before they can be used lawfully. Tags should look for the presence of a CMP to adjust their behavior dynamically depending on the user’s selected preferences. This only works if the CMP loads before any other tags.
- Keep the CMP up to date: We regularly publish updates to InMobi CMP to fix bugs or change and update functionalities in response to new best practices, regulatory opinion, and case law. All versions are listed here.
- Don’t modify InMobi CMP’s source code: Not only is doing so against our terms of service, but you run the risk of breaking or circumventing carefully considered elements that, when changed, may result in your and your partners’ non-compliance with the law.
- Privacy by Default: If you are in doubt about what privacy and data protection laws require you to do, leverage InMobi’s default configuration settings and go TCF 2.2. We have carefully tuned the default to help reduce the risk of non‑compliance.
- With great customizability comes great responsibility: Only change defaults after carefully considering the implications and after having consulted with your privacy and/or legal team. Even something as basic as changing the color scheme of the CMP can have severe consequences. For example, you could inadvertently change the color of text or buttons to make them hard to read or invisible against their background.
- Keep the persistent Recall CMP link: Users must be able to withdraw their consent at any time, the persistent Recall CMP link is the easiest way to achieve that. Only remove the persistent Recall CMP link if you have added the link in another place in which the user would expect to withdraw their consent.
Last Updated on: 04 Jan, 2024