This event is raised when ads are successfully loaded from the Google or DoubleClick ad
servers through an AdsLoader. You can register for this event on AdsLoader.
After ads are loaded from the Google or DoubleClick ad servers, the publisher needs
to play these ads either in their own video player or in the Google-provided video
player.
After ads are loaded from the Google or DoubleClick ad servers, the publisher needs to
play these ads either in their own video player or in the Google-provided video
player. This method returns an AdsManager object. The AdsManager supports playing ads
and allows the publisher to subscribe to various events during ad playback.
Parameters
contentPlayback: object
Player that plays back publisher's content. This must be an object that
contains the property currentTime, which allows the SDK to query
playhead position to properly display midrolls in case ad server responds with
an ad rule. The HMTL5 video element fulfills these requirements. You may
optionally implement your own playhead tracker, as long as it fulfills the above
requirements.
During ads load request it is possible to provide an object that is available once the
ads load is complete. One possible use case: relate ads response to a specific request
and use user request content object as a key for identifying the response.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-17 UTC."],[],[]]