How does the auction process work, and what metrics does the platform use?
The number of valid Publisher Ad Opportunities.
Please note: Opportunities are environment specific. For example, if a Request is made to a tag where the Traffic Channel environment is set to Desktop, only Requests from Desktop will generate Opportunities. Requests to the same tag from Mobile devices will not generate Opportunities.
If an Opportunity is generated, then StreamRail ad manager starts generating an Ad Impression. During this process, the ad manager (depending on internal optimizations) is generating simultaneous Requests to all of the Ad Sources for the same tier, starting with tier 1.
One Opportunity can generate multiple Requests at once, depending on the amount of Ad Sources that fit the targeting conditions of this specific Opportunity (Device, GEO, Player Size, Whitelist, Blacklist etc).
Each request can convert to either a Bid or a Pre-Bid error.
A “Request” may resolve to a either a Bid or a Pre-bid error. Bids are counted when the ad server of the Ad Source replied with a non-empty VAST without errors.
Please note: certain timeouts are applied during the bidding process. Therefore, slow responding servers may fail to generate Bids.
If the ad server of the Ad Source replied with an empty VAST or did not reply on time (approx. 15 seconds).
After receiving enough Bids, the ad manager chooses the Ad Source most likely to generate an Impression. This Ad Source is loaded and started, which is counted as a “Win” (this Ad Source is the winner of the bidding process). If the winning Ad Source ended up yielding an Ad Impression, the entire flow is complete and the ad manager finishes its job. If the winning Ad Source resolved to a Post-bid error, the ad manager will assign a Win to the next best bidding Ad Source. This process repeats itself until the ad manager times out or is disposed by the player which loaded it.
The winning Ad Source yielded an Ad Impression (Ad Video actually started to play).
The winning Ad Source could not generate an Ad Impression. This is mostly because of the Demand behind the Ad Source, in which case the Post-Bid error is a VPAID error. However, in some cases this can also be a timeout error (the winning Ad Source tried to bring an ad unsuccessfully for too long, approx. 30 seconds), a technical integration error (for example, the Ad Source tag is the wrong type), or simply because of user actions (the user closed the page before the ad finished loading).
Additional metrics within the StreamRail funnel:
Inventory– this is the first phase of the StreamRail funnel. Inventory represents the initial call that our server receives from another server.
An Inventory will generate an Opportunity once there is at least 1 Ad Source that can receive this specific traffic (based on the Targeting conditions at each Ad Source level).
Player loads– relevant only for Player activity. The Player load represent the loading of the player itself within a specific Publisher. The Player loads will appear after an Inventory was generated.