This guide shows you how to use Google Mobile Ads SDK to load and display ads from Verve HyBid SDK using [AdMob Mediation](https://developers.google.com/admob/ios/mediation.md.txt) covering bidding integrations. It covers how to add Verve HyBid SDK to an ad unit's mediation configuration, and how to integrate the Verve HyBid SDK and adapter into an iOS app. ## Supported integrations and ad formats The mediation adapter for Verve HyBid SDK has the following capabilities: | Integration || |---|---| | Bidding | Yes [^1^](https://developers.google.com/admob/ios/mediation/verve.md.txt#bidding-footnote) | | Waterfall | | | Banner | Yes | | Interstitial | Yes | | Rewarded Interstitial | Yes | | Rewarded | Yes | | Native | Yes | ^1^ Bidding integration is in alpha. Reach out to your your account manager to request access. ## Prerequisites Before you continue, verify the following: - iOS deployment target of 13.0 or later. - Latest Google Mobile Ads SDK version. - [Set up AdMob Mediation](https://developers.google.com/admob/ios/mediation.md.txt). ## Step 1: Set up configurations in Verve HyBid SDK UI For configuration setup, [contact Verve](https://verve.com/contact/). ## Step 2: Set up Verve HyBid SDK demand in AdMob UI ### Configure mediation settings for your ad unit You need to add Verve HyBid SDK to the mediation configuration for your ad unit. First, sign in to your [AdMob account](https://apps.admob.com/). Next, navigate to the **Mediation** tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to [Add Verve HyBid SDK as an ad source](https://developers.google.com/admob/ios/mediation/verve.md.txt#add-ad-source). To create a new mediation group, select **Create Mediation Group**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-create.png) Enter your ad format and platform, then click **Continue**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-new-iOS.png) Give your mediation group a name, and select locations to target. Next, set the mediation group status to **Enabled** , and then click **Add Ad Units**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-details-iOS.png) Associate this mediation group with one or more of your existing AdMob ad units. Then click **Done**. ![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-select-iOS.png) You should now see the ad units card populated with the ad units you selected: ![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-card-iOS.png) ### Add Verve HyBid SDK as an ad source
In the **Ad Sources** section, find the **Bidding** card and select **Add ad source** . Then select **Verve HyBid SDK** . Click **How to sign a partnership agreement** and [set up a bidding partnership](https://support.google.com/admob/answer/9842838) with Verve HyBid SDK. ![](https://developers.google.com/static/admob/images/mediation/verve/bidding-agreement-1.png) Click **Acknowledge \& agree** , then click **Continue** . ![](https://developers.google.com/static/admob/images/mediation/verve/bidding-agreement-2.png) If you already have a mapping for Verve HyBid SDK, you can select it. Otherwise, click **Add mapping** . ![](https://developers.google.com/static/admob/images/mediation/verve/bidding-add-mapping-1-iOS.png) Next, enter the **Zone ID** and **AppToken** obtained in the previous section. Then click **Done** . ![](https://developers.google.com/static/admob/images/mediation/verve/bidding-add-mapping-2-iOS.png) ### Add Verve Group 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/admob/answer/10113004#adding_ad_partners_to_published_gdpr_messages) and [US state regulations settings](https://support.google.com/admob/answer/14125907) to add **Verve Group** to the European and US state regulations ad partners list in the AdMob UI. ## Step 3: Import the Verve HyBid SDK and adapter > [!NOTE] > **Note:** Failure to integrate the compatible Verve HyBid SDK 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 3.8.0.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-verve.git 3. In **Dependency Rule** , select **Branch**. 4. In the text field, enter `main`. ### Manual integration - Download the latest version of the Verve iOS SDK and link `VerveSDK.framework` in your project. - Download the latest version of the Verve adapter from the download link in the [Changelog](https://developers.google.com/admob/ios/mediation/verve.md.txt#verve-ios-mediation-adapter-changelog) and link `VerveAdapter.framework` in your project. - Add the following frameworks to your project: - `AdSupport` - `AVFoundation` - `CoreGraphics` - `CoreMedia` - `CoreTelephony` - `StoreKit` - `SystemConfiguration` - `UIKit` - `WebKit` - `libz.tbd` ### 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 'GoogleMobileAdsMediationVerve' - From the command line run: ```bash pod install --repo-update ``` ## Step 4: Implement privacy settings on Verve 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. Verve HyBid SDK iOS adapter version 3.7.1.1 and later supports passing GDPR consent signals from consent management platforms that integrate with IAB's Transparency and Consent Framework (TCF) to Verve HyBid SDK SDK. For more information, see [GDPR TCF Compliance](https://github.com/pubnative/pubnative-hybid-ios-sdk/wiki/GDPR-TCF-Compliance). ### US states privacy laws [US states privacy laws](https://support.google.com/admob/answer/9561022) 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/admob/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. Verve HyBid SDK supports privacy settings through a method. The following sample code passes this consent information to Verve HyBid SDK. If you pass consent information to Verve HyBid SDK manually, we recommend that you call the example before you request ads through Google Mobile Ads SDK. ### Swift ```swift HyBidUserDataManager.sharedInstance().setIABUSPrivacyString(usPrivacyString) ``` Replace usPrivacyString with your US privacy string. ### Objective-C ```objective-c [[HyBidUserDataManager sharedInstance] setIABUSPrivacyString:kUSPrivacyString]; ``` Replace kUSPrivacyString with your US privacy string. For details, see Verve HyBid SDK privacy documentation on [CCPA Compliance](https://github.com/pubnative/pubnative-hybid-ios-sdk/wiki/CCPA-Compliance). ## Step 5: Add required code ### Implement SKAdNetwork Follow [Verve HyBid SDK's documentation](https://developers.verve.com/docs/ios-14-and-skadnetwork) 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/admob/ios/test-ads.md.txt#enable_test_devices) for AdMob. > [!IMPORTANT] > **Important:** Disable test mode for AdMob and Verve HyBid SDK before releasing your app. ### Verify test ads To verify that you are receiving test ads from Verve HyBid SDK, enable [single ad source testing](https://developers.google.com/admob/ios/ad-inspector.md.txt#single_ad_source_testing) in ad inspector using the **Verve (Bidding)** ad source(s). Follow [Verve HyBid SDK's documentation](https://github.com/pubnative/pubnative-hybid-ios-sdk/wiki/Setup-HyBid#advanced-configurations) for additional configuration. ## Error codes If the adapter fails to receive an ad from Verve HyBid SDK, publishers can check the underlying error from the ad response using [`GADResponseInfo.adNetworkInfoArray`](https://developers.google.com/admob/ios/api/reference/Classes/GADResponseInfo.md.txt#adnetworkinfoarray) under the following classes: ```objective-c GADMAdapterVerve GADMAdapterVerveRewardBasedVideoAd GADMediationAdapterVerve ``` Here are the codes and accompanying messages thrown by the Verve HyBid SDK adapter when an ad fails to load: | Error code | Domain | Reason | |---|---|---| | 100 to 106 | Verve HyBid SDK returned an error. | | 101 | com.google.mediation.verve | Server configuration missing a required app token. | | 102 | com.google.mediation.verve | User is a child. | | 103 | com.google.mediation.verve | Verve HyBid SDK fails to initialize. | | 104 | com.google.mediation.verve | Invalid ad configuration for loading an ad. | | 105 | com.google.mediation.verve | Unsupported banner size. | | 106 | com.google.mediation.verve | The full screen ad is not ready for presentation. | | 115 | com.google.mediation.verve | Ad unit ID is missing. Cannot load ad. | ## Verve iOS Mediation Adapter Changelog #### [Version 3.9.3.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.9.3.0.zip) - Verified compatibility with HyBid SDK version 3.9.3. Built and tested with: - Google Mobile Ads SDK version 13.11.0. - HyBid SDK version 3.9.3. #### [Version 3.9.2.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.9.2.0.zip) - Verified compatibility with HyBid SDK version 3.9.2. Built and tested with: - Google Mobile Ads SDK version 13.9.0. - HyBid SDK version 3.9.2. #### [Version 3.9.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.9.1.0.zip) - Verified compatibility with HyBid SDK version 3.9.1. Built and tested with: - Google Mobile Ads SDK version 13.8.0. - HyBid SDK version 3.9.1. #### [Version 3.9.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.9.0.0.zip) - Updated the minimum Google Mobile Ads iOS SDK version to `13.3` to relax and allow minor versions. - Verified compatibility with HyBid SDK version 3.9.0. Built and tested with: - Google Mobile Ads SDK version 13.6.0. - HyBid SDK version 3.9.0. #### [Version 3.8.1.1](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.8.1.1.zip) - Filter age-restricted requests for Verve SDK when new `ageRestrictedTreatment` is set to `GADAgeRestrictedTreatmentChild`. Built and tested with: - Google Mobile Ads SDK version 13.4.0. - HyBid SDK version 3.8.1. #### [Version 3.8.1.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.8.1.0.zip) - Verified compatibility with HyBid SDK version 3.8.1. Built and tested with: - Google Mobile Ads SDK version 13.4.0. - HyBid SDK version 3.8.1. #### [Version 3.8.0.0](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.8.0.0.zip) - Removed banner size check from the adapter to resolve signal collection failures and ad load failures. - Verified compatibility with HyBid SDK version 3.8.0. Built and tested with: - Google Mobile Ads SDK version 13.2.0. - HyBid SDK version 3.8.0. #### [Version 3.7.1.3](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.7.1.3.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. - HyBid SDK version 3.7.1. #### [Version 3.7.1.2](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.7.1.2.zip) - Updated the CocoaPods minimum iOS version to `13.0`. Built and tested with: - Google Mobile Ads SDK version 13.0.0. - HyBid SDK version 3.7.1. #### [Version 3.7.1.1](https://dl.google.com/googleadmobadssdk/mediation/ios/verve/VerveAdapter-3.7.1.1.zip) - Initial Release! - Supports bidding banner, interstitial, rewarded, rewarded interstitial and native ad formats. - Verified compatibility with HyBid SDK version 3.7.1. Built and tested with: - Google Mobile Ads SDK version 12.13.0. - HyBid SDK version 3.7.1.