Delivering Ads in IMA 3

946 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
946
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Best place to start for basic or advanced setup is the documentationManygeneral HTML ad details as well as a page specific to IMA 3
  • May have noticed on top of each documentation page a big warningHTML5 ads disabled by default- didn’t want to cause issues with numbers if serving FLV ads. Also a lot of customers have wanted to test out their setup themselves before they turn on HTML5 adsPersonally I think you should just turn it on right awayOne-time action for each account.
  • Choose DFP IMA 3If you’ve already chosen DFP XML, DFP IMA 2, or DFP IMA 3 for Flash delivery, then you’re all setAs a side note, choosing VAST Server also works if you’re not using DFP
  • This is not something you should have to do for DFPGood to know about in any case as the alternative path for ad plugin setupSet up in the publishing module, as shownMake sure to remove any ad plugins added this way if you are using DFP
  • Need to have an ad tag URL, just like in the Flash setupShare the same field as is used for FlashWill will go more into setting up a video ad properly and the generation of this URL
  • I do want to talk a little bit more about what should be in the ad tag URLRemember that for the HTML player to work, the ad must be VAST compliant and use H264Testing with local ads doesn’t always work as you expect, given CORS. Also, if you’re using a local ad or know of the details of your ad in DFP, make sure it’s a VAST ad with H.265 videos. The latter often trips up people with old assets that are still using FLVs in places.
  • When you go back to the listing of players in the ad module, ignore the SWF mentioned on the right. This is the SWF location we use for the IMA 3 plugin in the Flash player, but rest assured we do still use a JavaScript plugin for the HTML player.
  • AddingforceHTML5=true and debug=true to any player URL really helps for simple testingTo be clear, the desktop browser is not the same as a mobile device. Each OS and version, even minor versions, has significant differences with HTML video. But in general you shouldn’t have to worry about that- we do this testing
  • Need to use same settings as used on the Flash side, although there is a way around this through APIs (as is discussed a little bit soon)Ignores onload ads for HTML. You can still have this set on the Flash side if you want, just ignored on the HTML side. Onload ads don’t work given restrictions on playing on iOS and the latest versions of AndroidIgnores changing of ad policy in lower-left corner- you can still set these for Flash though.
  • If you are using arules, the only thing that matters is that there’s a proper ad server URL and that prerolls are setEverything else is ignored, as DFP is really driving the ad policy here
  • We do have ad-specific smart player APIs, and these do all work with IMAAd start and complete are often used for analytic purposes or changing the display in a custom way when an ad is playingYou can use these on the page, in which case they are used for both the Flash and HTML player. Or you can use them in a JS plugin, in which case they are just used for the HTML playerIn general setAdPolicy() won’t work if you’re using ad rules, since DFP is setting the ad policy
  • As mentioned in the example, appending forceHTML=true and debug=true to the page is a great first step for debuggingLook in the IMA 3 guide for known limitationsAlso try the ad in Google’s Video Suite Inspector, first switching to the HTML Player (right below the video player) before doing so. If it doesn’t work there either, consider that it may be an issue with the ad or configIf you’re still seeing it as an issue, consider narrowing it down to a specific OS version to determine whether it is something that you are concerned about. Often issues are specific to one OS versionAnd as always, please contact our excellent CS department
  • (mention questions will be at the end)
  • Delivering Ads in IMA 3

    1. 1. BRIAN DEITTE, ARCHITECT AT BRIGHTCOVEWILL WEINGARTEN, PRODUCT MANAGER FOR DFP VIDEODelivering Ads with HTML5Players Using DFP IMA 3
    2. 2. AgendaBasic player setup — BrianAdvanced player setup — BrianConfiguring a video ad — WillIMA 3 features — WillQuestions
    3. 3. My backgroundArchitect and product ownerAdvertising focusPlayer partner liaison
    4. 4. Basic player setup for IMA 3
    5. 5. Start herehttp://support.brightcove.com/en/video-cloud/docs/delivering-advertising-html5
    6. 6. Enable HTML5 ads
    7. 7. Pick an ad source
    8. 8. Adding an ad plugin
    9. 9. Set an ad server URL
    10. 10. Set an ad server URL, continuedRemember CORSUse VAST ads with H.264 video
    11. 11. Ignore this detail
    12. 12. ExamplePlayer using IMA 3
    13. 13. Advanced player setup for IMA 3
    14. 14. Upgrading to IMA 3DFP IMA 2 to DFP IMA 3: usually easyDFP XML to DFP IMA 3: sometimes easyTest upgrade before rolling out to allAble to batch edit the policy updates
    15. 15. Regular ad policy settings
    16. 16. Ad policy settings for ad rules
    17. 17. Using smart player APIshttp://docs.brightcove.com/en/smart-player-api/reference/symbols/brightcove.api.modules.AdModule.html
    18. 18. TroubleshootingforceHTML=true and debug=true appended to the URLCheck the known limitationsTry the ad at https://developers.google.com/interactive-media-ads/docs/vastinspector_dualTry other devices and other OS versions to see how wide of anissue it isAs always, contact support
    19. 19. Thank youHTTP://TINY.CC/IMA3PLEASE TAKE A MOMENT TO COMPLETE A SESSION EVALUATION.YOUR FEEDBACK WILL HELP IMPROVE BRIGHTCOVE PLAY.

    ×