GAM connection

Last edited: 2024/11/07

Yieldbird Platform requires API connection with your Google Ad Manager account to properly service all modules. The connection is using a dedicated GAM user: service account that you must setup during the implementation process.

The connection is established automatically when Yieldbird is creating a workspace and adding your GAM network code to it.

Main purposes for GAM API connection

The purposes of using the GAM API depend on the modules you are using:

General:

• reporting for settlements
• creating key values

Prebid Stack:

• reporting
• creating key values / advertiser/ orders / line items / creatives (learn more)

Price Genius:

• reporting & AI data modelling
• automatic price updates

Refresher:

• reporting
• targeting line item names or types

Viewability Tools

• reporting & AI data modelling

Unfilled Recovery

• not used

Connection status

Connection status can be checked in Global setup > GAM connection. However, if the connection is not working properly you will also see an alert icon next to the name of your workspace and GAM id:

The status of GAM connection is updated automatically every day around midnight CEST.

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> Troubleshooting failed GAM connection:

If you can see that the GAM connection rendered an error, check the error reason provided in the Error box; these are the error reasons provided directly by GAM API, to decipher them please refer to GAM API documentation (link).

The most common reason for a GAM connection malfunction is insufficient permissions granted to Yieldbird’s service account when providing access to your GAM (error reason: PERMISSION_DENIED). In such cases, please make sure that all the required permissions are granted in your GAM.

For other reasons please refer to GAM API documentation on API errors, and if you are not sure what to do, please reach out to your Customer Success Manager directly.

</aside>

Key values

This panel allows you to manage which key values are automatically created and, if necessary, updated in the connected GAM account.

Each key value can have one of the following statuses:

• Created: The key value has been properly added to GAM and has all necessary values.
• Not created: The key value is not added to GAM and its values are not being updated. May also indicate that there was a problem when trying to add the key value or update its values.

To change the status of the key values go to actions and choose the action you want:

• Activate (available only when status is Inactive)
  1. Creates the key value in GAM and assigns values.
  2. Adds the key value to the key value check queue.
• Update values (available when status is Active OR Requires attention)
  1. Updates the assigned values for the key value.
• Deactivate (available when status is Active OR Requires attention, not available for key value yb_platform)
  1. Removes the key value from GAM.
  2. Removes the key value from the key value check queue.

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> key value check queue is the automated process executed everyday at midnight (CEST) when Yieldbird Platform checks if the given key value:

• is created in GAM
• has all the values assigned </aside>

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> For more information about the key values used by Yieldbird Platform: key values dictionary

</aside>

Setup Prebid Stack in GAM

Prebid Stack requires implementation in Google Ad Manager (GAM). This includes creating Delivery items: Advertiser, Orders, Line Items, and Creatives in your GAM. These must be set up separately for:

• Banner & Outstream Video
• Instream Video
• Native

Alternatively, you can enable Header Bidding Trafficking (requires GAM 360 & supports only selected Bidders).

On this page:

To learn more about how this work, please read the following article.