Integration and Implementation

1. What is the integration process?

The integration process is composed of 3 simple steps:

1. Create your account and log in via https://choice.inmobi.com/login.
2. Set up your app(s) and/or site(s) via the interface.
3. Integrate the SDK or Web Tag following the instructions on this support portal.

We recommend watching the video below for a visual overview of the entire process. You can also explore the comprehensive details available on this support portal, where each step is thoroughly outlined.

2. Is this available on both Android and iOS?

InMobi CMP is designed to be applicable to  Android and iOS, in-app and web. It offers seamless integration and consent management capabilities for both mobile operating systems, ensuring comprehensive coverage across different devices and providing a consistent user experience for all your app users.​​​​​

3. Is the CMP compatible with Unity?

Yes, we have a Unity package available here. Please note, whilst UI customization for Unity is not currently supported, it is currently on our roadmap to be available in Q2 2024.

4. Is the CMP a standalone SDK for in-app?

At present, it is a standalone SDK for in-app consent management. In our ongoing efforts to enhance the experience for our publishers, we plan to seamlessly integrate the CMP into our monetization SDK in the first half of 2024. This integration will allow you to effortlessly enable or disable the CMP module, providing you with greater flexibility and control over your app’s consent management approach.

5. How does the integration with Google Mobile Ads or other Ad providers work?

Integration with Google Mobile Ads and other Ad providers through InMobi CMP requires publishers to configure consent preferences and vendors within the CMP interface. The CMP SDK handles user consent collection, TCF string generation, and storage. Ad providers can access the TCF string either through their SDK's API, with publishers passing the consent string, or by retrieving it from shared storage. This string helps Ad providers determine whether to display personalized Ads, ensuring compliance with user consent choices and data protection regulations.

6. Why do I see CMP warnings in the browser console?

If you're seeing CMP warning in the browser, check the following:

• Ensure you're using the latest CMP tags or GTM container file (if integrated via GTM).
• Test with the latest CMP version to rule out outdated configurations.

7. Why is the CMP pop-up not appearing on my site?

If the CMP pop-up is missing despite setup, check the following:

• Site URL Match: Ensure the CMP site URL matches your actual site URL exactly (e.g.,"www.example.com" vs. "example.com").
• User Location & Consent Scope: If consent is set for specific regions (e.g., "EEA"), the pop-up will not show for users outside those locations.
• Complete essential post-implementation checks for Android, iOS, and Web.

8. Why is my Google Analytics (GA4) data incorrect or missing consent signals? 

If you're experiencing issues with Google Analytics data or missing consent signals, check whether Google Basic Consent is enabled. This issue typically occurs when it is disabled.

If enabled, verify that all required consent signals are correctly configured. For more information, see Google Basic Consent with InMobi CMP.