Important! Before reading this article you must be familiar with our ad serving logic. For further details, please see Introduction to our Player ad serving logic.
What does the Ad Prioritization Logic Layer Do?
The Ad Priority and optimization Logic layer is responsible for deciding which Ad campaigns, will be sent out, and in what order, to Ad servers.
Note: This process only applies to outgoing ad requests and does not affect the ad playback order in the player. The ad playback order in the player is controlled by an additional logic layer that deals with the ad response timing. For further details, please see Ad response timing logic.
Ad Prioritization Overview
The following diagram and explanations describe how the system prioritizes which Ad campaigns are triggered to request an ad response.
Important! The following diagram might be overwhelming at first site. Please read the explanations beneath the diagram to understand each part of the process.
Note: The following explanation will describe the prioritization logic for Stages I and II. Stage III is explained in separate articles for each of the optional scenarios. Follow the explanations to understand each flow.
As mentioned before in the introduction article, the Ad set object is responsible for linking Ad campaigns to the player. Because all the Ad campaigns in the Ad set have no hierarchy or order, the system needs to prioritize them to optimize the player's performance when requesting ads.
In the first stage, the system filters out any non relevant Ad campaigns using an Ad campaign validation process. This process checks the following requirements to eliminate any old or non relevant Ad campaigns that might exist in your Ad set.
The Ad campaign validation process will not take into account any Ad campaign if one the following validation terms is fulfilled:
- Ad campaign not enabled - Meaning the Ad campaign 'Enabled' field is not selected.
- Ad campaign not active - Meaning the Ad campaign is either before the defined 'Start date' or After the defined 'End date'.
- Incompatible Media Type - The Player is requesting a non supported Media type - Meaning that the player is located in a Desktop environment and is requesting a Mobile ad or vice versa.
Note: Media type field
- Geo Targeting Block - The 'Geo target' field definition in the Ad campaign is preventing the ad from being run in that location - Meaning that the accessing IP address of the player is not white listed.
Note: Geo targeting
The remaining list of Ad campaigns that comply with these validation terms will move on to the next stage.
The second stage will determine what type or types of Ad campaigns are included in the assigned Ad set/s. One of two possible scenarios can occur:
- Direct Only or Direct & Network Ad campaigns - The common denominator of both the titles in this scenario is the existence of at least one Direct Ad campaign in the attached Ad set/s.
- Network campaigns only - The scenario addresses the situation where only Network Ad campaigns are assigned to the Ad set/s (No Direct Ad campaigns at all).
Note: The outcome of the second stage affects what prioritization process is applied to the Ad campaigns.
The third stage is divided into the two articles, one for each of the possible outcome scenario of stage II. Please click on the required link below to learn about each process in more detail:
- Direct only or Direct & Network ad campaign prioritization.
- Network only ad campaign prioritization.
To learn more, please refer to the following articles:
- What are VAST and VPAID?
- What is a VPAID Shim?
- Introduction to our Player ad serving logic.
- Ad response timing logic.