Ad unit mapping for SDK Bidding

Ad unit mapping provides a way for publishers to connect a Google Ad Manager Ad unit to the ad network required parameters for a specific ad format (for example, Banner or Native).

You can have a maximum of 250 ad unit mappings per app, and 1000 network wide. Learn the best practices for ad unit mapping and discover available partners.

Add an ad unit mapping

You can add one ad unit mapping at a time or bulk upload mappings.

1. Sign in to Google Ad Manager.
2. Click Delivery, then Bidders, and then Go to SDK Bidding.
3. Select the name of your Bidder.
4. Click Ad unit mapping, then New Ad unit mapping.

Select the ad unit

5. Select the type of Ad unit: "Run of network" or "Specific Ad unit".
6. Select the "Format".
   Note: If you're configuring ad unit mapping for a rewarded interstitial ad, choose the "Rewarded" format and use the rewarded interstitial placement ID.
7. Select "Mobile application" name.

Choose the mapped inventory

8. Select the corresponding "Partner inventory".
9. If you've connected to an available Bidder's API with the "API login" button, additional parameters will automatically populate. Otherwise, click Manual entry to enter those parameters.
10. Click Save.

Review a Bidder's existing ad unit mappings

1. Click Delivery, then Bidders.
2. Click Go to SDK Bidding, and select the name of your Bidder.
3. Click Ad unit mapping.
4. Click Download to download a CSV file with all existing ad unit mappings for this Bidder.

Bulk upload Ad unit mappings

Upload multiple Ad unit mappings using a CSV.

1. Click Delivery, then Bidders.
2. Click Go to SDK Bidding, and select the name of your Bidder.
3. Click Ad unit mapping.
4. Click Upload.
5. Click Download sample CSV file to download a file that you can use to define your ad units. Open the CSV file and make changes based on the example to include your ad units and parameters. When you're done, save the CSV file using your file editor.
6. Upload the edited Ad unit mapping CSV.
7. Click Confirm.

Best practices

The following recommendations will help you plan your ad unit mapping:

• To ensure you don't exceed the maximum of 250 ad unit mappings per app or 1000 network wide ad unit mappings, create only top level ad units.
• We recommend coverage of all ad units, available formats, and inventory so that bidders can access that inventory.
• Map specific ad unit IDs rather than "run of network" in order to map specific inventory with matching formats and inventory types.

Expand all Collapse all

How to use the sample CSV file

The sample CSV file contains fields and examples relevant to your account.

• Don't remove columns or change the column order. Doing so results in a failed upload
• Delete header rows from bulk upload sample CSV prior to upload. If you don't delete header rows, the upload will likely fail
• Remove semicolon (;) from your file editor's list of delimiter or separator characters to ensure the sample file renders columns and values correctly

Claim your apps in the app store

• To use ad unit mapping, claim your mobile app in Ad Manager.
• If you re-release an app to the app store, it may be given a new ID. Claim your re-released app.

Ad unit mapping fields

These fields are required to support ad unit mapping.

Field	Example	Description
Ad unit mapping ID	123456789	ID associated with an ad unit. Required when uploading CSV files to edit existing Ad unit mappings. Leave this blank when creating new mappings.
Ad unit path	top-level/parent1/child1	Full path for ad units, unique within a hierarchy level. The path should separate directories with a /.
Format	Banner	Available Formats include "Banner", "Interstitial", "In-stream Video", "Native", and "Rewarded".
Inventory type	Mobile	Inventory type identifies the kind inventory or the context in which ad creatives serve. Values you can select include: Mobile and Video.
Mobile application ID	987654321	ID associated with your mobile application.
Parameters	Key: Value	Third-party inventory identifiers for SDK Bidders. It is possible to have one or more parameters.

 

Available partners

Ad unit mapping is available for third-party bidders with custom SDKs. It is not available to ad exchanges.

AppLovin

AppLovin is available for ad unit mapping.

Field	Example	Description
Parameters	SDK Keys: 987612xxxxx_6789	Third-party inventory identifiers for SDK Bidders. It is possible to have one or more of these columns.

InMobi

InMobi is available for ad unit mapping.

Liftoff

Liftoff is available for ad unit mapping.

Meta Audience Network

Meta Audience Network (FAN) is available for ad unit mapping.

Field	Example	Description
Parameters	Placement ID: 12345xxxxxxx_xx321	Third-party inventory identifiers for SDK Bidders. It is possible to have one or more of these columns. Placement ID is the Meta SDK's identifier for your Ad unit.

Connect to FAN API ^(Optional) 

For Meta ad units only, you can connect to the FAN API to allow ad unit data to be shared with Google Ad Manager.

1. Before you choose your mapped inventory, click API Login to authorize Google Ad Manager to manage your Meta business and allow data about your placements to be shared.
2. Once authorized, you will return to Google Ad Manager and the ad unit mapping will indicate API Connected.

Meta best practice

All app banner ad sizes should map to the Meta placement format of "Banner".

Mintegral

Mintegral is available for ad unit mapping.

Pangle

Pangle is available for ad unit mapping.