Google Ad Manager (GAM) Orders

Owned by Oleg
Last updated: Sept 02, 2020
2 min read

In August 2020 the new tool "GAM Orders" has been introduced.
There are several features that may significantly help or simplify setup.

  1. Publisher may pre-create GAM Order to use it as a Draft for further Site creation (GAM integration manual)

  2. Publisher may pre-create GAM Order to use it as the Linked Order for further Site creation (GAM integration API)

  3. When Publisher creates GAM Order API-based he should use pre-created GAM Link and should not enter authentication parameters anymore.

  4. There are two types of GAM Order API-based integrations available. First - legacy one, when Publisher points several ad units from GAM Account exactly! Second - the new one, the RON option. Publisher attaches the whole GAM account and may use any ad unit further.

Why use the RON (Run Of Network) setup.

  1. Publisher will have only one Order for all sites in the GAM account

  2. Proper Line Item will be found by a proper set of key/values

  3. GAM (Google Ad Manager) allows using a multi-level ad unit hierarchy. So, using RON, Publisher may create a 1st level Ad Unit that represents "Site" and then, creates child ad units under it. Those child ad units will be used for prebid setup (just use them when creating ad placements) and, at the same time, they allow to get reporting with proper granularity, site by site reports.

Two main points here.

  1. There is the selector “RON“. When false, a Publisher may choose ad units that must be included in the Order (See option “GAM Units“). This is a dynamic option, HBM retrieve the full ad unit list via API link.

  2. When “RON“ = true, a Publisher can’t select ad units. They must be added manually on the next step, creation of the HBM “Site“ entity.

RON Orders might be re-used multiple times for multiple sites within a single GAM account

Manual Order might be used only once.