+ All Categories
Home > Documents > inAPP Ad Enabler Training

inAPP Ad Enabler Training

Date post: 31-Dec-2015
Category:
Upload: kibo-hicks
View: 40 times
Download: 0 times
Share this document with a friend
Description:
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 - PowerPoint PPT Presentation
Popular Tags:
10
© 2011 MediaMind | A Division of DG | All rights reserved July 2, 2013 inAPP Ad Enabler Training
Transcript
Page 1: inAPP  Ad Enabler Training

© 2011 MediaMind | A Division of DG | All rights reserved

July 2, 2013

inAPP Ad Enabler Training

Page 2: inAPP  Ad Enabler Training

© 2011 MediaMind | A Division of DG | All rights reserved

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)

Page 3: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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)

Page 4: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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

Page 5: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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

Page 6: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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

Page 7: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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)

Page 8: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

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)1. As seen in GreyStripe iOS App2. 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

1. As seen in Rhythm New Media iOS app (Still waiting on app to perform our own testing… have made changes & re-tested with Certification)

Page 9: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

ORMMAORMMAReady()adConfig.openWindow = falseopenPage()expand()collapse()

MRAID (default close button or custom close button)useCustomClosemraidExpandiframeCCRef._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

Coding Topics to Review

Page 10: inAPP  Ad Enabler Training

© 2011 MediaMind | A division of DG | All rights reserved

Banner Expand half way Fix expansion

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

Case Study


Recommended