This article explains how you can import data from a .CSV file to create and update ad unit mappings and ad source instances in mediation groups. You can also use export to create a .CSV file to review the data, troubleshoot any issues, and then import updates to your mediation setup.
In addition, this article provides a breakdown of the structure of your .CSV file and provides a table to help you correctly map your data to app and ad unit configurations during import.
On this page
- Before you get started importing your ad unit mappings and mediation groups
- Export a CSV file of your ad unit mappings and mediation groups
- Import a CSV file of your ad unit mappings and mediation groups
- Understand the columns in your CSV file
- Third-party ad source names, app, and ad unit credentials
Before you get started importing your ad unit mappings and mediation groups
Importing a .CSV file allows you to efficiently create and update ad unit mappings and ad source instances. Before you get started, we recommend you follow these best practices:
- Start by exporting a .CSV file to understand the file format, and all of the ad unit mappings and mediation groups in your app. Once you’ve familiarized yourself with the .CSV file, you can start to edit and add ad unit mappings and line items.
- Work with a single app at a time to avoid making bulk changes across multiple apps.
- Create ad units and mediation groups in advance. Importing a .CSV file does not create ad units or mediation groups. First, you’ll need to create them in AdMob and then copy those IDs into your .CSV file to use them for new mappings and ad source instances.
- Set up your waterfall and bidding ad sources beforehand. You’ll need to set up ad sources in AdMob, before you can import a .CSV file of the mappings for those ad sources. Once you’ve set up the ad source, you can use the table below to know what mapping details to use in which columns (App Config 1, App Config 2, Ad Unit Config 1, Ad Unit Config 2).
Export a CSV file of your ad unit mappings and mediation groups
You can export a .CSV file to download mapping and ad source details. Use export to create a .CSV file to review the data, troubleshoot any issues, and then import updates to your mediation setup. You can choose to download mappings for a specific app or all the apps in your account.
To export a .CSV file:
- Sign in to your AdMob account at https://admob.google.com.
- Click Mediation in the sidebar.
- Click Export to CSV.
- Check the checkbox next to the apps you want to include in the .CSV file download. You can use the Search box to find a specific app.
- Click Confirm.
- Save the .CSV file to your device.
The downloaded .CSV file includes your selected ad unit mappings, third-party network ad unit identifiers, AdMob ad unit details, and the list of the mediation groups where the mappings are being used. For more information about the different columns in a .CSV file and what they mean, refer to the table below.
Import a CSV file of your ad unit mappings and mediation groups
You can import a .CSV file to create and update ad unit mappings and add ad source instances to mediation groups.
To import a .CSV file:
- Sign in to your AdMob account at https://admob.google.com.
- Click Mediation in the sidebar.
- Click Import CSV.
Note: The upload limit is 1000 rows - Select the .CSV file you want to import from your device.
- Click Next to generate a preview.
- Review the updates you want to make to your mediation setup, click Apply changes.
Each row in the generated preview corresponds to a row in your file and shows its change status:
- No change: This means the ad unit mapping already exists in your account, and it’s usage in mediation groups also has no change.
- Update: This means the ad unit mapping already exists, but updates have been made to the fields in the ad unit mapping (name, IDs, eCPM, etc.) or to the list of mediation groups where the mapping is used.
- Create: This means a new ad unit mapping will be created and ad source instances will be added to the specified mediation groups.
- Error: This means something is wrong with the row you are attempting to import. Review the error details to resolve the issue.
-
Click Yes, apply changes to confirm your updates.
Changes you make via upload will modify serving behavior if you’re making updates to mediation groups. -
A message indicates the import was successfully applied. Click Done.
Understand the columns in your CSV file
The table below details the columns and their meanings within the .CSV file.
Note: Column names include their corresponding field types:
- Read only - informational field included in the download
- Optional - this field can be included when creating or updating ad unit mappings in the upload
- Required - required field for importing in order to create or upload ad unit mappings
| Column Name | Description |
|---|---|
| Mapping ID (optional) | Unique ID to identify an existing ad unit mapping.
Required when importing .CSV files to update existing ad unit mappings. Leave this blank to create new ad unit mappings. |
| Mapping name (optional) |
A unique name for the ad unit mapping in AdMob. Optional use to differentiate between ad unit mappings. Note: For custom events, the Mapping name is required and will be used as the custom event label. |
| Ad source name (required) | The name of the third-party ad source.
Note that this value cannot be updated for an existing ad unit mapping. Note: This field is required. Refer to the "Ad Source Name" column in the mapping details table below. |
| Ad unit ID (required) |
A unique ID number assigned to each of your ad units when they're created in AdMob.
Note: This value cannot be updated for an existing ad unit mapping. Note: This field only supports standard AdMob ad units. |
| Ad unit name (read-only) | Unique name for the AdMob ad unit. This name is provided in the download for informational purposes. |
| Format (read-only) | The ad format assigned to the AdMob ad unit. This detail is provided in the download for informational purposes. |
| Platform (read-only) | The device platform of your app (Android or iOS)
This detail is provided in the download for informational purposes. |
| App config 1 (required) | These app config IDs come from a third-party ad source. Each third-party ad source uses different names for their fields.
When importing, you need to identify what config value you’re required to use for an ad source and which column you need to add that value into the file. Refer to the "App Config 1" and "App Config 2" columns in the mapping details table below to determine what config value to use for which column. |
| App config 2 (required) | |
| Ad unit config 1 (required) | These ad unit config IDs come from a third-party ad source. Third-party ad sources use different names for their fields.
When importing, you need to identify what config value you’re required to use for an ad source and which column you need to add that value into the file. Refer to the "Ad Unit Config 1" and "Ad Unit Config" 2 columns in the mapping details table below to determine what config values to use for which columns. |
| Ad unit config 2 (required) | |
| Network / (Order by) eCPM (optional) | Reference eCPM floor for ad unit mappings
Note: This value is required for waterfall ad unit mappings when you want to add them as line items in a mediation group |
| Mediation group IDs (optional) | Unique ID number assigned to each of your mediation groups in AdMob. Multiple mediation group IDs display in a comma-separated list. |
| Mediation group names (read-only) | Comma-separated list of mediation group names for informational purposes. The mediation group names display in order of mediation group IDs. |
Third-party ad source names, app, and ad unit credentials
To import your .CSV file, consult the table below to determine the appropriate app and ad unit configuration values for each relevant column.
Example of .CSV file import using the table
To illustrate the process, let's walk through an example of integrating LINEAds Network waterfall line items:
- In the "Ad source name" column, enter 'LINEAdsNetwork_Waterfall'.
- In the "App config 1" column, enter your LINEAds Application ID.
- In the "Ad unit config 1" column, enter your LINEAds Slot ID.
| Ad Source | Ad Source Name | App Config 1 | App Config 2 | Ad Unit Config 1 | Ad Unit Config 2 |
|---|---|---|---|---|---|
| AdMob Network | AdMobNetworkWaterfall_Waterfall | Ad Unit ID | |||
| Applovin | Applovin_Bidding | SDK Key | |||
| Applovin_Waterfall | SDK Key | Application ID (Android) / Bundle ID (iOS) | Zone ID | ||
| Chartboost | Chartboost_Waterfall | App ID | App Signature | Ad Location | |
| Custom Event | CustomEvent_Waterfall | Class name | Parameter | ||
| DT Exchange | DTExchange_Waterfall | Application ID | Placement ID | ||
| i-mobile | i-mobile_Waterfall | Publisher ID | Media ID | Spot ID | |
| InMobi |
InMobi(SDK)_Bidding |
Account ID |
Placement ID |
||
| InMobi_Waterfall | Account ID | Placement ID | |||
| ironSource Ads | ironSourceAds_Waterfall | App Key | Instance ID | ||
| ironSourceAds_Bidding | App Key | Instance ID | |||
| Liftoff Monetize | LiftoffMonetize_Bidding | Application ID | Placement Reference ID | ||
| LiftoffMonetize_Waterfall | Application ID | Placement Reference ID (Vungle SDK version 5.0.0 or greater) | |||
| LINEAds Network | LINEAdsNetwork_Waterfall | Application ID | Slot ID | ||
| maio | maio_Waterfall | Media ID (メディアID) | Zone ID (ゾーンID) | ||
| Meta Audience Network | MetaAudienceNetwork_Bidding | Placement ID | |||
| Mintegral | Mintegral_Bidding | App Key | App ID | Placement ID | Ad Unit ID |
| Mintegral_Waterfall | App Key | App ID | Placement ID | Ad Unit ID | |
| myTarget | myTarget_Waterfall | Slot ID | |||
| Pangle | Pangle_Bidding | App ID | Ad Placement ID | ||
| Pangle_Waterfall | App ID | Ad Placement ID | |||
|
Tapjoy |
Tapjoy_Bidding |
SDK Key |
Placement Name |
||
| UnityAds | UnityAds_Waterfall | Game ID | Placement ID | ||
| UnityAds_Bidding | Game ID | Placement ID | |||
| Vpon | Vpon_Waterfall | Vpon Ad ID | Zone | ||
| Zucks | Zucks_Waterfall | Frame ID |