Google in Display Setups

Owned by
Matan Nahum
Last updated: Apr 08, 2024
4 min read

Table of contents

  1. Google as a renderer - How Google ad sources are treated in Display compared to Video.

  2. Setup Google display demand in the Aniview platform: - How to include Google demand in Display Standalone and Multiformat setups.

Google as renderer

  1. In Display, Google is used both as a demand source and a renderer when it is included in the waterfall.

    1. *When it is not included in the waterfall, or an error prevents it from rendering, Aniview steps in as the renderer.

  2. How the process works: When Google is the renderer, it means that every impression is being run through Google before it reaches the ad placement, example of prebid+google auction cycle:

    1. Aniview calls the waterfall and receives google ad source + prebid ad sources.

    2. Aniview ad manager calls all the prebid ad sources on the client side.

    3. Aniview ad manager sends the winning prebid bid CPM as a key value in the Google ad request.

    4. Google runs an auction in GAM between all participating bidders, this may include ADX, prebid bid, OpenBidding, and any direct line items.

    5. The winning line item is selected and a creative is returned to the ad placement.

    6. Prebid impression is considered an Ad-Server impression while ADX impressions are considered As ADX impressions.

  3. Note: Considering the above, every non-ADX impression is charged with a fee (by GAM).

Setup Google display demand in the Aniview platform:

  1. Create Google ad unit in your GAM account.

  2. Create a Google ad source - You can choose one of two options:

    1. Platform Link source type setup (Display / Google) - This is the recommended setup.

      1. Note: To use this source type you must make sure that:

        1. You have a TPP API connection with the relevant GAM account.

        2. “Import & Sync GAM Entities” option is enabled in (Account Settings / TPP page).
          image-20240404-151811.png

        3. Your Google ad unit (in GAM) must have one ad size or more associated to it.

      2. Select the relevant “TPP Auth Credentials”.

      3. Select the right TPP Entity ID (represents the Google ad unit by name and ID).

      4. If required, select the relevant Child Network from the dropdown.

      5. If required, select the Google Third ID from the dropdown.

      6. TPP CPM sync is automatically used here.

      7. Full path and sizes are automatically imported for the selected ad unit.

      8. If required, Key/Values can be added at the bottom of the page.

    2. Google Tag source type setup (Display / Google):

      1. No API connection is required for this setup - the setup is done manually.

      2. You can choose wether to add TPP sync CPM data (recommended).

      3. Full path: Add the full path - You may add the full path for the ad unit, or the whole ad unit tag from google.

        1. Child Network and Google Third ID can be added manually in fullpath.

      4. Sizes - Select from dropdown the same sizes you have set up on your Google ad unit in GAM.

      5. If required, add key/values.

  3. Connect Google ad source to your display or multiformat channel:

    1. Google ad units must be associated to the relevant ad placement type they are going to appear in.

    2. In your display waterfall (Multiformat channel “Display” tab, or Display channel “Waterfall” tab) go to the “Google Ad Units” section to selected the ad sources per placement.

      image-20240404-155242.png

    3. The Google ad unit placement types are:

      1. Standalone - Used by the “Display Placement” studio entity.

      2. InRead - Used by the video player’s multiformat features as in the InRead position (specifically the preloader and passback features).

      3. Float - Used by the video player’s multiformat features as in the Float and Sticky positions (specifically the preroll and passback features).

      4. Overlay - Used by the Instream video player’s overlay feature in InRead Position.

      5. Overlay Float - Used by the Instream video player’s overlay feature in Float/Sticky Position.

    4. For the same channel, each Google ad unit associated (in each placement) must be different, to prevent rendering issues on the client side (Google prevents two renders of same ad unit in page).

      1. Not only the ad source must be different, also the associated Google ad unit must be different.

    5. “Delegate to Partner” - You can also choose to connect a partner connection instead of Google ad sources, in this scenario, your partner will have to set up their Google ad units in their channel.

      image-20240404-160048.png

  4. Google in Publisher Connections/Channels:

    1. Publisher connection needs to be associated to the publisher channel in the Google Ad Units section so Google demand will be recognized by the player (when associated to publisher channel).

    2. If you have created a publisher connection using the “Save + Channel” button, the publisher connection will be associated to publisher channel’s Google Ad Unit section as “Delegate to Partner” automatically.

    3. If you have created a publisher connection and attached an existing channel using the “Associate to existing publisher channel” option, the publisher connection will be associated to the publisher channel’s Google Ad Unit section as “Delegate to Partner” automatically.

  5. Multiformat setup next steps - can be found here: https://aniviewwiki.atlassian.net/wiki/spaces/HELP/pages/2474901512/Multiformat+Features?search_id=4efdf2d7-3711-4aee-86cf-4ca4ba4da62a

  6. Standalone display placement setup next steps - can be found here: https://aniviewwiki.atlassian.net/wiki/spaces/HELP/pages/2474934274/Set+Up+a+Display+Placement?search_id=585e920a-f04c-41a9-a7cd-07deb1933576