Labels:

MacOS High Sierra includes a new version of Safari, Safari 11. This new version by default will remove support for auto-playing videos unless they are muted. If your desktop site currently autoplays unmuted video with the IMA SDK, your users will see the first frame of the ad, but the ad will not play. To resolve this, you can either change your implementation to click-to-play, or attempt to autoplay and revert to click-to-play if that fails. We've also added a new error that will fire if the SDK is asked to autoplay an ad but is prevented from doing so by the browser. Continue reading for more info on these solutions.

Click-to-play

The simple, advanced, and playlist IMA SDK samples use this click-to-play functionality. In short, you add a play button to your UI, and render that play button on page load. Your code should then delay calls to adDisplayContainer.initialize(), adsManager.init() and adsManager.start() until the user clicks that play button.

Attempt to autoplay

We've added a new sample to our GitHub repo, Attempt to Autoplay. This sample will autoplay ads if allowed, and if not, will follow the above click-to-play workflow. The sample starts by attempting to autoplay the content video. If autoplay succeeds, it pauses the content to play a pre-roll. This happens in an instant, so the users will not see any content actually play before the ads. If this autoplay attempt fails, the sample renders a play button and waits for the user to click that button to initialize the ad display container and play ads.

New error for failed autoplay

We've added AdError.ErrorCode.AUTOPLAY_DISALLOWED which the SDK will fire if it is asked to autoplay an ad but is prevented from doing so by the browser. You should not see this error if you've properly implemented one of the solutions above. This error is wrapped in a VIDEO_PLAY_ERROR; you can look for it as follows: 

onAdError(adErrorEvent) {
  if (adErrorEvent.getError().getInnerError().getErrorCode() ==
      google.ima.AdError.ErrorCode.AUTOPLAY_DISALLOWED) {
    // The browser prevented the SDK from autoplaying an ad.
  }
}



If you have any questions, feel free to reach out to us on our support forum.


 - 
MacOS High Sierra
includes a new version of Safari, Safari 11. This new version by default will
remove support for auto-playing videos unless they are muted. If your desktop
site currently autoplays unmuted video with the IMA SDK, your users will see the
first frame of the ad, but the ad will not play. To resolve this, you can either
change your implementation to click-to-play, or attempt to autoplay and revert
to click-to-play if that fails. We've also added a new error that will fire if
the SDK is asked to autoplay an ad but is prevented from doing so by the
browser. Continue reading for more info on these solutions.



Click-to-play



The simple, advanced, and playlist IMA SDK
samples use this click-to-play functionality.
In short, you add a play button to your UI, and render that play button on page
load. Your code should then delay calls to adDisplayContainer.initialize(),
adsManager.init()
and adsManager.start()
until the user clicks that play button.


Attempt to autoplay



We've added a new sample to our GitHub repo, Attempt
to Autoplay. This sample will autoplay ads if allowed, and if not, will
follow the above click-to-play workflow. The sample starts by attempting to
autoplay the content video. If autoplay succeeds, it pauses the content to play
a pre-roll. This happens in an instant, so the users will not see any content
actually play before the ads. If this autoplay attempt fails, the sample renders
a play button and waits for the user to click that button to initialize the ad
display container and play ads.



New error for failed autoplay



We've added AdError.ErrorCode.AUTOPLAY_DISALLOWED which the SDK
will fire if it is asked to autoplay an ad but is prevented from doing so by the
browser. You should not see this error if you've properly implemented one of the
solutions above. This error is wrapped in a VIDEO_PLAY_ERROR; you can look for
it as follows:





onAdError(adErrorEvent) {
  if (adErrorEvent.getError().getInnerError().getErrorCode() ==
      google.ima.AdError.ErrorCode.AUTOPLAY_DISALLOWED) {
    // The browser prevented the SDK from autoplaying an ad.
  }
}




If you have any questions, feel free to reach out to us on our support forum.



 - , IMA SDK Team

Labels: ,

Labels: , ,

Labels: , , , ,


 - , Ad Exchange Team
Labels: , ,

Labels: , , , ,

  • New fields in various report types.
  • The TABLE_EXTENSION enum value for ClickType was renamed to PRICE_EXTENSION.
  • See the full AdWords API release notes for more details.
The major changes in v201710 are:
  • The Automated field was added to the AD_PERFORMANCE_REPORT.
  • The EnhancedCpvEnabled field was removed from all reports.
  • See the full AdWords API release notes for more details.
In addition to these changes, v201705 is now the default version for reports. You can use one of the newly supported versions instead by specifying the apiVersion in your report request:
var report = AdWordsApp.report(query, {
    apiVersion: 'v201710'
});

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
- Mike Cloonan, AdWords API Team.
Labels: , , ,

Labels: ,

Labels: ,

Labels: , ,

Labels: ,

Labels: ,

Implementation Guides

We've also updated our publisher guides with Kotlin snippets wherever code is shown. Similar to the mobile ads guides for iOS (which show either Swift or Objective-C syntax with a click of a tab), the Android guides now let developers easily switch back and forth between Java and Kotlin implementations.

Questions?

If you take a look at the Kotlin guides and samples and find you've got questions about the best way to implement something in Android's first ever new language, stop by our support forum. Our staff there will be happy to help.

 - , Mobile Ads Developer Relations
Labels: , , , , , ,

Current Ad Exchange Seller REST API users will need to migrate to the DoubleClick for Publishers API before July 26, 2018. This migration guide provides a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.
For general assistance with the DFP API or your migration, reach out on our developer forum.

Why this is happening


As a part of our effort to provide a unified tool to manage your ad business and monetize your inventory, the DoubleClick for Publishers API now supports all of the features of the Ad Exchange Seller REST API. The DFP API is more robust and has more frequent updates.

What isn't changing


Users will not need to create new accounts. All Ad Exchange Seller users already have a DoubleClick for Publishers account.

No data is changing. The only change is how you programmatically access that data.

 - , DFP API Team
Labels: , , ,

Example of ad appearing outside of "safe area" on iPhone X

With the launch of the iPhone X, app developers now need to plan for new design considerations as the rounded corners, notch, and home screen indicator on the extended screen can obscure content and lead to poor ad experiences for users when ads are placed in these areas.

That's why we've put together a guide to help you adapt your ad strategy for iPhone X. This includes guidance for how you can shift placement of banner or native ads to designated "safe areas" for this new device.

We've also updated our policies to indicate that ads must not be placed where objects may interfere with the user's typical interaction with the ad or app, such as under the home screen indicator on the iPhone X.

Please review these policy updates and our suggested implementation guide to ensure you're compliant by November 20th.

If you have any questions, visit the AdMob Help Center or contact your Google account team.

Posted by Pablo Alvarez, Product Manager, AdMob

Labels: , ,

Labels: , ,

Labels: , ,

Labels: , , , , ,

 - , DFP API Team
Labels:

When using autolayout, ensure any constraints are relative to safe area layout guides. If you're using manual layout, check that banners and native ads fit within the safeAreaInsets.

For interstitials and rewarded video ads, we're working to ensure all controls and important content are also placed within the safe area. Keep an eye out for another Google Mobile Ads SDK release ahead of the iPhone X release date.

If you have any questions about iOS 11 support in the Google Mobile Ads SDK, please drop us a line at the developer forum.

 - , Mobile Ads Developer Relations

Labels: , ,

Labels:

Labels: , ,

Labels:

Labels: , ,

Labels: , ,

Labels:

Labels: , ,

Labels: