Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.




1Video SDK /Player/SSAI initiates request for ads with Ad Pod details
2Server side wrapper interprets this request to AdPod optimisation / Selection Engine 
3Selection engine looks at available ads (if already present in cache / collection store) if it doesn't have all ads as per rules, sends altered request to Requester
4Bid details with ad exclusion and other rules are sent to Prebid server Bidder adapters module
5The bid responses are added to ad collection and Selection Engine reevaluates if it has all ads based on rules
6Post Timeout or fulfilment fullfilment of ads per rule all relevant ads is pushed to  collector/cache
7All selected / relevant ads are sent to ad pod generator - which generates VAST XML
8This VAST may be hosted in cache - bases on use case / settings
9Ad Pod details and price is communicated back to Client
10Client select best ads from direct / programmatic to serve 
11Player gets the ad during break and tries to render all ads in a pod.


PubMatic's implementation adds the AdPod extension the AdPod extension object as a child the BidRequest object the BidRequest object and/or the Video the Video object. When you use and AdPod and AdPod object as a child of BidRequestof BidRequest, then the AdPodthe AdPod's settings are global in scope. When AdPod When AdPod is a child of Videoof Video, the AdPodthe AdPod's settings are local scope for the Video the Video object and its parent Impression. When both BidRequest and Video parent Impression. When both BidRequest and Video each have an AdPod an AdPod object, then the Impressionthe Impression. Video.Ext.AdPod settings override BidRequest's global settings. And while BidRequest and Video can override the BidRequest global settings. And while BidRequest and Video can each use most of AdPodof AdPod's parameters, there are a few that apply only to BidRequest as shown in the table below.