GPID and Ad Unit Mapping
Buyers recognise an ad slot across every network they buy it from by its Global Placement ID (GPID). Many buyers only bid, or bid higher, on slots they can identify. On MAX, BidMachine sends your MAX Ad Unit ID as the GPID by default. There is nothing to set up.
Mapping your MAX ad units to BidMachine placements is optional. It gives each ad unit its own placement in the BidMachine dashboard, where you can set your own GPID, for example one GPID shared by several ad units.
The whole mapping lives in the BidMachine dashboard and works on Android and iOS: one placement per MAX ad unit, with the ad unit's ID in the placement's MAX Ad Unit ID field. You do not need to touch your MAX ad unit settings, and ads keep serving while you do this.
Before you start
-
BidMachine is enabled on the ad unit in MAX with your Source ID (see Overview).
-
You know where to find the MAX Ad Unit ID: in MAX go to Manage → Ad Units. The Ad Unit ID column shows it for every ad unit (16 characters, for example
aaaa0000bbbb1111).
Which option: up to about ten ad units, do it by hand (Option A). More than that, upload the MAX export (Option B).
Option A: a few ad units, by hand
Repeat for each MAX ad unit.
-
In MAX, go to Manage → Ad Units and copy the Ad Unit ID of the ad unit.
-
In the BidMachine dashboard, open Source & Blocking Rules, open the source of the app, click Edit and go to the Placements tab.
-
Click Add Placement to create a placement for the ad unit, or edit the one you already use for it. One placement per MAX ad unit.
-
Fill in the form so that it describes the ad unit: Platform and Bundle of the app, Ad Type of the ad unit (banner and MREC are Banner).
Bundle formatAndroid: the package name, for example
com.example.mygame. iOS: the numeric App Store id, for example123456789. See Placements. -
Paste the MAX Ad Unit ID into the MAX Ad Unit ID field and click Save. Leave GPID empty unless you want to set your own. The placement is saved right away; you do not need to save the source form.
-
The placement appears in the list with its MAX Ad Unit ID. That is the whole mapping.
Option B: many ad units, upload the MAX export
-
In MAX, go to Mediation → CSV Tools → Ad Unit Manager and click Export Ad Unit Settings (AppLovin describes the tool on its Waterfall management tools page). Do not edit the file.
-
In the BidMachine dashboard, open any source, go to the Placements tab and click Import from MAX CSV. One upload covers all the sources of your account.
-
Choose the exported file and click Import.
-
Read the result: how many placements were created and updated, and which rows were skipped and why (see Skipped rows).
What happens to your file
- Only the BidMachine Bidding rows whose Source ID belongs to your account are read. Other networks and other accounts are ignored.
- Each ad unit becomes one placement, with the ad unit's ID in its MAX Ad Unit ID field. Placements you already have are updated, never deleted, and a GPID you set yourself is never overwritten.
- The dashboard offers your export back with the BidMachine placement id written into the Ad Unit ID / Placement ID cell of each BidMachine Bidding row. Uploading it back into MAX is optional: the mapping works without it.
- Uploading the same export again is safe. Nothing changes, and rows reported as already imported as placement … are normal, not errors.
Check it worked
- In the placements list every mapped placement shows its MAX Ad Unit ID.
- A new mapping is live within about a minute. Your account manager can confirm it from BidMachine reporting.
Set your own GPID
The GPID field of a mapped placement is optional. Leave it empty and the GPID stays the ad unit's MAX Ad Unit ID; fill it in to send your own value instead. To give several ad units one shared GPID, for example several MAX ad units that serve the same ad slot, enter the same value in each of their placements.
Skipped rows and what to do
| Reason shown | What to do |
|---|---|
| source '…' is not in this account | The Source ID in that ad unit's BidMachine settings is not one of yours. Check it in MAX. |
| ad type not recognised in ad unit name | BidMachine reads the ad type from the ad unit name. Include banner, MREC, interstitial, rewarded or native in the name, or create the placement by hand. |
| platform '…' is not android or ios | Only Android and iOS ad units are imported. |
| no bundle: add a placement or a default-domain bundle for … | Create one placement for that platform on the source by hand first, then upload again. |
| MAX Ad Unit ID already on placement … | Two ad units carry the same BidMachine placement id in MAX, the placement already belongs to another ad unit, or the ad unit is already on another placement. Fix the duplicate and upload again. |
| ad unit is paused or disabled in MAX | Paused and disabled ad units are not imported. Enable the ad unit in MAX and upload again. |
| expected 15 columns, got … | The row is damaged. Export the file from MAX again without editing it. |
Good to know
- The MAX Ad Unit ID must be exactly as MAX shows it.
- Give each MAX ad unit its own placement. A MAX Ad Unit ID can be on only one placement per source.
- In MAX, the BidMachine Placement ID field is optional. If you fill it in, enter the ad unit's BidMachine placement id, not your Source ID.