AI Search

Manage Vendors

This guide covers the steps and best practices for configuring and managing vendors for your properties within the InMobi CMP portal. When you use InMobi CMP on your property, you must specify the vendors (third parties) that may process user data, set their purposes, and manage consent preferences. 

Access the Vendors Page

  1. Log in to the InMobi CMP portal.
  2. Navigate to the Vendors page from the left-side panel. Here you’ll find tabs for:
  3. You manage each category separately under the same interface.

IAB Vendors

IAB vendors are those registered in the IAB Global Vendor List (GVL) and recognized by the IAB Transparency & Consent Framework (TCF). Using them allows you to use standardized consent strings (TCF/GPP) and simplifies compliance.

  1. Search vendors by name in the search field.
  2. Click the + icon next to the vendor name to find the Purposes, Special Purposes, Features, and Special Features for that vendor.

  3. Filter the vendors list by legal basis - Consent, Legitimate Interest, Flexible, and Multi. 
    • Consent: vendor with only consent purposes.
    • Legitimate Interest: vendors with only legitimate interest purposes.
    • Flexible: vendors with at least one flexible purpose.
    • Multi: vendors with consent and legitimate interest purposes.

    Note

    We consider consent, legitimate interest, and flexible purposes to classify vendors' legal basis types. Special purposes, features, and special features are not considered to classify vendors based on legal basis.

  4. Select the checkbox next to the vendor name and click Block or Whitelist as required.

Non-IAB Vendors

Non-IAB vendors are vendors who have not registered with IAB Europe and are not part of the IAB Vendor List TCF 2.2. Since they are not listed in the IAB Global Vendor List, it is not possible to create a signal to transmit to non-IAB vendors. They only enable publishers to show the vendor to the consumer and obtain a consumer's privacy preferences for that vendor, not the ability to transmit them in a standard way. 

  1. To add non-IAB vendors, go to the Non-IAB Vendors tab and click Add Vendor.

  2. Add details such as Vendor name, Vendor Privacy Policy Link, Vendor Description, TCF Version, Vendor Legitimate Interest Claim, and Purposes

  3. Click Add Vendors to save changes.

Your newly created vendor will be added to your non-IAB vendors list in the portal and will appear in the CMP in the partner screen.

On the InMobi CMP portal, the vendor will be given a non-IAB vendor ID, which will correlate to their position in the non-IAB vendor cookie and the non-IAB vendor API. You will now need to manage these vendor technologies using the non-IAB APIs and/or cookie instructions. 

Note

  • We recommend adding non-IAB Vendors in batches if you're planning to add multiple non-IAB Vendors to your CMP for disclosure, to minimize the number of times your users will be re-prompted on the site.
  • You will need to control the firing of technology for these vendors using some form of tag management (e.g., Google Tag Manager (GTM) or Tealium). For implementation with GTM, view our GTM Implementation Guide.

You have completed all the configuration options for the InMobi CMP and can apply the Universal tag to the site.

nonIABVendorConsent API

You need to use the nonIABVendorConsent API to gather user consent. Each vendor you specified is assigned an id and stored in the consent.nonIabVendorConsents object. Check each entry as needed for consent (true/false). Here is an example using a fictitious vendor "Non-IAB Company" with id 1, which requires consent for purposes 1 and 3 to operate.

__tcfapi('getNonIABVendorConsents', 2, function(consent, success) { 
    // check consent for non-IAB vendor with id 1. Always check 
    // whether the callback returned success and GDPR applies
    if (   success 
        && consent.gdprApplies
        && consent.nonIabVendorConsents[1]
       ) {
        // Use getTCData to validate consent is given for the 
        // purposes declared in the configuration step
        __tcfapi('getTCData', 2, function(tcdata, success) {
          if (   success 
              && consent.gdprApplies) {
              if (   tcdata.purpose.consents[1]
                  && tcdata.purpose.consents[3]) {
                  nonIabCompanyTag(); // replace this with your own code
                  console.log("Debug: ", tcdata.purpose.consents[1],
                    tcdata.purpose.consents[3]);
              }
          }
        });
    }
});

You can make that call anywhere in your code where you need to check for consent for the non-IAB vendor you use on your page. You also need to manually configure your Google tag(s) on your site to behave based on the consent preference made and on the product the user is using.

For Non-IAB vendor API and all other APIs, see CMP2 & CCPA API Index.

Google Vendors

These are vendors that work with Google and are not listed under the TCF vendor list. If you work with Google Ad Manager, you may want to review this list and enable the vendors that you are working with through Google Ad Manager, AdMob, and AdSense. By default, all vendors are selected. For more information, see Ad Technology Providers.

  1. Select the additional vendors you want to include in your ad request within Google Ad Manager. Check or uncheck the vendors in the list.

  2. Click Save.

Note

  • Google vendors are only used if the Enable Google Vendors checkbox is selected during Protect a Site.
  • In the IAB TCF framework, Disclosed Vendors are those not listed in the IAB Europe Global Vendor List (GVL) but still present on the site and shown in the CMP. These vendors should not be included in the TCF string; instead, pass them via Google’s Additional Consent specification. When monetizing with Google in the EU, set “Include Disclosed Vendors in TCF string?” to ‘No’. Enabling this may lead to Google rejecting the TC string.

On This Page

Last Updated on: 23 Dec, 2025