Integrate BidMachine with Mediation

Select platform: Android Android iOS Unity Flutter

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

Supported integrations and ad formats

The mediation adapter for BidMachine has the following capabilities:

¹ Waterfall integration is in closed beta, reach out to your account manager to request access.

Requirements

• Android API level 23 or higher

• [For bidding]: To integrate all supported ad formats in bidding, use BidMachine adapter 3.4.0.1 or higher (latest version recommended).

• Latest Google Mobile Ads SDK

• Complete the mediation Get started guide

Step 1: Set up configurations in BidMachine UI

Log in to your BidMachine account dashboard.

Create new placements

Navigate to the Source tab and under the Sources table, select the Edit button.

You will be shown a list of all the placements you have. To create a new placement, click the Add Placement button on the dialog.

Fill out the form and click Save.

Finally, take note of the Placement ID.

Update your app-ads.txt

Authorized Sellers for Apps app-ads.txt 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.

To implement app-ads.txt for BidMachine, navigate to the app-ads.txt tab from the Dashboard. Then, copy the list and append it to your website's app-ads.txt file.

Step 2: Set up BidMachine demand in Ad Manager UI

Sign in to your Ad Manager account.

Add BidMachine in Companies

Enable secure signal sharing

Share secure signal on bid requests

Allow secure signal sharing for SDK Bidding

Configure BidMachine bidding

Configure ad unit mapping

Add BidMachine to GDPR and US state regulations ad partners list

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

Step 3: Import the BidMachine SDK and adapter

Android Studio integration (recommended)

In your app-level gradle file, add the following implementation dependencies:

dependencies {
    implementation("com.google.android.gms:play-services-ads:25.3.0")
    implementation("com.google.ads.mediation:bidmachine:3.7.0.0")
}

dependencies {
    implementation 'com.google.android.gms:play-services-ads:25.3.0'
    implementation 'com.google.ads.mediation:bidmachine:3.7.0.0'
}

Step 4: Implement privacy settings on BidMachine 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.

BidMachine automatically reads GDPR consent set by consent management platforms including the UMP SDK. For more information, see GDPR.

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.

BidMachine automatically reads GPP consent set by consent management platforms including the UMP SDK. For more information, see GPP.

Step 5: Add required code

No additional code needed for BidMachine integration.

Step 6: Test your implementation

Enable test ads

Make sure you register your test device for Ad Manager.

Follow the instructions in BidMachine's documentation for Android in order to enable test mode for BidMachine.

Verify test ads

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

Optional Steps

Native ads

Ad rendering

The BidMachine adapter returns its native ads as NativeAd objects. It populates the following fields for a NativeAd.

Error codes

If the adapter fails to receive an ad from BidMachine, you can check the underlying error from the ad response using ResponseInfo.getAdapterResponses() under the following classes:

io.bidmachine
com.google.ads.mediation.bidmachine

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

BidMachine Android Mediation Adapter Changelog

Next Version

• Maps AgeRestrictedTreatment to BidMachine's COPPA API.

Version 3.7.0.0

• Verified compatibility with BidMachine SDK version 3.7.0.

Built and tested with:

• Google Mobile Ads SDK version 25.1.0.
• Google Mobile Ads Next-Gen SDK version 1.1.0.
• BidMachine SDK version 3.7.0.

Version 3.6.1.0

• Added property to build the adapter with GMA Next-Gen SDK dependency.
• Verified compatibility with BidMachine SDK version 3.6.1.

Built and tested with:

• Google Mobile Ads SDK version 25.1.0.
• BidMachine SDK version 3.6.1.

Version 3.5.1.2

• Updated BidMachine Adapter to use AdPlacementConfig.

Built and tested with:

• Google Mobile Ads SDK version 24.9.0.
• BidMachine SDK version 3.5.1.

Version 3.5.1.1

• Added support for forwarding the tagForUnderAgeOfConsent Google Mobile Ads SDK parameter to the BidMachine SDK.

Built and tested with:

• Google Mobile Ads SDK version 24.9.0.
• BidMachine SDK version 3.5.1.

Version 3.5.1.0

• Verified compatibility with BidMachine SDK version 3.5.1.

Built and tested with:

• Google Mobile Ads SDK version 24.9.0.
• BidMachine SDK version 3.5.1.

Version 3.5.0.0

• Verified compatibility with BidMachine SDK version 3.5.0.

Built and tested with:

• Google Mobile Ads SDK version 24.7.0.
• BidMachine SDK version 3.5.0.

Version 3.4.0.1

• Removed class-level references to Context objects to help with memory leak issues.
• Updated adapter to support banner ad requests that are close in size to its supported formats, instead of requiring an exact size match.

Built and tested with:

• Google Mobile Ads SDK version 24.7.0.
• BidMachine SDK version 3.4.0

Version 3.4.0.0

• Added waterfall support for banner, interstitial, rewarded and native ad formats.
• Adapter now forwards onAdOpened() with onAdImpression() for full-screen ads.
• Verified compatibility with BidMachine SDK version 3.4.0.

Built and tested with:

• Google Mobile Ads SDK version 24.6.0.
• BidMachine SDK version 3.4.0.

Version 3.3.0.0

• Initial release.

Built and tested with:

• Google Mobile Ads SDK version 24.5.0.
• BidMachine SDK version 3.3.0.