Integrate Moloco with bidding

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Moloco using mediation, covering bidding integrations. It covers how to add Moloco to an ad unit's mediation configuration, and how to integrate the Moloco SDK and adapter into an iOS app.

Supported integrations and ad formats

The mediation adapter for Moloco has the following capabilities:

Integration
Bidding
Waterfall
Formats
App Open
Banner
Interstitial
Rewarded
Rewarded Interstitial
Native

Requirements

• iOS deployment target of 12.0 or higher

• Moloco adapter 3.9.1.0 or higher

• Latest Google Mobile Ads SDK

• Complete the mediation Get started guide.

Step 1: Set up configurations in Moloco UI

Log in to the Moloco Publisher Portal.

Navigate to Overview > Apps tab, then click the Add App button to create a new app.

Select the OS and Privacy Settings for your app, fill out the rest of the form, and then click Create.

Once your app is created, select it from the Apps tab to view the details and take note of the App Key.

Navigate to the Overview > Ad Units tab, select the app from the drop-down menu, and then click New Ad Unit.

Select In-app bidding as the Auction method and fill out the rest of the form. Then, click Create.

Navigate to your newly created ad unit under the Ad Units tab to view its details. Take note of the Ad Unit ID.

Step 2: Set up Moloco 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 Moloco Ads 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 Moloco bidding

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

Click New bidder.

Select Moloco Ads 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 Moloco Ads 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 App Key and Ad Unit ID obtained in the previous section.

Finally, click Save.

Important: Target the selected ad unit by at least one yield group.

Add Moloco Ads to European and US state regulations ad partners list

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 for details.

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

Step 3: Import the Moloco SDK and adapter

Note: Failure to integrate the compatible Moloco and Google Mobile Ads SDK versions might lead to build issues.

Using CocoaPods (recommended)

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

  pod 'GoogleMobileAdsMediationMoloco'
  

• From the command line run:

  pod install --repo-update

Step 4: Implement privacy settings on Moloco SDK

EU consent and GDPR

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.

The Moloco SDK includes the hasUserConsent flag to pass consent information to the Moloco SDK.

The following sample code shows how to pass consent information to the Moloco SDK. If you choose to set these flags, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

Swift

import MolocoSDK
// ...

MolocoPrivacySettings.hasUserConsent = true;

Objective-C

#import <MolocoSDK/MolocoSDK-Swift.h>
// ...

[MolocoPrivacySettings setHasUserConsent:YES];

See Moloco's Privacy documentation for more information.

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.

The Moloco SDK includes the isDoNotSell flag to pass consent information to the Moloco SDK.

The following sample code shows how to pass consent information to the Moloco SDK. If you choose to set these flags, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

Swift

import MolocoSDK
// ...

MolocoPrivacySettings.isDoNotSell = true;

Objective-C

#import <MolocoSDK/MolocoSDK-Swift.h>
// ...

[MolocoPrivacySettings setIsDoNotSell:YES];

See Moloco's Privacy documentation for more information.

Step 5: Test your implementation

Enable test ads

Make sure you register your test device for Ad Manager.

Important: Disable test mode for Ad Manager and Moloco Ads SDK before releasing your app.

Verify test ads

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

Error codes

If the adapter fails to receive an ad from Moloco, you can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following classes:

MolocoSDK.MolocoError
GADMediationAdapterMoloco

Here are the codes and accompanying messages thrown by the Moloco adapter when an ad fails to load:

Error code	Domain	Reason
101	com.google.ads.mediation.moloco	Moloco SDK does not support serving ads on iOS 12 and below.
102	com.google.ads.mediation.moloco	Missing or invalid Moloco App Key.
103	com.google.ads.mediation.moloco	Missing or invalid Moloco Ad unit ID.
104	com.google.ads.mediation.moloco	Ad is not ready to be shown.
105	com.google.ads.mediation.moloco	Ad failed to show.
106	com.google.ads.mediation.moloco	Rendering data not available to render the ad.
-1 to 5000	Sent by Moloco SDK	Moloco SDK returned an error. See Moloco's documentation for more details.

Rewarded Server-side verification

If you Validate server-side verification (SSV) callbacks, the ad source identifier for Moloco is 8267622065755668722.

Moloco iOS Mediation Adapter Changelog

Version 3.12.1.0 (In progress)

Version 3.12.0.0

• Verified compatibility with Moloco SDK version 3.12.0.

Built and tested with:

• Google Mobile Ads SDK version 12.8.0.
• Moloco SDK version 3.12.0.

Version 3.11.0.0

• Verified compatibility with Moloco SDK version 3.11.0.

Built and tested with:

• Google Mobile Ads SDK version 12.6.0.
• Moloco SDK version 3.11.0.

Version 3.10.1.0

• Verified compatibility with Moloco SDK version 3.10.1.

Built and tested with:

• Google Mobile Ads SDK version 12.6.0.
• Moloco SDK version 3.10.1.

Version 3.10.0.0

• Verified compatibility with Moloco SDK version 3.10.0.

Built and tested with:

• Google Mobile Ads SDK version 12.5.0.
• Moloco SDK version 3.10.0.

Version 3.9.1.0

• Added watermark support for bidding ad formats.
• Fixed an issue when loading MREC banner ads.
• Verified compatibility with Moloco SDK version 3.9.1.

Built and tested with:

• Google Mobile Ads SDK version 12.3.0.
• Moloco SDK version 3.9.1.

Version 3.9.0.0

• Mediation platform name is now set when initializing the Moloco SDK.
• Verified compatibility with Moloco SDK version 3.9.0.

Built and tested with:

• Google Mobile Ads SDK version 12.3.0.
• Moloco SDK version 3.9.0.

Version 3.8.0.0

• Enabled -fobjc-arc and -fstack-protector-all flags.
• Fixed an issue with obtaining the star rating for native ads.
• Verified compatibility with Moloco SDK version 3.8.0.

Built and tested with:

• Google Mobile Ads SDK version 12.2.0.
• Moloco SDK version 3.8.0.

Version 3.7.2.0

• Verified compatibility with Moloco SDK version 3.7.2.
• Added bidding support for native ad format.

Built and tested with:

• Google Mobile Ads SDK version 12.1.0.
• Moloco SDK version 3.7.2.

Version 3.7.1.0

• Verified compatibility with Moloco SDK version 3.7.1.

Built and tested with:

• Google Mobile Ads SDK version 12.1.0.
• Moloco SDK version 3.7.1.

Version 3.7.0.0

• Verified compatibility with Moloco SDK version 3.7.0.

Built and tested with:

• Google Mobile Ads SDK version 12.0.0.
• Moloco SDK version 3.7.0.

Version 3.6.0.1

• Updated the adapter to retrieve the Moloco SDK version from the main thread.
• Now requires Google Mobile Ads SDK version 12.0.0 or higher.

Built and tested with:

• Google Mobile Ads SDK version 12.0.0.
• Moloco SDK version 3.6.0.

Version 3.6.0.0

• Verified compatibility with Moloco SDK version 3.6.0.

Built and tested with:

• Google Mobile Ads SDK version 11.13.0.
• Moloco SDK version 3.6.0.

Version 3.5.0.0

• Initial release.
• Added bidding support for banner (includes MREC), interstitial and rewarded ad formats.
• Verified compatibility with Moloco SDK version 3.5.0.

Built and tested with:

• Google Mobile Ads SDK version 11.13.0.
• Moloco SDK version 3.5.0.