1 / 10

inAPP Ad Enabler Training

inAPP Ad Enabler Training. July 2, 2013. Ad Enablers – An Introduction. Overview Common API for mobile rich media ads to run in mobile apps There are numerous Enabler SDKs – many of which are now supported by MediaMind

kibo-hicks
Download Presentation

inAPP Ad Enabler Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. inAPP Ad Enabler Training July 2, 2013

  2. Ad Enablers – An Introduction Overview • Common API for mobile rich media ads to run in mobile apps • There are numerous Enabler SDKs – many of which are now supported by MediaMind • Enabler APIs generally support ad interactions such as expand, collapse, click-through and video • Use of Enablers will prevent creatives from having their code re-written and updated every time it needs to run within a different app Enablers to Review: • MRAID 1.0 • DFP Premium (Based on MRAID 1.0 with slight adjustments) • mOcean (Based on MRAID 1.0 with slight adjustments) • ORMMA (released by R&D team… picked up by Custom Dev)

  3. inAPP Support for MRAID 1.0inAPP Support for DFP Premium Overview: • Provide inAPP support for MM Expandable & Banner ads running in an MRAID 1.0 or DFP Premium environment • DFP Premium supports MRAID 1.0 for iOS & Android 4.0+ • Functionality supported includes expand, collapse, click-through • Released Sept 2, 2012 within MediaMind Platform Test Apps: • MRAID: CNN (iPhone/iPad), inMobi (Android, iPhone), Sound Hound (Android, iPhone) • DFP: DFP test app (iPhone, Android), Major Issues resolved prior to release: • Click-throughs not showing up in reports • Support for MRAID close button/hotspot (Template updates) • Interactions sent multiple times • Final queued up interactions not being sent out • Custom click-throughs not working New EB Command Module • EBCMD module setup for inclusion in creative (see slide)

  4. inAPP Support for mOcean SDK Overview: • Provide inAPP support for MM Expandable & Banner ads running in an mOcean environment • App provided by mOcean allows different ad ids to be entered for testing • Functionality supported includes expand, collapse, click-through Issues resolved this sprint: • Determined that mOcean expandable ads could not be set up as MRAID placements even though mOcean was based on MRAID • mOcean had positioning issues different than MRAID that needed to be addressed

  5. Expandable Format (Support EBCMD Module) Overview • Expandable format maintained on the Custom Development portal • Portal includes workspace, demo link and documentation • Updated to include EB Command Module • EB Command module handles events sent to creative for expanding or collapsing the ad (as seen with MRAID inAPP Expandable ads) • Updated workspace should be used for all expandable ads going forward Demo Link

  6. ORMMA Support Key Highlights: • Trained by R&D with ORMMA support in Nov. 2011 • Review of functions overridden in ORMMA.js • Building and testing of ORMMA workspace ads within the ORMMA testing site on Safari Browsers • Not provided with ORMMA test apps, but have trouble-shooted ORMMA test apps in the past year

  7. Setting up Enablers in Platform Overview: • Download the appropriate creative from Quickbase • For expandables, modify the creative to either use a custom close button or the default MRAID/DFP close button (with MRAID/mOcean, default close button can be hidden, but not for DFP) • MRAID Default button will be hidden but may be shown with the following creative code: • additionalConfig = { • useCustomClose: false • }; • Put ad in mobile placement and select appropriate application (see image)

  8. Known Issues / Open Issues MRAID • After doing a click-through, the landing page is often loaded inside the banner ad (in addition to opening a click-through window) • As seen in GreyStripeiOS App • Problem tracked down to an R&D change with the function EB._openWindowIfNeeded() … consulting with R&D on the next steps • Click-throughs are being counted as interactions • As seen in Rhythm New Media iOS app (Still waiting on app to perform our own testing… have made changes & re-tested with Certification)

  9. Coding Topics to Review • ORMMA • ORMMAReady() • adConfig.openWindow = false • openPage() • expand() • collapse() • MRAID (default close button or custom close button) • useCustomClose • mraidExpand • iframeCCRef._sendMessage("collapseAd", {}); • DFP (not support android under 4) • override showOnlyImage for android devices • mOcean (positioning issue fix using bocAlign) • use boxAlign style on body tag • EBCMD module • Known Issues • MRAID click-through is not tracked correctly • Click-through is open in both App and placement

  10. Case Study Expand half way Fix expansion Banner • Tips • use Fiddler to redirect the resource files for the debugging • always check to see if ormma, mraid is available • alert() and log may not available in App, create a div for the debug output instead • remove App to clean up the cache in App • video support is not available for current enabler

More Related