Implementing Web SDK

Introduction 

This page includes step-by-step instructions for integrating the InMobi CMP Web Tag to obtain user consent before activating any tags on your websites. Ensure that you have completed site and consent configurations before tagging. 

Best Practices

• The Web Tag operates asynchronously, and once consent is obtained, it does not interfere with the loading of other tags on your site. 
• We recommend you trigger the CMP tag first in the header. This ensures you capture user consent before activating any vendor tags. 
• Allowing tags to fire before a user's consent can expose your website to compliance risks. 
• Delaying the loading of the CMP may result in timeout issues, such as IAB vendors being unable to retrieve the consent string in time. This can have a detrimental effect on revenue. 

Implementation

Retrieve and Implement Your Tag

1. After you add your sites, click the Web Tag button in the top right corner of the InMobi CMP portal. A modal appears containing the code snippet. You should use it on your website.

   

   

2. When integrating the tag, copy and paste the complete tag into your site's header. Avoid making any modifications to the tag, as alterations may lead to the CMP functioning improperly.

   

3. Upon successful implementation of your tag, you can expect consent metrics to commence populating within 1-2 days. Additionally, the status beacon will transition from orange to green.

   

Implement with Google Tag Manager

For Google Tag Manager support, see Google Tag Manager (GTM) Implementation.

Update Your Tag for IAB Europe’s CMP Domain Changeover

IAB Europe mandates the migration of CMP scripts from consensu.org subdomains. InMobi CMP has completed this. Publishers must update the consent domain to avoid audits and reminders from IAB Europe. Failure to make required changes may lead to website issues after consensu.org deprecation.

If you are a Publisher already using our InMobi CMP product please follow the steps below:

1. After logging in to InMobi CMP portal, check the version number of the CMP.
2. If the number displayed is less than forty-two (42) then you will need to upgrade. If the number is forty-two or higher or is shown as the Latest, you do not need to upgrade.
   • To upgrade, retrieve, and implement your tag as shown above on this page.
3. Once completed successfully, customers should see version forty-two (42) (or the Latest) as the CMP version they are running for a given web property 

Confirming the Tag is Live

Callbacks are intended to be handled directly by the CMP through event listeners, as the calls to the CMP commands are intended to be resolved in a synchronous way. We recommend attaching asynchronous callbacks to the CMP through this method as it will be the source of information set up by the CMP at specific moments.

• Asynchronous Consent String API - When implemented, can add the consent handler, then call the TC Data API to retrieve the string
• CMP Ping - You can use the Ping once loaded to ensure the CMP is available to you.

Post-Implementation Verification Checklist

Once you have integrated InMobi CMP with your website, follow the checklist to ensure a seamless experience.

• Check if the callbacks are being returned properly. For details on callbacks, see Web.
• Check for APIs that trigger MSPA consent screen. For details, see Web APIs.
• If the consent screen pops up successfully, integration is a success.
• If you have any questions about implementation, refer to the General FAQs. If you face issues, raise a ticket to our support team for further assistance.