raise support ticket
BACK

Additional Reading

Web

Version 58

[17/December/2024]

  • Bug Fixes:
    • Resolved an issue where Legitimate Interest was not included in the consent string when the close or reject button was clicked.

Version 57

[17/December/2024]

  • Bug Fixes:
    • Fixed an issue where the GPP string was invalid due to Publisher Restrictions.

Version 56

[21/October/2024]

  • Feature Enhancement:
    • Included new vendors disclosed section(along with Core and Publisher TC) in the TC string.
    • UX Changes
      • Vendor Screen (for every vendor)
        • Added Legitimate Interest Purpose(s)
        • Added Description for features, special features, and data categories
        • Under Storage disclosure, changed key maxAgeSeconds to Max Age Period for better clarity
        • Under Storage disclosure, for Cookie Refresh, we are showing either True or False
        • Minor CSS fixes

Version 55

[25/September/2024]

  • Feature Enhancement:
    • Added Dynamic Persistent link text in CMP description: A customizable privacy label will appear in the CMP description set on the Portal in the Themes section with the PERSISTENT CONSENT LINK LABEL field.
    • Categorization of Special Purposes, Features, and Special Features into separate categories.
    • Added Brazil and Canada as separate options along with EEA, USA, WorldWide, and Never.
    • Added special purpose: “Save and communicate privacy choices”.
    • Updated CMP description text to include consent storage mechanism and cookie expiration duration.
    • Added functionality to add GDPR Privacy Link on the init/purposes screen of the CMP consent screen.
    • The GPP stub function has been moved to the universal tag now. Please deploy the updated universal tag.
  • Bug Fixes:
    • Purposes are shown properly under storage disclosures in Vendors.
    • Added data retention for each purpose, special purpose, and feature.

Version 54

[04/June/2024]

  • Feature Enhancement:
    • Global Privacy Platform: The GPP is a protocol designed to streamline the transmission of privacy, consent, and consumer choice signals from sites and apps to ad tech providers. It enables advertisers, publishers, and technology vendors in the digital advertising industry to adapt to regulatory demands across markets. The GPP currently supports the following privacy strings: the IAB Europe TCF, the MSPA’s US National string, and US states-specific privacy strings for California, Virginia, Utah, Colorado, and Connecticut.
    • Added Iceland, Liechtenstein, and Norway: We have expanded our Consent Management Platform (CMP) to include additional countries under EEA (European Economic Area). Iceland, Liechtenstein, and Norway users will now see the GDPR consent popup and can give their consent under EEA.

Version 53

[29/April/2024]

  • Feature Enhancement:
    • Launched Group consents for Google Consents.
    • Added Switzerland to the list of GDPR countries covered under "EEA & UK".
  • Bug Fixes:
    • Fixed the issue where the CMP was failing to load on Firefox.
    • Accept All/Reject All buttons are now working for Google Consents.
    • Fixed consent_cookie_update gtm custom event firing on page refresh.

Version 52

[29/February/2024]

  • Feature Enhancement:
    • Google Basic Consent Support: Introduced functionality to activate Google Basic Consent support for properties utilizing Google services like Google Analytics and Google Ads. This enhancement ensures users can seamlessly continue using these applications while adhering to consent requirements. For more information, see Google Basic Consent with InMobi CMP.
    • Global Privacy Control Support: Implemented functionality to respect users' Global Privacy Control (GPC) signals, ensuring compliance with CCPA legislation requirements.
      • When an end-user activates the GPC flag in their browser and does not communicate any preferences through the consent banner, the Opt-out signal in the US privacy string will be set to Yes, effectively opting the user out.
      • Conversely, if an end-user enables the GPC flag and communicates an opt-out preference via the consent banner, the user's explicitly shared preference takes precedence over the GPC signal.
      • If the GPC flag is not set or not supported by the browser, there are no changes to the string.

On This Page

Last Updated on: 19 Dec, 2024
✕

You are almost there...

By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.

I AGREE