Tag Archives: AdMob

AdMob’s new reporting delivers better insights

At AdMob, we’re focused on helping publishers make smarter decisions to grow their mobile app earnings and deliver the best experience to their users. Clear, comprehensive reporting is a big part of this, and we’ve recently released some updates to our reporting so that you can gain more actionable insights about your app users. 


More insights about how people use your app

We’ve enhanced our AdMob SDK to begin providing insights into how your users are interacting with your app and engaging with your rewarded ads.  To enable these new features, you need to do two things:


  1. Update your SDK to the latest version (Android SDK 18.1.0 or later, iOS SDK 7.44 or later)

  2. Log into AdMob and take a few simple steps to enable user metrics  (Help Center Article)

Once you’ve done both, available new features will include:

User engagement card

When you log into your AdMob account, we’ll now present you with important basic user engagement metrics on your App Overview dashboard.  This report helps you keep an eye on your app’s most important top-line user numbers so you always know how your apps are performing.

User engagement card

             Basic metrics in the user engagement card

Holistic revenue report including in-app purchases

We’ve updated our revenue reporting to look beyond AdMob earnings to also include in-app purchases and subscriptions. This will minimize time spent going back and forth between interfaces so you can spend more time working on your app. IAP reporting is currently only offered on iOS, but will be coming to Android soon.

Holistic revenue report

                             Holistic revenue report including in-app purchases

Rewarded ads report

You’ll now have access to the rewarded ads report, helping you understand how users are interacting with rewarded ads.  This report captures activity from the entire AdMob platform, including AdMob, Open Bidding, and 3rd-party inventory. We’re also working to provide additional reporting around each of your ad formats so you can make the most informed decision with your app business.

Rewarded ads report

                                                   Example rewarded ads report

Expanded functionality and ease of use

In addition to adding new reports, we’ve also launched several new features that make it easier for you to access, analyze and understand your data: 


AdMob API

Traditionally, developers have had to use the AdSense API to access AdMob stats.  This was a suboptimal solution, as AdSense uses different ad metric definitions than AdMob, resulting in inconsistent reporting.  To address this, we’re introducing a brand new AdMob API to help you retrieve your publisher reports programmatically. Metrics in the AdMob API will be consistent with those in the AdMob front-end interface and will be more accurate than those in the AdSense API.  This API is currently in beta, so reach out to your account manager or a mobile specialist if you’re interested in trying it out.


Easy comparison reporting

When looking at changes to a single AdMob metric, such as revenue, we know that context is key. So we’ve added the ability for you to compare two metrics within the same chart (see upper right in image below) so that you can more easily correlate trends within your data.


You can also now break out metrics, such as estimated earnings, by dimensions like app, ad unit, format, and country (see upper left in image below).  Our improved graph interactivity allows you to add or remove dimensions by simply clicking on the corresponding circle in the key, as shown below on the upper left.

Reporting improvements gif

                                          New comparison and usability chart features

Reporting is an integral part of optimizing any app ads business, and we’re continuously taking steps to make actionable insights easier to discover for publishers.  We hope these new features will help publishers better understand their users and ad performance so they can focus on driving more revenue and delighting their users.

Share your feedback about AdMob and Ad Manager mobile app integration

We’re continuously improving our guides, code samples, and other developer resources for the Google Mobile Ads SDK to help you integrate AdMob and Ad Manager into your mobile apps.

To learn more about what's working well and what could be improved, we're announcing our second annual developer feedback survey for the Google Mobile Ads SDK. We'd like to hear from you about where we should focus our efforts.

SHARE YOUR FEEDBACK

Your answers will be completely anonymous. The survey should take about 15 minutes to complete and will close on September 30, 2019.

Your feedback is truly important to us. Here are a few highlights of the changes we made based on feedback from last year’s survey:

  1. Continuous translations of the developer docs in several languages
  2. Continuous build integration of sample applications via Travis CI
  3. Launched a Developer tutorials playlist on the Google AdMob YouTube channel
  4. Launched the App Policy Center to help publishers handle policy violations

Please let us know what you’d like us to focus on next. Thank you in advance for helping us continue to improve the developer experience for everyone.

Simplifying our content policies for publishers

One of our top priorities is to sustain a healthy digital advertising ecosystem, one that works for everyone: users, advertisers and publishers. On a daily basis, teams of Google engineers, policy experts, and product managers combat and stop bad actors. Just last year, we removed 734,000 publishers and app developers from our ad network and ads from nearly 28 million pages that violated our publisher policies. 


But we’re not just stopping bad actors. Just as critical to our mission is the work we do every day to help good publishers in our network succeed. One consistent piece of feedback we’ve heard from our publishers is that they want us to further simplify our policies, across products, so they are easier to understand and follow. That’s why we'll be simplifying the way our content policies are presented to publishers, and standardizing content policies across our publisher products.

A simplified publisher experience

In September, we’ll update the way our publisher content policies are presented with a clear outline of the types of content where advertising is not allowed or will be restricted. 

Our Google Publisher Policies will outline the types of content that are not allowed to show ads through any of our publisher products. This includes policies against illegal content, dangerous or derogatory content, and sexually explicit content, among others. 

Our Google Publisher Restrictions will detail the types of content, such as alcohol or tobacco, that don’t violate policy, but that may not be appealing for all advertisers. Publishers will not receive a policy violation for trying to monetize this content, but only some advertisers and advertising products—the ones that choose this kind of content—will bid on it. As a result, Google Ads will not appear on this content and this content will receive less advertising than non-restricted content will.  


The Google Publisher Policies and Google Publisher Restrictions will apply to all publishers, regardless of the products they use—AdSense, AdMob or Ad Manager.


These changes are the next step in our ongoing efforts to make it easier for publishers to navigate our policies so their businesses can continue to thrive with the help of our publisher products.

Additional safeguards to protect the quality of our ad network

Supporting a healthy ads ecosystem that works for publishers, advertisers, and users continues to be a top priority in our effort to sustain a free and open web. As the ecosystem evolves, our ad systems and defenses must adapt as well. Today, we’d like to highlight some of our efforts to protect the quality of our ad network, and the benefits to our publishers and the advertising ecosystem. 

Last year, we introduced a site verification process in AdSense to provide additional safeguards before a publisher can serve ads. This feature allows us to provide more direct feedback to our publishers on the eligibility of their site, while allowing us to communicate issues sooner and lessen the likelihood of future violations. As an added benefit, confirming which websites a publisher intends to monetize allows us to reduce potential misuse of a publisher's ad code, such as when a bad actor tries to claim a website as their own, or when they use a legitimate publisher's ad code to serve ads on bad content in an attempt to demonetize the good website — each day, we now block more than 120 million ad requests with this feature. 

This year, we’re enhancing our defenses even more by improving the systems that identify potentially invalid traffic or high risk activities before ads are served. These defenses allow us to limit ad serving as needed to further protect our advertisers and users, while maximizing revenue opportunities for legitimate publishers. While most publishers will not notice any changes to their ad traffic, we are working on improving the experience for those that may be impacted, by providing more transparency around these actions. Publishers on AdSense and AdMob that are affected will soon be notified of these ad traffic restrictions directly in their Policy Center. This will allow them to understand why they may be experiencing reduced ad serving, and what steps they can take to resolve any issues and continue partnering with us.

We’re excited for what’s to come, and will continue to roll out improvements to these systems with all of our users in mind. Look out for future updates on our ongoing efforts to promote and sustain a healthy ads ecosystem.  

Five ways to make your app video-ad friendly

Video ads are one of the most effective ad formats to use in your app. Increasingly, people expect to see ads that are relevant to them and that don’t interrupt their app experience—and video ads deliver on both counts. They’re a powerful canvas that you can use to engage users, for you and your advertisers. With a variety of formats, such as rewarded, interstitial, or native video, you can integrate video ads into your app to provide an enhanced experience. 

But using video ads goes beyond selecting them as an option in Google AdMob. To make sure users have the best experience with video ads, you need to optimize your app to play them. If the video doesn’t play correctly, users often blame the app, not the ad. Playback needs to start promptly and reliably, and continue without interruption. But serving an ad in a mobile app is not always easy—a number of factors can degrade the experience. The network connection might be poor, or the phone itself might be busy with other things.

Video ads use more memory, network, and device resources than other types of ads. The key to optimal video quality is to use these resources as efficiently and as intelligently as you can. And when your video quality is better, your ads will perform better too, and you may find that your app becomes more stable overall.

Load ads well in advance to permit buffering

4v2.png

The moment you load a video ad, behind the scenes the ad starts buffering (essentially pre-loading) the video. In this instance, the network is the bottleneck. For example, if the phone is connected to WiFi or 4G, buffering should happen fast. But if the user is on a slower network, it can degrade or interrupt playback. The more time you allow for the ad to fill its buffer, the more reliable playback will be.

Seconds matter. Load your ad at least 15 seconds in advance of showing it. Even a few seconds in advance will prevent some users from seeing a blank ad.

Free unused ads

2v2.png

If you load an ad that you won't need, like a rewarded ad where the user declined the reward, then be sure to release it right away. This frees up memory and video decoders, which will help the phone run faster and reduce the possibility of interruption on your app. On Android, we recommend you null your reference to the ad, and if you're using native ads, call UnifiedNativeAd.destroy() on the main thread. On iOS, set your reference to nil.

Avoid loading multiple concurrent ads

app-ads.txt image 1 cropped

Every phone has a limit to the number of videos it can hold in a prepared state. The Google Mobile Ads SDK doesn't know which video ad will be shown next, so it keeps them all prepared. Lots of phones can't hold more than one prepared video at a time. So whether your app is used in developing or developed markets, it’s very important to always free up memory as soon as possible.

Load only the ads that you need to give them the best chance at successful playback. For example, if you show multiple video ads, like native video ads in a news feed, then be sure to recycle ads that have scrolled offscreen so video players don't just pile up in memory. This should also lead to better overall app performance.

Don’t show an ad before receiving a notification that it has loaded

5v2.png

The Google Mobile Ads SDK uses notifications to inform the app when a video is prepared to play. On Android, it is possible to show an ad before this notification--a legacy from the days of static content ads--but it's not a good idea to do that. Video performance will be poor and users may think something is wrong not just with playback, but with the app itself.

On Android, this notification arrives through AdListener.onAdLoaded().

Be extra cautious combining video ads with video content

3v2.png

The recommended approach of not loading multiple concurrent video ads applies equally to content video and ad video. If your app plays video outside of ads, then freeing content video resources before video ads are shown will help reliability, too.

As developers, you put a huge amount of time and energy into creating an engaging app. And a great app experience should provide a great ad experience. We hope these tips help you make the most out of video ads as part of your monetization strategy.

Growing in-app viewability coverage with Open Measurement

People are spending more time on their mobile phones, especially in apps, and move across screens frequently. As people’s usage of mobile apps has grown, so has the importance of standardizing the way viewability is measured on mobile devices.

Today we’re sharing how we’ve made in-app inventory more measurable through the IAB Tech Lab’s Open Measurement standard. Integrating the Open Measurement Software Development Kit (SDK) into both our Google Mobile Ads (GMA) and Interactive Mobile Ads (IMA) SDKs has allowed us to enable Open Measurement on 85+ percent of in-app display and video impressions on Google AdMob and Google Ad Manager publishers. This means that buyers of this inventory can now take viewability measurements using solutions like Integral Ad Science, DoubleVerify, Comscore, and Moat in addition to measurement that was previously available with Active View.  

“IAB Tech Lab’s Open Measurement (OM) initiative makes it easier for ad buyers and sellers to work together for viewability measurement and other verification needs,” said Dennis Buchheim, Executive Vice President and General Manager, IAB Tech Lab. “The sell-side has been adopting OM quickly, and we ask brands, agencies, and Demand Side Platforms (DSPs) to get more active and take advantage of what OM offers.” 

Advertisers can get started today by appending Open Measurement enabled tags from their viewability vendor of choice to their creatives.

Measurement vendors are lauding this development as progress for a more measurable future. Joseph Ranzenbach, Director of Product Management, IAS says, "Google's adoption of the Open Measurement SDK is a huge step in moving the industry forward and creating more transparency for advertisers." Sumit Shukla, SVP, Strategic Partnerships, Comscore says, "It’s important for Brands to consistently measure viewability across the entirety of their media buys. With Comscore’s cross-platform campaign measurement as a trusted market currency, this close partnership with Google further helps Brands measure what matters."  

Viewability measurement unlocks high-performing In-app inventory for advertisers

Viewability continues to be an integral part of measuring ad effectiveness—it helps advertisers understand if their ad had the opportunity to be seen and it helps publishers offer more high-quality inventory.

In-app viewability means that advertisers can confidently take advantage of this high-value inventory. In 2018 we worked with Ipsos MORI to understand the impact of in-app advertising and found it was successful in driving action. People were 50 percent more likely to interact with a brand, buy a product or service, follow a call-to-action or recommend a brand to their family or friends after seeing its ad in an app, compared with those who saw it via a browser. Display & Video 360 customers can now confidently extend their brand campaigns to apps knowing they are able to measure ad viewability at the impression level as they would in other environments.

Publishers like Pandora recognize the importance of holistic viewability measurement. Maria Breza, VP, Ad Quality Measurement and Audience Data Operations at Pandora said, “Advertisers should be able to seamlessly use one viewability provider to measure their buys across all publishers and platforms. Open Measurement has allowed Pandora to make this a reality for our clients with less latency, less maintenance and more stability.”

What’s next for Open Measurement

We’re continuing to work with the IAB’s Tech Lab Open Measurement Working Group to expand Open Measurement to use cases beyond viewability, as well as to other environments such as web video. We believe Open Measurement has the potential to create a more transparent and accountable digital media ecosystem across all screens. Reach out to your measurement partners and Google representative to find out how you can take advantage of this new measurement technology.



Source: Google Ads


Support for app-ads.txt to protect your app revenue and brand

To help build a safe and transparent advertising ecosystem, we’re introducing support for app-ads.txt across Google AdMob and Google Ad Manager. This will help app publishers prevent their inventory from being spoofed by bad actors while ensuring advertiser spend reaches the intended audience. 

What is app-ads.txt?

App-ads.txt is a standard released by the IAB Tech Lab that helps prevent unauthorized or domain-spoofed app inventory from being transacted across mobile, connected TV, and other devices. It defines a simple method for app publishers to publicly declare who is authorized to sell or resell their digital advertising inventory. App-ads.txt is an extension of the original ads.txt standard that was first published by the IAB in 2017. The ads.txt standard is one of the most successful industry standards and is now widely adopted by web publishers. 

Google’s support for IAB Tech Lab’s app-ads.txt

We’ve actively contributed to the specification of app-ads.txt since the beginning and will support the standard across all relevant products including AdMob and Ad Manager. Starting August 27, 2019, we will begin to block ad serving of unauthorized app inventory in both AdMob and Ad Manager as identified by a publisher’s app-ads.txt file. 

We strongly encourage you to create an app-ads.txt file and publish it to the developer domain you have listed in your App Store and/or Google Play store listing. This will help prevent unauthorized and domain-spoofed app inventory from damaging your brand and revenue.  Publishers who do not implement an app-ads.txt file will see no changes to their ad serving, but they will not benefit from these added spoofing protections.

How to prepare for the enforcement  

Correct implementation of app-ads.txt will help protect your inventory against bad actors. Implementation errors could cause interruptions to ad serving, so it is very important for you to verify that the app-ads.txt file you publish on your developer domain contains all your valid property codes before August 27. 

To prepare for the upcoming enforcement rollout, simply follow the steps below. You can find more details in our Help Center guides (AdMob, Ad Manager). 

  1. Provide a developer website URL in app store listings on Google Play or the App Store
  2. Publish an app-ads.txt file in the root directory of your site (e.g. example.com/app-ads.txt)
  3. Include all authorized publisher codes for the networks your app sells through in the file

Once you finish implementing the app-ads.txt file, we encourage you to carefully review it to ensure that it contains lines in the following format: 

google.com, pub-0000000000000000, DIRECT

As the sample line shows, your app-ads.txt file should include the name of the ad network you are working with (e.g. ‘google.com’) as the domain name and you should replace the publisher ID with your property code. 

To help you verify correct file implementation, we are currently rolling out verifications and warnings in the user interface for both AdMob and Ad Manager when errors are detected. The warnings will appear if we detect your publisher ID is missing from your app-ads.txt file.

app-ads.txt Alerts Mock in Ad Manager

Example of error notifications in Ad Manager

Example of error notification in AdMob

Example of error notifications in AdMob

There will be no interruption to your ad serving should you choose not to implement the app-ads.txt file on your developer website, but your app may be at risk of inventory spoofing which could result in revenue loss. 

By supporting the new app-ads.txt standard, AdMob and Ad Manager will help you better protect your revenue and brand. 

New innovations to grow your app business with ads

App developers around the world are pushing the limits of innovation to meet consumers' high expectations. In an increasingly competitive global market, it’s more important than ever for app developers to find better ways to build and grow their businesses.

Today at Think Games at ChinaJoy, we are sharing innovations that help you find more users and grow your revenue with Google’s latest solutions.

Reach more users when they’re looking for something new 

Connecting with the right people at the right time is key to building a strong user base. Google App campaigns make it easy for you to find app-happy users across Google Search, Play, YouTube and over 3 million sites and apps in our network. Here are some new ways App campaigns can help you expand your global reach.

Discover (formerly known as the Google feed) helps over 800 million monthly active users uncover fresh and interesting content related to the things they care about—like global news and topics of interest like sports, music, and mobile games. Now, you can access Discover inventory through App campaigns to make a strong impression on more users with relevant and visually engaging ads.

Headspace

               Ad for the Headspace app in Discover


App campaigns running in the United States will now automatically reach more potential users on Discover who are open to exploring your app. And in the coming months, your app ads on Discover will also serve in Malaysia, South Africa, India, Pakistan, Canada, Brazil, Japan and Indonesia. We aim to bring app ads in Discover to all available markets before the end of this year. 

In addition to Discover⁠, we’re introducing new reach opportunities on two more platforms:

  • App ads on YouTube Search: Your app promotion ads are now eligible to show in the top slot of YouTube’s mobile search results. Combining YouTube’s global audience with rich intent signals helps you deliver relevant and useful ads to more prospective app users.

App ad for Tap Titans

           App ad for Tap Titans 2 in YouTube Search


  • In-stream video ads in our display network: Display in-stream video ads are skippable video ads that play before, during, or after a video a user is watching. Starting next month, you can reach more people with your ads while they're viewing video content on mobile apps and sites in our network.

Grow revenue and deliver a better user experience

Finding the right users is important, but developers need to think about growing overall revenue in order to build sustainable businesses. By integrating ads during natural break points in your app you can build a new revenue stream and deliver a better user experience.

Our new app open ad format allows you to show ads to your users as they wait for your app to load. Designed to seamlessly integrate with your app’s branding, this format gives you new ways to earn revenue while creating a good user experience. Reach out to your account manager to get started with this format in alpha.  

In addition to the new app open ads, here are two more ways we are helping you grow revenue while delivering better ad experiences for your users:


  • Smart segmentation is now available for rewarded ad units. This feature, announced earlier this year for interstitial ads units, only shows ads to users unlikely to make purchases in your app. This protects the user experience of your purchasers while growing your ads revenue.

  • AdMob Insights: Our new Insights feature provides alerts to your AdMob dashboard when our system detects abnormal changes to your key metrics like eCPM, impressions and revenue. This new beta lets you know instantly if changes in your app are impacting user experience.

To learn more about how our new solutions can help you connect with the right users and scale your business, join our livestream at 1:40 pm SST during the Think Games event at ChinaJoy in Shanghai, China on August 1st, 2019. 

Source: Google Ads


Design the ideal ad experience with native ads from Google AdMob

Native is the newest ad format supported by Google AdMob. It offers the most flexible design and placement to help developers create the ideal ad experience for your app users. Today native ads have come out of beta and are now available for all developers. 

As the name suggests, native ads allow you to design an ad experience that feels like a natural part of your app. You can customize the look and feel of native ads the way you’d design your app content.

Publishers who have implemented native ads during the beta phase have seen great results. For example, Cleveni, a South Korea-based mobile app publisher specializing in utility apps, saw 4 times revenue growth with native ads. 

With careful design, implementation and testing, native ads can feel like a natural part of the app experience. This seamless integration can lead to revenue growth by means of increased ad density and better user retention while also clearly noting that it’s a promotional unit.

Native ads allow unlimited flexibility—you can design any ad layout imaginable as long as it meets the AdMob native ads policies. We highly encourage you to explore the design freedom with this ad format and use A/B tests with different creatives to maximize engagement and revenue. 

Getting started

There are two ways to get started with native ads in AdMob: 

  1. For a quick and easy start, use the native ads templates (Android, iOS). Simply use the code as-is, or modify it to better match the look and feel of your app. 
  2. For more advanced users,  you can go straight to the native ads advanced section (Android, iOS). This option allows you to create native ads from scratch.

With the flexibility of native ads also comes many questions you need to think through. For example, what should my ad look like? How similar should it look to actual app content? Where should I place it? The AdMob native ads playbook provides best practices and examples to help you design and implement a successful native ads strategy. 

As with all advertising experiences, there are some important policies and guidelines put in place to help ensure a good experience for users. Please be sure to read through the AdMob native ads policy compliance checklist, and pay close attention to the restrictions around ad size and the usage of MediaView.

We hope native ads can help you unlock more revenue growth for your app and will continue to improve this new ad format. 

Google Mobile Ads SDK for Android: How to migrate to v18.0.0

Earlier this week, Google Play services released a major update to many of its libraries to migrate all Android support library dependencies to Jetpack (using androidx.* packages). This includes the play-services-ads library from the Google Mobile Ads SDK, which has been updated to 18.0.0.

While the Google Mobile Ads SDK itself hasn’t changed between version 17.2.1 and 18.0.0, you’ll need to migrate your own app and all of your dependencies to AndroidX in order to pick up play-services-ads 18.0.0 or any future versions. This is particularly important if you use AdMob mediation, as several mediation partners have dependencies on Android support libraries that aren’t compatible with AndroidX.

To make the migration process as smooth as possible for you, Android Studio offers an easy way to convert your project and its dependencies to AndroidX using the Migrate to AndroidX option.

Migrate to AndroidX

Android Studio 3.2 or higher includes a Refactor > Migrate to AndroidX menu option to convert your project to use AndroidX. We’ll demonstrate what happens when converting our BannerExample to AndroidX.

  1. Change the project’s compileSdkVersion to 28. This is a prerequisite for migrating to AndroidX.
  2. Right click the app module, and select Refactor > Migrate to AndroidX. You’ll be given an option to save your project as a zip file before Android Studio converts it.
  3. Select Do Refactor to complete the migration.

What changed?

Here is the project before the migration:

And here is the project afterwards:

First, you’ll notice that the package name for AppCompatActivity has changed to androidx.appcompat.app. The refactor has changed this project’s com.android.support:appcompat-v7:26.1.0 dependency to androidx.appcompat:appcompat:1.0.0 and fixed the associated imports.

Second, this migration added a gradle.properties file with these two lines:

android.useAndroidX=true
android.enableJetifier=true

These properties ensure your project and its dependencies use AndroidX, by rewriting any binaries that are using an Android support library. See Using AndroidX for more details on these flags.

Now that your project is converted to AndroidX, you can safely update your play-services-ads dependency to 18.0.0 in your project-level build.gradle file:

dependencies {
implementation 'androidx.appcompat:appcompat:1.0.0'
implementation 'com.google.android.gms:play-services-ads:18.0.0'
}

As always, you can follow the release notes to learn what’s changed in the Google Mobile Ads SDK. We’d also love to hear about how your migration went! If you have any questions about the release or have trouble migrating, please reach out to us on the Google Mobile Ads SDK developer forum.