faqs | Migrating to SDK 710 (GDPR Compliant)

The General Data Protection Regulation (GDPR) goes into effect on May 25, 2018 across the European Union. These new regulations create a framework to protect personal data about individuals in the EU and must be adhered to by all businesses who collect or process such data. Failure to comply with GDPR can result in strict penalties for non-compliant companies.

As a trusted partner of leading brands across the globe, InMobi is committed to data protection and protecting consumer privacy while creating a safe and transparent marketplace for advertisers and generating value for our publisher partners.

If your app currently monetizes or has plans to monetize in the European Economic Area (EEA) in the future, we ask that you carefully read the rest of this note in its entirety.

As part of these new regulations, any entity collecting or processing the personal data of EEA residents is subject to the GDPR. It is important to note that GDPR expands the definition of "personal data” to include data sets such as advertising identifiers like IDFA and the Google Advertising ID), as well as IP addresses, geolocation data and more.

InMobi SDK 710 supports:

  • iOS - Minimum iOS 8 and requires XCode 9.0 or later
  • Android - Minimum Android 4.0.3 (API level 15) or later

You can upgrade to SDK 710 using following methods:

The new integration guides are available here: iOS, Android.

Direct Integration

Change 1

The following SDK init API is deprecated:

iOS - [IMSdk initWithAccountID:@"Insert InMobi account ID here"]

Android - [InMobiSdk.init(MainActivity.this, "Insert InMobi Account ID here")]

Change 2

SDK 710 introduces consentObject - a JSONObject representation of all kind of consent provided by the publisher to the SDK. The key gdpr_consent_available can be accessed via string constant IM_GDPR_CONSENT_AVAILABLE

Important:

  • consentObject has to be provided in every session. The SDK does not retain the consent. It only keeps the consentObject in temporary session memory. If the app is relaunched or crashes during a session, the SDK will lose the consentObject.
  • Within a session, you can update the consent like these:
    • iOS: [IMSdk updateGDPRConsent:@{<Insert consentObject dictionary here>}];
    • Android: InMobiSdk.updateGDPRConsent(JSONObject consentObject)
iOS

Initialize the SDK in the didFinishLaunchingWithOptions method within the app delegate's .m file:

- (BOOL)application:(UIApplication *)application  didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{   
//Initialize InMobi SDK with your account ID
[IMSdk initWithAccountID:@"Insert InMobi account ID here" consentDictionary:@{<Insert consentObject dictionary here>}
];
// Do your stuff.
return YES;
}
		
Android

Initialize the SDK in your launcher Activity like so, by passing in the Activity context and your InMobi account ID.

InMobiSdk.init(MainActivity.this, "Insert InMobi Account ID hered", “Insert consentObject JSONObject here”);
		

Further details are captured in the integration documents.

Integration via Mediation Partners or Plugins

The updated adapters and plugins will available soon.