Tag Archives: AdSense

Check out the latest workshop content!

We’ve completed the last round of the AdWords API Workshops, and you can check out all the content online by visiting the official website, www.adwordsapiworkshops.com, and clicking on Resources.

Be sure to also check out our YouTube channel for the recorded presentations.

If you have any questions about the AdWords API Workshops, you can post them on our forums. Check out our Google+ page for Ads APIs updates.

The time is now for multi-screen


We live in an exciting time, where the number and variety of connected devices are growing at a rapid pace. People are coming online for the first time, and they’re accessing the Web through a mobile device.

Having a solid multi-screen strategy will help you prepare for the next wave of mobile web users. By following the simple steps below, we can help set you up for success on mobile web and answer questions like: How will my users react?, how do I keep my brand identity?, and what will happen to my earnings?

1. Test your site 
Start by understanding how your site currently runs on mobile devices. Use Google PageSpeed Insights to see how your site is performing on mobile and identify your site’s most crucial needs and what to take care of first.



2. Pick your strategy
Next, it’s time to make a choice on which multi-screen strategy to move forward with. The most common solutions are:


The choice is yours and all strategies have both pros and cons. When making the decision, you should consider the following:

  • Do I want to serve the same content to all platforms? If so, a responsive design should do the trick.
  • What’s more important; speed or flexibility? A separate mobile site or dynamic serving allows for better optimization.
  • Do I have the resources to maintain more than one site? Responsive design can help you save valuable time and resources.
  • What kind of technical capabilities do I have? Pick a strategy that best suits your skill set.

3. Follow best practices
We’ve finally made it to the fun part – building the site. No matter what solution you choose, every multi-screen developer should follow these general rules of thumb.

  • Focus on the main action that you want the user to take: While you had plenty of space on desktop, you’ll have to be resourceful on mobile.
  • Make your navigation easy to understand: Users want quick access to key actions, so make things easy to find.
  • Use existing design paradigms: Do you already have a brand identity on your desktop site? Reuse the same design elements when possible. Try adapting to the user’s device, for example using Material Design for Android: users like familiarity.
  • Make sure videos work: Design your look and feel and page animations using modern web technologies. Read more about Look and Feel for video in our Web Fundamentals guide.
  • Limit image-based text: Make use of web fonts when possible. Mobile means lower bandwidth.
  • Simplify payment processes: Auto-populate shipping addresses and contact details. Use existing payment solutions such as Google Wallet.


4. Avoid common mistakes
Learn from other developers by checking out some of the most common mistakes on mobile sites. This can save you time as you plan and launch your multi-screen strategy.

We hope these guidelines are useful when thinking about your multi-screen strategy. Let us know if you have any other tips that have worked well for you in the comments below.

Not yet an AdSense user? Sign up now!





Posted by Felix Nermark
Marketing Communication Specialist

Source: Inside AdSense


Engage your mobile audience with these best practices

74% of people say that when a site is mobile-friendly, they're more likely to return to that site in the future, according to a Think With Google study.

If that's not enough to encourage you to build up your mobile audience, consider this: 52% of users in the same study said that a bad mobile experience made them less likely to engage with a company.

Designing a mobile-friendly site is important, and so is creating the best mobile user experience. That includes ads: if you want to make the most of every opportunity to earn, your ads should be designed for mobile, too.

Download The AdSense Guide to Mobile Web Success to learn practical ways to engage and delight your mobile audience. Get tips on how to:
  • Potentially boost mobile ad revenue with the best ad placements
  • Choose the right mobile ad formats for your site
  • Send push notifications to your audience just like an installed native app
  • Help your audience jump back into your content with just a single tap
What’s your favorite way to engage your mobile audience?  We’d love to hear from you in the comments or on Twitter.

Not yet an AdSense user? Sign up today!



Posted by Jay Castro
Audience Development Specialist
@jayciro


Source: Inside AdSense


DoubleClick Ad Exchange Seller REST API Report changes

On November 17th, 2015, we'll be updating the Ad Exchange Seller REST API to make it consistent with the user interface. Specifically, we'll remove the ability to download saved reports or retrieve the dimensions we retired in April.

Requests made after this date for these dimensions will result in that dimension being ignored and requests for saved reports will result in an error.

As a reminder, the dimensions we retired in April are:

  • AD_FORMAT_CODE
  • AD_UNIT_ID
  • AD_UNIT_CODE
  • DSP_ID
  • EXPANSION_TYPE_CODE
  • PLATFORM_TYPE_CODE

For a full list of available dimensions, please see the AdX Seller REST API documentation.

Follow our Google+ page for other announcements and updates.

-- Dean Lukies, Ads Developer Relations

Multiple scenes and ads in Unity

When developing with AdMob in Unity, it is a common practice to make your banner ads persist across multiple scenes. This blog post will highlight best practices to accomplish this with the Google Mobile Ads Unity Plugin.

The most straightforward approach is to link the lifecycle of ads to that of the scenes they’re displayed in. When transitioning from one scene to another, existing ads are destroyed before leaving the first scene. New ads can then be created and displayed in the next scene.

The downside of this approach is that every scene transition would result in a new banner request. This may not be desirable if scene transitions are frequent and occur quickly.

An alternative is to use a GameObject as a wrapper for banners or interstitials. By default, each GameObject in a scene will be destroyed once the new scene is loaded (unless you use additive scene loading). However, you can make a GameObject survive across scenes by marking it with DontDestroyOnLoad. You can then use the GameObject.Find method to obtain references to the wrapper GameObject from scripts in other scenes.

Here is an example of how to use a GameObject to wrap banner ads:


// FirstSceneScript.cs
void Start() {
// Create a wrapper GameObject to hold the banner.
GameObject myGameObject = new GameObject("myBannerAdObject");
myGameObject.AddComponent<BannerWrapper>();
// Mark the GameObject not to be destroyed when new scenes load.
DontDestroyOnLoad(myGameObject);
}
The BannerWrapper GameObject is a wrapper for a BannerView.

// BannerWrapper.cs
using System;

using UnityEngine;
using GoogleMobileAds;
using GoogleMobileAds.Api;

public class BannerWrapper : MonoBehaviour {

public BannerView bannerView;

void Start()
{
bannerView = new BannerView(
"your_ad_unit_id", AdSize.SmartBanner, AdPosition.Bottom);
AdRequest request = new AdRequest.Builder().Build();
bannerView.LoadAd (request);

bannerView.Show();
}
}

In SecondSceneScript.cs, which is attached to the second scene, you can find a GameObject by name, get the BannerWrapper component, and access the BannerView:


// SecondSceneScript.cs
void Start () {
GameObject myGameObject = GameObject.Find("myBannerAdObject");
BannerWrapper bannerWrapper = myGameObject.GetComponent();
bannerWrapper.bannerView.Hide();
}

By managing your ads efficiently and seamlessly across scenes, you are sure to provide a better ad experience for your users. If you have any questions about Unity integration, you can reach us on our forum. You can also find our quick-start guide linked here. Remember that you can also find us on Google+, where we have updates on all of our Google Ads developer products.

Turn your passion into profit with AdSense

Today, we’re excited to announce our new AdSense website* with a fresh design and new publisher stories. We traveled around the world, met several inspirational AdSense publishers, and now we'd like to share their stories with you.

Discover AdSense through the eyes of the people who use it everyday. From French food bloggers to Japanese newspaper publishers, we’re proud of making digital advertising easy for over 12 years -giving our users a safe, reliable source of income and the freedom to make great content.


Almost two million people are using AdSense right now. Learn more about how to start turning your passion into profit today.


Posted by Stacey Garcia
AdSense Marketing Manager

*We've launched our new website in the United States, and local sites are coming soon.

Source: Inside AdSense


Announcing v2.3 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.3 of the DCM/DFA Reporting and Trafficking API. This release brings a number of enhancements, such as:

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.1, which will sunset on February 29th, 2016.

As a reminder, February 29th is also the end of the extended migration window we've provided to users of v2.0 and earlier versions of the API. The current schedule is as follows:

API Version
Deprecation Date
Sunset Date
v1
3 Aug 2015
29 Feb 2016
v1.1
v1.2
v1.3
v2.0
v2.1
4 Nov 2015

To avoid an interruption in service, all users are required to migrate off of these versions by the sunset date.

Learn more

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the Release Notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

Changes to validation for AdWords API iTunes AppConversions

What’s new?

The validation for AppConversions will become stricter starting on November 9, 2015. If you’re using AppConversions in v201509 or v201506 with AppPlatform: ITUNES, you’ll need to make sure that you’re using the correct AppConversionType.

What was the old behavior?

When v201509 was first released, the API would not throw an error if the incorrect value was sent in a request for an iTunes AppConversion. The API automatically converted to the correct AppConversionType. For example, if the value DOWNLOAD was passed into v201509 for an iTunes AppConversion, then that value would automatically be converted to FIRST_OPEN.

What is the new behavior?

In v201509, AppConversionType DOWNLOAD changed to FIRST_OPEN for iTunes apps. Here’s what you will need to do:
  • For v201506 or earlier, you must pass in AppConversionType DOWNLOAD rather than FIRST_OPEN.
  • For v201509 or later, you must pass in FIRST_OPEN instead of DOWNLOAD.
Passing in the incorrect value will result in the error DOMAIN_EXCEPTION from the API starting on November 9.

Note: This only impacts iTunes conversions. There will be no changes to the validation for AppConversions with an AppPlatform of ANDROID.

Where can I learn more?

For more information on mobile apps and conversions, check out these guides: Questions? Visit us on the AdWords API Forum or our Google+ page.

Proguard and AdMob mediation

If you’re an Android developer who uses ProGuard to post-process builds, you already know the improvements it can make to APK size and speed. Just as handy, though, is its ability to obfuscate your compiled code by stripping out debug information and renaming classes, methods, and fields to generic identifiers. It’s a great way to discourage reverse-engineering of your application. If you’re an AdMob publisher who uses mediation, however, you need to take special care when configuring ProGuard in order to avoid obfuscating some of the code used in the mediation process.

AdMob mediation needs two classes to maintain their original names in your final APK: AdUrlAdapter and AdMobAdapter. If either of those has been renamed by ProGuard, it can cause the SDK to incorrectly return “no fill” responses for the AdMob demand in your mediated ad units.

The good news is that it’s easy to avoid this problem. Just add the following two keep options to your ProGuard configuration file:


-keep class com.google.ads.mediation.admob.AdMobAdapter {
*;
}

-keep class com.google.ads.mediation.AdUrlAdapter {
*;
}

These options instruct ProGuard to avoid renaming the two classes, and to leave the names of their fields and methods unobfuscated as well. With the original names intact, the mediation system will be able to instantiate them dynamically whenever they’re needed, and your otherwise obfuscated application won’t miss out on any AdMob impressions.

The third-party networks your app mediates may also need certain classes exempted from obfuscation. Be sure to check with those networks to find out if they have recommendations for ProGuard configuration.

If you have technical questions about this (or anything else relating to the Google Mobile Ads SDK) stop by our forum.

tags: android, admob_mediation, mobile_ads_sdk

Reporting changes in AdWords API v201509

AdWords API v201509 introduces some changes to reporting columns, particularly Clicks. Recently, AdWords introduced new columns called Engagements and Interactions. It also added reporting columns related to video campaigns such as VideoViews, which have previously been unavailable via API reporting. AdWords API version v201509 has updated its reporting to match these changes.

The new Interactions field, available in API performance reports, can be thought of as the main action a user takes with the ad format: clicks for text ads, engagements for Lightbox ads, and views for video ads. Previously, views for video ads were not returned in API reporting, so having access to this data is new.

Prior to v201509, the Clicks field always included both clicks and engagements. Starting in v201509, the Clicks field includes only click actions, like clickthroughs to a landing page or clicks to call. This means that clicks on video ads, which are unpaid, will be included in this field. However, engagements for Lightbox ads will not be counted.

If measuring performance across multiple ad formats, you might consider using Interactions to view the total number of primary user actions on ads, all in the same column. Clicks, Engagements, and VideoViews are available as well for more fine-grained reporting by ad format.

The table below summarizes the changes in each field for various ad formats.

Field
v201506
v201509
Clicks
Text ads: clickthrough to a landing page

Lightbox ads: hover to expanded ad format
Text ads: clickthrough to a landing page or clicks to call

Lightbox ads: clickthrough to a landing page

Video ads: clickthrough to a landing page
Engagements
N/A
Lightbox ads: hover to expanded ad format
VideoViews
N/A
Video ads: view
Interactions
N/A
Text ads: clickthrough to a landing page or clicks to call

Lightbox ads: hover to expanded ad format

Video ads: views

Please note that reporting in v201506 and previous versions is unaffected; they return the same data that they always have, represented the same way. This means that when comparing the data you receive from older versions of the API to user interface reports, or to v201509 reports, the numbers will not directly match up. Video-related stats will still be excluded from v201506. The Clicks column in v201506 will match the Interactions column from v201509 if you subtract out video interactions.

For ease of reporting, it’s recommended to migrate to v201509 as soon as possible.

Keep in mind these aren’t the only reporting changes in v201509 — for more details on conversion-related reporting changes, please see the release notes.

If you have any questions about this or other aspects of the AdWords API, please contact us via the forum or the Ads Developers Plus Page.