This guide shows you how to use Google Mobile Ads SDK to load and display ads from InMobi using [mediation](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation.md.txt), covering both waterfall and bidding integrations. It covers how to add InMobi to an ad unit's mediation configuration, and how to integrate the InMobi SDK and adapter into an iOS app. ## Supported integrations and ad formats The mediation adapter for InMobi has the following capabilities: | Integration || |---|---| | Bidding | Yes | | Waterfall | Yes | | Banner | Yes | | Interstitial | Yes | | Rewarded | Yes | | Rewarded Interstitial | Yes | | Native | Yes | ## Prerequisites Before you continue, verify the following: - iOS deployment target of 13.0 or later. - \[For bidding\]: To integrate all supported ad formats in bidding, use InMobi adapter 10.6.0.0 or later ([latest version recommended](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation/inmobi.md.txt#inmobi-ios-mediation-adapter-changelog)). - Latest Google Mobile Ads SDK version. - [Set up mediation](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation.md.txt). ## Step 1: Set up configurations in InMobi UI [Sign up](https://publisher.inmobi.com/signup) for an InMobi account.  Once your account is verified, [log in](https://publisher.inmobi.com). ### Add an app To add your app to the InMobi dashboard, click **Inventory \> Inventory Settings**.  Click **Add Inventory** and select the **Mobile App** channel from the drop-down menu.  Start typing your published app store **URL** in the search bar and select the app from the auto-populated results. Click **Continue**.  If your app in not published, click **Link manually** and enter the required details. Click **Continue**.  Review the **App \& Website Compliance** settings and then click **Save and Create Placements**.  ### Placements After you set up your inventory, the system redirects you to the placement creation workflow. > [!NOTE] > **Note:** If the system does not redirect you to the placement creation workflow, go to **Inventory \> Inventory Settings** . Then, search for the app or website you would like to create a placement for. Click **Add a placement**.  ### Bidding > [!NOTE] > **Note:** Contact your account manager to get access for configuring bidding in the InMobi dashboard. Select the type of ad unit. Then enter a **Placement Name** , select **On** and **Google SDK Bidding** for **Audience Bidding** and **Partner** respectively, and fill out the rest of the form. Click **Create Placement** when done.  ### Waterfall Select the type of ad unit. Then enter a **Placement Name** , select **Off** for **Audience Bidding** , and fill out the rest of the form. Click **Create Placement** when done.  Once the placement is created, its details are shown. Take note of the Placement ID, which will be used for setting up your Ad Manager ad unit. > [!NOTE] > **Note:** The InMobi Placement ID is present under the placement name.  ### Account ID Your InMobi account ID is available under **Finance \> Payment Settings \> Payment Information**.  ### Locate InMobi Reporting API Key ### Bidding This step isn't required for bidding integrations. ### Waterfall Go to **My Account \> Account Settings** . Navigate to the **API Key** tab and click **Generate API Key**. Select the **email** of the user the key is required for and click **Generate API Key**. A file containing the API key and username/login name will be generated.  Only the publisher administrator of the account will be able to generate an API key for all users. If you have forgotten the previously generated API key, reset your API key by hovering over your mail on the **API Key** tab.  ### Update your app-ads.txt [Authorized Sellers for Apps app-ads.txt](https://iabtechlab.com/wp-content/uploads/2019/03/app-ads.txt-v1.0-final-.pdf) is an IAB Tech Lab initiative that helps ensure your app ad inventory is only sold through channels you've identified as authorized. To prevent a significant loss in ad revenue, you'll need to implement an `app-ads.txt` file. If you haven't done so already, [create an app-ads.txt file for Ad Manager](https://support.google.com/admanager/answer/7544382). To implement `app-ads.txt` for InMobi, [Add your personalized code snippet](https://support.inmobi.com/monetize/manage-inventory/app-ads-txt/set-up-an-app-ads.txt-file-for-your-app#add-your-personalized-code-snippet). ### Turn on test mode Enable **Test Mode** for your placement on all live impressions or certain test devices only. > [!NOTE] > **Note:** Test mode is turned **Off** by default for all placements. However, test mode can be enabled for placements across all app instances or only for devices you specify.  ## Step 2: Set up InMobi demand in Ad Manager UI Sign in to your [Ad Manager account](https://admanager.google.com/home/). ### Add InMobi in Companies ### Bidding This step isn't required for bidding integrations. ### Waterfall Navigate to **Admin** \> **Companies** , then click the **New company** button in the **All companies** tab. Select **Ad network**.  Select **InMobi** as the **Ad network** , enter a unique **Name** and enable **Mediation** . Turn on **Automatic data collection** , and enter the **Username** and **API Key** obtained in the previous section. Next, enter your **Username** and click **Save** when done.  ### Enable secure signal sharing ### Bidding Navigate to **Admin** \> **Global settings** . Go to the **Ad Exchange account settings** tab and review and turn on **Secure signal sharing** . Click **Save**.  ### Waterfall This step isn't required for waterfall integrations. ### Share secure signal on bid requests ### Bidding Navigate to **Inventory** \> **Secure Signals** . Under **Secure signals** , search for InMobi and turn on **Enable app integration**.  Click **Save**. ### Waterfall This step isn't required for waterfall integrations. ### Allow secure signal sharing for SDK Bidding ### Bidding Navigate to **Delivery** \> **Demand channel settings** . In the **Default settings** tab, turn on **Allow secure signal sharing** for **SDK Bidding**.  Click **Save**. ### Waterfall This step isn't required for waterfall integrations. ### Configure InMobi bidding ### Bidding Navigate to **Delivery** \> **Bidders** , and click **Go to SDK Bidding**.  Click **New bidder**.  Select **InMobi** as the bidder.  Click **Continue** to enable SDK Bidding for this bidder.  Click **Done**. ### Waterfall This step isn't required for waterfall integrations. ### Configure ad unit mapping ### Bidding Navigate to **Delivery** \> **Bidders** , and click **Go to SDK Bidding**.  Select the company for InMobi.  Go to the **Ad unit mapping** tab and click **New ad unit mapping**.  Choose **Specific ad unit** . Select an ad unit and format, **Mobile app** as the **Inventory type** , and your **Mobile application** . Then, enter **Account ID** and **Placement ID** obtained in the previous section. Finally, click **Save**. > [!IMPORTANT] > **Important:** Target the selected ad unit by at least one yield group, and the **App ID** must be associated with the targeted app as in the InMobi UI.  ### Waterfall Navigate to **Delivery** \> **Yield groups** and click the **New yield group** button. Select your **Inventory** and **App**.  Scroll to **Yield partners** and click **Add mediation partner**.  Select the company you created for InMobi in the previous section. Choose **Mobile SDK mediation** as the **Integration type** , **iOS** as the **Platform** , and **Active** as the **Status**. Enter the **Account ID** and **Placement ID** obtained in the previous section, and the **Default CPM** value. Click **Save**. > [!IMPORTANT] > **Important:** The **App ID** must be associated with the targeted app as in the InMobi UI.  > [!NOTE] > **Note:** Automatic data collection takes a few days to gather data before it can accurately calculate a Dynamic CPM value for a mediation network. Once the eCPM can be calculated, it is automatically updated on your behalf. ### Add InMobi to GDPR and US state regulations ad partners list > [!IMPORTANT] > **Important:** Verify that you have **Account Management** permission to complete the configuration for EU Consent and GDPR, US State regulations, and User Messaging Platform. See [Manage user access to your > account](https://support.google.com/admob/answer/2784628) for details. Follow the steps in [European regulations settings](https://support.google.com/admanager/answer/10113006#adding_ad_partners_to_published_gdpr_messages) and [US state regulations settings](https://support.google.com/admanager/answer/14117973) to add **InMobi** to the European and US state regulations ad partners list in the Ad Manager UI. ## Step 3: Import the InMobi SDK and adapter > [!NOTE] > **Note:** Failure to integrate the compatible InMobi and Google Mobile Ads SDK versions might lead to build issues. ### Recommended: Use Swift Package Manager Before you continue, you must have the minimum supported adapter version 10.8.6.0. To [add a package dependency](https://developer.apple.com/documentation/xcode/adding-package-dependencies-to-your-app#Add-a-package-dependency) to your project, follow these steps: 1. In Xcode, navigate to **File \> Add Package Dependencies...**. 2. In the prompt that appears, search the following package URL: https://github.com/googleads/googleads-mobile-ios-mediation-inmobi.git 3. In **Dependency Rule** , select **Branch**. 4. In the text field, enter `main`. ### Manual integration - Download the latest version of the [InMobi iOS SDK](https://support.inmobi.com/monetize/ios-guidelines/) and link `InMobiSDK.framework` in your project. > [!NOTE] > **Note:** Note: It is recommended to use the latest 7.x version of the InMobi SDK instead of 8.x. - Download the latest version of the InMobi adapter from the download link in the [Changelog](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation/inmobi.md.txt#inmobi-ios-mediation-adapter-changelog), and link `InMobiAdapter.framework` in your project. - Add the following Frameworks to your project - `libsqlite3.0.tbd` - `libz.tbd` - `WebKit.framework` ### Use CocoaPods > [!CAUTION] > **Caution:** Starting December 2, 2026, the [CocoaPods Specs > repository](https://blog.cocoapods.org/CocoaPods-Specs-Repo/) is in read-only mode. As of this date, Google Mobile Ads SDK no longer publishes updated versions of mediation adapters for iOS to CocoaPods.
- Add the following line to your project's Podfile: pod 'GoogleMobileAdsMediationInMobi' - From the command line run: ```bash pod install --repo-update ``` ### Project settings Add `-ObjC` flag to the **Other Linker Flags** under **Application Target \> Build Settings**. ## Step 4: Implement privacy settings on InMobi SDK ### EU Consent and GDPR To [comply with the Google EU User Consent Policy](https://www.google.com/about/company/consentstaging.html), you must make certain disclosures to your users in the European Economic Area (EEA), the UK, and Switzerland, and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). You are responsible for verifying that consent is propagated to each ad source in your mediation chain. InMobi iOS adapter version 10.7.5.0 and later supports passing GDPR consent signals from consent management platforms that integrate with IAB's Transparency and Consent Framework (TCF) to InMobi SDK. For more information, see [GDPR](https://support.inmobi.com/monetize/privacy/gdpr). ### US states privacy laws [US states privacy laws](https://support.google.com/admanager/answer/9561023) require giving users the right to opt out of the "sale" of their "personal information" (as the law defines those terms), with the opt-out offered through a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The [US states privacy laws compliance guide](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/privacy/us-states) offers the ability to enable [restricted data processing](https://privacy.google.com/businesses/rdp/) for Google ad serving, but Google is unable to apply this setting to each ad network in your mediation chain. Therefore, you must identify each ad network in your mediation chain that may participate in the sale of personal information and follow guidance from each of those networks to ensure compliance. In version 10.5.6.0, the InMobi adapter added support to read IAB U.S. Privacy string from `NSUserDefaults`. Follow the instructions in [U.S. states privacy laws documentation](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/privacy/us-states.md.txt#iab_signal) to set the U.S. Privacy string in `NSUserDefaults`. Additionally, see InMobi's [CCPA documentation](https://support.inmobi.com/monetize/privacy/ccpa/#introduction) for guidelines on how to enable CCPA settings in InMobi dashboard. ## Step 5: Additional code required ### Implement SKAdNetwork Follow [InMobi's documentation](https://support.inmobi.com/monetize/ios-guidelines/preparing-for-ios-14) to add the SKAdNetwork identifiers to your project's `Info.plist` file. ## Step 6: Test your implementation ### Enable test ads Make sure you [register your test device](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/test-ads.md.txt#enable_test_devices) for Ad Manager and [enable test mode](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation/inmobi.md.txt#turn-on-test-mode) in InMobi UI. > [!IMPORTANT] > **Important:** Disable test mode for Ad Manager and InMobi before releasing your app. ### Verify test ads To verify that you are receiving test ads from InMobi, enable [single ad source testing](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/ad-inspector.md.txt#single_ad_source_testing) in ad inspector using the **InMobi (Bidding) and InMobi (Waterfall)** ad source(s). ## Optional steps ### Network-specific parameters The InMobi adapter supports additional request parameters that can be passed to the adapter using the `GADInMobiExtras` class. `GADInMobiExtras` includes the following properties common for all supported ad formats: | Request parameters and values || |---|---| | `setAgeGroup` The user's age group. | `kIMSDKAgeGroupBelow18` `kIMSDKAgeGroupBetween18And24` `kIMSDKAgeGroupBetween25And29` `kIMSDKAgeGroupBetween30And34` `kIMSDKAgeGroupBetween35And44` `kIMSDKAgeGroupBetween45And54` `kIMSDKAgeGroupBetween55And64` `kIMSDKAgeGroupAbove65` | | `setEducationType` The education level of the user. | `kIMSDKEducationHighSchoolOrLess` `kIMSDKEducationCollegeOrGraduate` `kIMSDKEducationPostGraduateOrAbove` | | `setLogLevel` | `kIMSDKLogLevelNone` `kIMSDKLogLevelError` `kIMSDKLogLevelDebug` | | `setAge` | **Integer.** The user's age. | | `setYearOfbirth` | **Integer.** The user's year of birth. | | `setPostalCode` | **String**. The user's postal code. Usually a five-digit number. | | `setAreaCode` | **String**. The user's telephone area code (part of the phone number). | | `setLanguage` | **String**. The user's native language (if known). | | `setLoginId` | **String**. A login ID in the publisher's domain. | | `setSessionId` | **String**. A session ID in the publisher's domain. | | `setLocationWithCityStateCountry` | **String**. Location with city, state, and country as parameters. | | `setKeywords` | **String**. Any contextually relevant keywords to be passed in the ad request. | | `setInterests` | **String**. Any contextually relevant strings to be passed in the ad request. | | `setAdditionalParameters` | **Dictionary**. Any additional values to be passed in the ad request. | Here's a code example of how to set these ad request parameters: ### Swift ```swift let request = GAMRequest() let extras = GADInMobiExtras() extras.ageGroup = kIMSDKAgeGroupBetween35And54 extras.areaCode = "12345" request.registerAdNetworkExtras(extras) ``` ### Objective-C ```objective-c GAMRequest *request = [GAMRequest request]; GADInMobiExtras *extras = [[GADInMobiExtras alloc] init]; extras.ageGroup = kIMSDKAgeGroupBetween35And54; extras.areaCode = @"12345"; [request registerAdNetworkExtras:extras]; ```
### Using native ads #### Ad rendering The InMobi adapter returns its native ads as `GADNativeAd` objects. It populates the following [fields](https://support.google.com/admanager/answer/6075370) for a [`GADNativeAd`](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/api/reference/Classes/GADNativeAd.md.txt). | Field | Assets always included by InMobi adapter | |---|---| | Headline | Yes | | Image | [1](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/mediation/inmobi.md.txt#image-footnote) | | Media view | Yes | | Body | Yes | | App icon | Yes | | Call to action | Yes | | Star rating | | | Store | | | Price | | ^1^ The InMobi adapter does not provide direct access to the main image asset for its native ads. Instead, the adapter populates the [`GADMediaView`](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/api/reference/Classes.md.txt#gadmediaview) with a video or an image. ### Impression and click tracking Clicks are detected by Google Mobile Ads SDK and are forwarded to InMobi, so click reporting will be in sync. Google Mobile Ads SDK uses the InMobi SDK's callbacks for impression tracking, so the reports on both dashboards should match up with few to no discrepancies. ## Error codes If the adapter fails to receive an ad from InMobi, publishers can check the underlying error from the ad response using [`GADResponseInfo.adNetworkInfoArray`](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/api/reference/Classes/GADResponseInfo.md.txt#adnetworkinfoarray) under the following classes: ```objective-c GADMAdapterInMobi GADMediationAdapterInMobi ``` Here are the codes and accompanying messages thrown by the InMobi adapter when an ad fails to load: | Error code | Reason | |---|---| | 101 | InMobi server parameters configured in the Ad Manager UI are missing/invalid. | | 102 | The requested ad size does not match an InMobi supported banner size. | | 103 | An InMobi ad is already loaded for this network configuration. | | 104 | InMobi native ad returned with missing native assets, or required image assets failed to download. | | 105 | An InMobi ad is not ready to be shown. | | 106 | An empty or nil bid token is returned by InMobi. | | Other | InMobi SDK returned an error. See `IMRequestStatus.h` for more details. | ## InMobi iOS Mediation Adapter Changelog #### [Version 11.5.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.5.0.0.zip) - Verified compatibility with InMobi SDK 11.5.0. Built and tested with: - Google Mobile Ads SDK version 13.11.0. - InMobi SDK version 11.5.0. #### [Version 11.4.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.4.1.0.zip) - Verified compatibility with InMobi SDK 11.4.1. Built and tested with: - Google Mobile Ads SDK version 13.7.0. - InMobi SDK version 11.4.1. #### [Version 11.4.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.4.0.0.zip) - Verified compatibility with InMobi SDK 11.4.0. - Updated the minimum Google Mobile Ads iOS SDK version to `13.3` to relax and allow minor versions. Built and tested with: - Google Mobile Ads SDK version 13.6.0. - InMobi SDK version 11.4.0. #### [Version 11.3.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.3.0.0.zip) - Verified compatibility with InMobi SDK 11.3.0. Built and tested with: - Google Mobile Ads SDK version 13.3.0. - InMobi SDK version 11.3.0. #### [Version 11.2.0.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.2.0.1.zip) - Adapter now forwards the `ageRestrictedTreatment` Google Mobile Ads SDK flag to InMobi SDK's COPPA API. Built and tested with: - Google Mobile Ads SDK version 13.3.0. - InMobi SDK version 11.2.0. #### [Version 11.2.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.2.0.0.zip) - Verified compatibility with InMobi SDK 11.2.0. Built and tested with: - Google Mobile Ads SDK version 13.2.0. - InMobi SDK version 11.2.0. #### [Version 11.1.1.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.1.1.1.zip) - Updated the Google Mobile Ads SDK dependency to version 13.0.0. Built and tested with: - Google Mobile Ads SDK version 13.0.0. - InMobi SDK version 11.1.1. #### [Version 11.1.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.1.1.0.zip) - Verified compatibility with InMobi SDK 11.1.1. Built and tested with: - Google Mobile Ads SDK version 12.14.0. - InMobi SDK version 11.1.1. #### [Version 11.1.0.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.1.0.1.zip) - Added support for forwarding the `tagForUnderAgeOfConsent` Google Mobile Ads SDK parameter to the InMobi SDK. Built and tested with: - Google Mobile Ads SDK version 12.14.0. - InMobi SDK version 11.1.0. #### [Version 11.1.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.1.0.0.zip) - Verified compatibility with InMobi SDK 11.1.0. Built and tested with: - Google Mobile Ads SDK version 12.13.0. - InMobi SDK version 11.1.0. #### [Version 11.0.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-11.0.0.0.zip) - Verified compatibility with InMobi SDK 11.0.0. Built and tested with: - Google Mobile Ads SDK version 12.12.0. - InMobi SDK version 11.0.0. #### [Version 10.8.8.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.8.0.zip) - Verified compatibility with InMobi SDK 10.8.8. Built and tested with: - Google Mobile Ads SDK version 12.11.0. - InMobi SDK version 10.8.8. #### [Version 10.8.6.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.6.0.zip) - Verified compatibility with InMobi SDK 10.8.6. Built and tested with: - Google Mobile Ads SDK version 12.7.0. - InMobi SDK version 10.8.6. #### [Version 10.8.3.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.3.1.zip) - For banner bidding requests, removes a validation check that enforces the banner size to map to a standard InMobi ad size. If InMobi bidder bids on a non-standard size, the adapter now allows that request to render. - Removed account ID and placement ID validation checks on bidding requests. Built and tested with: - Google Mobile Ads SDK version 12.4.0. - InMobi SDK version 10.8.3. #### [Version 10.8.3.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.3.0.zip) - Added support for rewarded interstitial ads. - Added a guard statement in bidding signals for rewarded ads such that it does not bid if a previously loaded rewarded ad for the placement ID was not used. - Verified compatibility with InMobi SDK 10.8.3. Built and tested with: - Google Mobile Ads SDK version 12.4.0. - InMobi SDK version 10.8.3. #### [Version 10.8.2.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.2.0.zip) - Verified compatibility with InMobi SDK 10.8.2. Built and tested with: - Google Mobile Ads SDK version 12.2.0. - InMobi SDK version 10.8.2. #### [Version 10.8.0.2](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.0.2.zip) - Enabled `-fobjc-arc` and `-fstack-protector-all` flags. Built and tested with: - Google Mobile Ads SDK version 12.1.0. - InMobi SDK version 10.8.0. #### [Version 10.8.0.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.0.1.zip) - Now requires Google Mobile Ads SDK version 12.0.0 or higher. Built and tested with: - Google Mobile Ads SDK version 12.0.0. - InMobi SDK version 10.8.0. #### [Version 10.8.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.8.0.0.zip) - Verified compatibility with InMobi SDK 10.8.0. Built and tested with: - Google Mobile Ads SDK version 11.12.0. - InMobi SDK version 10.8.0. #### [Version 10.7.8.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.8.0.zip) - Verified compatibility with InMobi SDK 10.7.8. Built and tested with: - Google Mobile Ads SDK version 11.10.0. - InMobi SDK version 10.7.8. #### [Version 10.7.5.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.5.1.zip) - Updated `CFBundleShortVersionString` to have three components instead of four. Built and tested with: - Google Mobile Ads SDK version 11.10.0. - InMobi SDK version 10.7.5. #### [Version 10.7.5.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.5.0.zip) - Verified compatibility with InMobi SDK 10.7.5. Built and tested with: - Google Mobile Ads SDK version 11.7.0. - InMobi SDK version 10.7.5. #### [Version 10.7.4.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.4.0.zip) - Verified compatibility with InMobi SDK 10.7.4. Built and tested with: - Google Mobile Ads SDK version 11.6.0. - InMobi SDK version 10.7.4. #### [Version 10.7.2.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.2.0.zip) - Verified compatibility with InMobi SDK 10.7.2. Built and tested with: - Google Mobile Ads SDK version 11.3.0. - InMobi SDK version 10.7.2. #### [Version 10.7.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.7.1.0.zip) - Verified compatibility with InMobi SDK 10.7.1. Built and tested with: - Google Mobile Ads SDK version 11.2.0. - InMobi SDK version 10.7.1. #### [Version 10.6.4.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.6.4.0.zip) - Verified compatibility with InMobi SDK 10.6.4. - Replaced the deprecated method `GADMobileAds.sharedInstance.sdkVersion` with `GADMobileAds.sharedInstance.versionNumber`. - Replaced the use of `NSUserDefaults` with `CFPreferences` functions. - Now requires minimum iOS version 12.0. - Now requires Google Mobile Ads SDK version 11.0 or higher. - Included `Info.plist` in the frameworks within `InMobiAdapter.xcframework`. Built and tested with: - Google Mobile Ads SDK version 11.0.1. - InMobi SDK version 10.6.4. #### [Version 10.6.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.6.0.0.zip) - Verified compatibility with InMobi SDK 10.6.0. - Added watermark support for bidding banner, interstitial and rewarded ad formats. Built and tested with: - Google Mobile Ads SDK version 10.13.0. - InMobi SDK version 10.6.0. #### [Version 10.5.8.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.5.8.0.zip) - Verified compatibility with InMobi SDK 10.5.8. Built and tested with: - Google Mobile Ads SDK version 10.10.0. - InMobi SDK version 10.5.8. #### [Version 10.5.6.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.5.6.0.zip) - Added support to read IAB U.S. Privacy string from NSUserDefaults. - Verified compatibility with InMobi SDK 10.5.6. - Added bidding support for banner (includes MREC), interstitial and rewarded ad formats. Built and tested with: - Google Mobile Ads SDK version 10.9.0. - InMobi SDK version 10.5.6. #### [Version 10.5.5.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.5.5.0.zip) - Now requires Google Mobile Ads SDK version 10.4.0 or higher. - Updated the adapter to use the `didRewardUser` API. - Updated the adapter to initialize InMobi SDK on main thread. Built and tested with: - Google Mobile Ads SDK version 10.4.0. - InMobi SDK version 10.5.5. #### [Version 10.5.4.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.5.4.0.zip) - Verified compatibility with InMobi SDK 10.5.4. - Removed use of deprecated gender, birthday and location mediation APIs. - Removed support for the `armv7` architecture. - Now requires minimum iOS version 11.0. - Now requires Google Mobile Ads SDK version 10.0.0 or higher. Built and tested with: - Google Mobile Ads SDK version 10.2.0. - InMobi SDK version 10.5.4. Additional notes: - This release was created before [Version 10.1.3.0](https://github.com/googleads/googleads-mobile-ios-mediation/blob/main/adapters/InMobi/CHANGELOG.md#version-10130) so it does not use the `didRewardUser` API. #### [Version 10.1.3.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.1.3.0.zip) - Verified compatibility with InMobi SDK 10.1.3. - Now requires Google Mobile Ads SDK version 10.4.0 or higher. - Updated the adapter to use the `didRewardUser` API. Built and tested with: - Google Mobile Ads SDK version 10.5.0. - InMobi SDK version 10.1.3. Additional notes: - This release was created after [Version 10.5.4.0](https://github.com/googleads/googleads-mobile-ios-mediation/blob/main/adapters/InMobi/CHANGELOG.md#version-10540). #### [Version 10.1.2.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.1.2.1.zip) - Verified compatibility with InMobi SDK 10.1.2. - Fixed an issue where the native ads could become blank in scrollable UIs. - Updated the adapter to use the new mediation APIs. - Added support for forwarding the COPPA value to InMobi SDK. Built and tested with: - Google Mobile Ads SDK version 9.14.0. - InMobi SDK version 10.1.2. #### [Version 10.1.2.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.1.2.0.zip) - Verified compatibility with InMobi SDK 10.1.2. Built and tested with: - Google Mobile Ads SDK version 9.13.0. - InMobi SDK version 10.1.2. #### [Version 10.1.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.1.1.0.zip) - Verified compatibility with InMobi SDK 10.1.1. Built and tested with: - Google Mobile Ads SDK version 9.12.0. - InMobi SDK version 10.1.1. #### [Version 10.1.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.1.0.0.zip) - Verified compatibility with InMobi SDK 10.1.0. - Updated the adapter to use the `didRewardUser` API. - Now requires Google Mobile Ads SDK version 9.8.0 or higher. Built and tested with: - Google Mobile Ads SDK version 9.11.0. - InMobi SDK version 10.1.0. #### [Version 10.0.7.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.7.0.zip) - Verified compatibility with InMobi SDK 10.0.7. Built and tested with: - Google Mobile Ads SDK version 9.5.0. - InMobi SDK version 10.0.7. #### [Version 10.0.5.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.5.0.zip) - Verified compatibility with InMobi SDK 10.0.5. Built and tested with: - Google Mobile Ads SDK version 9.2.0. - InMobi SDK version 10.0.5. #### [Version 10.0.2.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.2.1.zip) - Verified compatibility with Google Mobile Ads SDK version 9.0.0. - Now requires Google Mobile Ads SDK version 9.0.0 or higher. Built and tested with: - Google Mobile Ads SDK version 9.0.0. - InMobi SDK version 10.0.2. #### [Version 10.0.2.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.2.0.zip) - Verified compatibility with InMobi SDK 10.0.2. Built and tested with - Google Mobile Ads SDK version 8.13.0. - InMobi SDK version 10.0.2. #### [Version 10.0.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.1.0.zip) - Verified compatibility with InMobi SDK 10.0.1. Built and tested with - Google Mobile Ads SDK version 8.12.0. - InMobi SDK version 10.0.1. #### [Version 10.0.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-10.0.0.0.zip) - Verified compatibility with InMobi SDK 10.0.0. - Now requires minimum iOS version 10.0. Built and tested with - Google Mobile Ads SDK version 8.11.0. - InMobi SDK version 10.0.0. #### [Version 9.2.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.2.1.0.zip) - Verified compatibility with InMobi SDK 9.2.1. Built and tested with - Google Mobile Ads SDK version 8.9.0. - InMobi SDK version 9.2.1. #### [Version 9.2.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.2.0.0.zip) - Verified compatibility with InMobi SDK 9.2.0. - Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher. Built and tested with - Google Mobile Ads SDK version 8.8.0. - InMobi SDK version 9.2.0. #### [Version 9.1.7.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.1.7.0.zip) - Verified compatibility with InMobi SDK 9.1.7. - Now requires Google Mobile Ads SDK version 8.3.0 or higher. Built and tested with - Google Mobile Ads SDK version 8.3.0. - InMobi SDK version 9.1.7. #### [Version 9.1.5.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.1.5.0.zip) - Verified compatibility with InMobi SDK 9.1.5. - Now requires Google Mobile Ads SDK version 8.1.0 or higher. Built and tested with - Google Mobile Ads SDK version 8.1.0. - InMobi SDK version 9.1.5. #### [Version 9.1.1.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.1.1.1.zip) - Updated the adapter to use the `.xcframework` format. - Now requires Google Mobile Ads SDK version 8.0.0 or higher. Built and tested with - Google Mobile Ads SDK version 8.0.0. - InMobi SDK version 9.1.1. #### [Version 9.1.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.1.1.0.zip) - Verified compatibility with InMobi SDK 9.1.1. - Now requires Google Mobile Ads SDK version 7.68.0 or higher. Built and tested with - Google Mobile Ads SDK version 7.68.0. - InMobi SDK version 9.1.1. #### [Version 9.1.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.1.0.0.zip) - Verified compatibility with InMobi SDK 9.1.0. - Now requires Google Mobile Ads SDK version 7.65.0 or higher. Built and tested with - Google Mobile Ads SDK version 7.65.0. - InMobi SDK version 9.1.0. #### [Version 9.0.7.2](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.0.7.2.zip) - Rewarded ads no longer default to coppa=0 when child directed treatment is unspecified. Built and tested with - Google Mobile Ads SDK version 7.61.0. - InMobi SDK version 9.0.7. #### [Version 9.0.7.1](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.0.7.1.zip) - Now requires Google Mobile Ads SDK version 7.61.0 or higher. - Added standardized adapter error codes and messages. Built and tested with - Google Mobile Ads SDK version 7.61.0. - InMobi SDK version 9.0.7. #### [Version 9.0.7.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.0.7.0.zip) - Verified compatibility with InMobi SDK 9.0.7. Built and tested with - Google Mobile Ads SDK version 7.60.0. - InMobi SDK version 9.0.7. #### [Version 9.0.6.0](https://dl.google.com/googleadmobadssdk/mediation/ios/inmobi/InMobiAdapter-9.0.6.0.zip) - Verified compatibility with InMobi SDK 9.0.6. - Updated InMobi iOS adapter CocoaPod dependency to use `InMobiSDK/Core`. - Now requires Google Mobile Ads SDK version 7.60.0 or higher. Built and tested with - Google Mobile Ads SDK version 7.60.0 - InMobi SDK version 9.0.6 #### Version 9.0.4.0 - Verified compatibility with InMobi SDK 9.0.4. - Adapter now fails early when InMobi SDK initialization fails. - Removed support for the i386 architecture. Built and tested with - Google Mobile Ads SDK version 7.57.0 - InMobi SDK version 9.0.4 #### Version 9.0.0.0 - Verified compatibility with InMobi SDK 9.0.0. - Removed bidding capability for banner, interstitial, and rewarded formats. Built and tested with - Google Mobile Ads SDK version 7.53.1 - InMobi SDK version 9.0.0 #### Version 7.4.0.0 - Verified compatibility with InMobi SDK 7.4.0. #### Version 7.3.2.1 - Fixed an issue where the adapter fails to initialize due to invalid mediation configurations. #### Version 7.3.2.0 - Verified compatibility with InMobi SDK 7.3.2. - Added bidding capability to the adapter for banner, interstitial and rewarded ad formats. #### Version 7.3.0.0 - Verified compatibility with InMobi SDK 7.3.0. - Removed support for Native Content and App Install ad requests. Apps must use the Unified Native Ads API to request native ads. - Now requires Google Mobile Ads SDK version 7.46.0 or higher. #### Version 7.2.7.0 - Verified compatibility with InMobi SDK 7.2.7. - Updated the adapter to use the new rewarded API. - Now requires Google Mobile Ads SDK version 7.42.2 or higher. - Added support for flexible banner ad sizes. #### Version 7.2.4.0 - Verified compatibility with InMobi SDK 7.2.4. #### Version 7.2.1.0 - Verified compatibility with InMobi SDK 7.2.1. #### Version 7.2.0.0 - Verified compatibility with InMobi SDK 7.2.0. #### Version 7.1.2.0 - Verified compatibility with InMobi SDK 7.1.2. #### Version 7.1.1.2 - Added `adapterDidCompletePlayingRewardBasedVideoAd:` callback to the adapter. #### Version 7.1.1.1 - Added the `GADInMobiConsent` class which provides `updateGDPRConsent` and `getConsent` methods. #### Version 7.1.1.0 - Verified compatibility with InMobi SDK 7.1.1. #### Version 7.1.0.0 - Verified compatibility with InMobi SDK 7.1.0. #### Version 7.0.4.1 - Fixed an issue causing duplicate symbol errors when the adapter was used with those of other networks. #### Version 7.0.4.0 - Updated the adapter to make it compatibility with InMobi SDK 7.0.4. - Added support for native video ads. - InMobi's SDK does not provide images for ads containing video assets. To avoid potential NullPointerExceptions, when the adapter receives one of these ads it will automatically create a blank NativeAd.Image and include it in the images asset array in the ad object received by the app. Publishers using this adapter are encouraged to avoid using the image assets directly when mediating to InMobi, and instead use GADMediaView in their UI. GADMediaView will automatically display video assets for ads that contain them, and an image asset for ads that don't. #### Version 6.2.1.0 - Verified compatibility with inMobi SDK 6.2.1 #### Earlier versions - Support for banners, interstitials, rewarded video and native ad formats.