Integrate Verve HyBid SDK with bidding

Select platform: Android iOS Android (Legacy)

This guide shows you how to use Google Mobile Ads SDK to load and display ads from Verve HyBid SDK using mediation 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  1
Waterfall
Formats
Banner
Interstitial
Rewarded Interstitial
Rewarded
Native

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.

Step 1: Set up configurations in Verve HyBid SDK UI

For configuration setup, contact Verve.

Step 2: Set up Verve HyBid SDK demand in Ad Manager UI

Sign in to your Ad Manager account.

Enable secure signal sharing

Navigate to Admin > Global settings. Go to the Ad Exchange account settings tab and review and toggle on Secure signal sharing. Click Save.

Share secure signal on bid requests

Navigate to Inventory > Secure Signals. Under Secure signals, search for Verve HyBid SDK and toggle on Enable app integration.

Click Save.

Allow secure signal sharing for SDK Bidding

Navigate to Delivery > Demand channel settings. In the Default settings tab, toggle on Allow secure signal sharing for SDK Bidding.

Click Save.

Configure Verve HyBid SDK bidding

Navigate to Delivery > Bidders, and click Go to SDK Bidding.

Click New bidder.

Select Verve Group as the bidder.

Click Continue to enable SDK Bidding for this bidder.

Click Done.

Configure ad unit mapping

Navigate to Delivery > Bidders, and click Go to SDK Bidding.

Select the company for Verve HyBid SDK.

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 Zone ID and AppToken obtained in the previous section.

If you are configuring ad unit mapping for a rewarded interstitial ad within the Ad Manager UI, choose the Rewarded format and use the rewarded interstitial placement ID.

Finally, click Save.

Add Verve Group to GDPR and US state regulations ad partners list

Follow the steps in European regulations settings and US state regulations settings to add Verve Group to the European and US state regulations ad partners list in the Ad Manager UI.

Step 3: Import the Verve HyBid SDK and adapter

Use Swift Package Manager

Before you continue, you must have the minimum supported adapter version 3.8.0.0.

To 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.

Use CocoaPods

  • Add the following line to your project's Podfile:

    pod 'GoogleMobileAdsMediationVerve'

  • From the command line run:

    pod install --repo-update

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 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

Step 4: Implement privacy settings on Verve SDK

To comply with Google EU User Consent Policy, 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 consent is propagated to each ad source in your mediation chain. Google is unable to pass the user's consent choice to such networks automatically.

Verve HyBid SDK automatically reads GDPR consent set by consent management platforms including UMP SDK. For more information, see GDPR TCF Compliance.

US states privacy laws

US states privacy laws 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 offers the ability to enable restricted data processing 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

HyBidUserDataManager.sharedInstance().setIABUSPrivacyString(usPrivacyString)

Replace usPrivacyString with your US privacy string.

Objective-C

[[HyBidUserDataManager sharedInstance] setIABUSPrivacyString:kUSPrivacyString];

Replace kUSPrivacyString with your US privacy string.

For details, see Verve HyBid SDK privacy documentation on CCPA Compliance.

Step 5: Add required code

Implement SKAdNetwork

Follow Verve HyBid SDK's documentation 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 for Ad Manager.

Verify test ads

To verify that you are receiving test ads from Verve HyBid SDK, enable single ad source testing in ad inspector using the Verve (Bidding) ad source(s).

Follow Verve HyBid SDK's documentation 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 under the following classes:

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 Reason
100 to 106 Verve HyBid SDK returned an error.
101 Missing app token.
102 User is a child.
103 Verve HyBid SDK fails to initialize.
104 Invalid ad configuration.
105 Unsupported banner size.
106 The full screen ad is not ready for presentation.
115 Ad unit ID is missing. Cannot load ad.
116 Ad is not ready. Cannot display the ad.

Verve iOS Mediation Adapter Changelog

Version 3.9.0.0

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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.