The new Google Mobile Ads SDK for Android is now included as part of Google Play services 4.0.
As an Android developer, you’re probably familiar with Google Play services, a unified platform which makes it easy to integrate Google features into your Android apps, delivered through the Play Store and updated at regular intervals. Now that AdMob is part of the package, benefits include:
This new version of Google Play services supports devices running Android 2.3 and higher. We recommend updating your apps right away to make ongoing maintenance of your apps easier. Even if you develop for Android devices that don’t receive Google Play services, the Google Mobile Ads SDK is still compatible with those devices, the difference is that users won’t receive automatic updates. Also, please note, the SDK doesn’t currently support DFP, Ad Exchange or Search Ads for Mobile Apps but support is coming soon.
You can find the new SDK in the SDK Manager; follow these instructions to get it, and find the release notes here. If you have questions about it please post to the forum or check out our G+ page.
Posted by Vishay Nihalani, Product Manager, AdMob
dimensions=ga:pagePath&metrics=ga:adsenseCTR,ga:adsenseRevenue,ga:adsenseECPM&sort=-ga:adsenseRevenue
dimensions=ga:pagePath&metrics=ga:pageviews,ga:adsenseCTR&sort=-ga:pageviews
dimensions=ga:sourceMedium&metrics=ga:adsenseCTR,ga:adsenseRevenue,ga:adsenseECPM&sort=-ga:adsenseRevenue
// Create selector.Selector selector = new Selector();selector.setFields(new String[] { "Id", "Name", "Impressions", "Clicks", "Cost", "Ctr"});selector.setPredicates(new Predicate[] {new Predicate("Impressions", PredicateOperator.GREATER_THAN, new String[] {"0"})});String oneWeekAgo = new DateTime().minusDays(7).toString("yyyyMMdd");String yesterday = new DateTime().minusDays(1).toString("yyyyMMdd");selector.setDateRange(new DateRange(oneWeekAgo, yesterday));
// Create selector.Selector selector = new Selector();List<String> fields = selector.getFields().addAll(Lists.newArrayList( "Id", "Name", "Impressions", "Clicks", "Cost", "Ctr");// Create report definition.ReportDefinition reportDefinition = new ReportDefinition();reportDefinition.setReportName( "Campaign performance report #" + System.currentTimeMillis());reportDefinition.setDateRangeType( ReportDefinitionDateRangeType.LAST_7_DAYS);reportDefinition.setReportType( ReportDefinitionReportType.CAMPAIGN_PERFORMANCE_REPORT);reportDefinition.setDownloadFormat(DownloadFormat.CSV);reportDefinition.setIncludeZeroImpressions(false);reportDefinition.setSelector(selector);
String query = "SELECT Id, Name, Impressions, Clicks, Cost, Ctr" + "FROM CAMPAIGN_PERFORMANCE_REPORT “ + “WHERE Impressions > 0 DURING LAST_7_DAYS";
Last year, we introduced the Ad Exchange Real-Time Bidding Optimization Series on the developer's blog with our first post on post-filtered bids.
Today, we’ll drill down into one of the filtering reasons: Auction filtered.
We’ll revisit the definition of auction filtered bids, review the main reasons for being filtered from the auction, and the steps you can take to ensure your ads will not be filtered.
Auction Filtered: After the bid response passes the Google and publisher checks, it makes its way to the auction. However, the bid may not win the auction due to one of the following:
1. Outbid in auction means that your bid was lower than a competitor’s bid and since AdX uses a second-price auction model, the highest bid wins the auction and pays the price of the second highest bid. One way to make sure you are bidding at a competitive price is to implement the new RTB feature for AdX, Real-time Feedback. The feature will give you feedback on auction results in near real-time, including (1) why your bid was filtered (e.g. disapproved ads, product/sensitive category exclusion, outbid in auction, etc.) and (2) what the winning bid price was (if you lost in the previous auction). We include this information in subsequent bid requests sent to your bidder. You can use this information to improve the efficacy of your own bidding by reducing the number of times you are outbid. The creative_status_code field in the proto buffer will reveal the filtering reason. For example, the creative_status_code field may be 79, meaning you were ‘outbid in auction’, whereas 80 and 81 mean your ‘bid was below the minimum threshold’ and ‘not allowed in private auction’ respectively. You can review a complete list of filtering reasons in the creative-status-codes.txt dictionary file.
2. Bid was below the minimum threshold means that your Max CPM (max_cpm_micros in your BidResponse) was lower than the publisher’s min CPM. Specifically, the bid response contained a max_cpm_micros value that was less than the publisher’s minimum_cpm_micros value. Ensure that your bidder understands the minimum_cpm_micros required by the publisher per bid request and bid at or higher than this price if you are interested in the impression, or submit an empty bid if you are not interested in the impression. The minimum_cpm_micros value is listed in the AdSlot section of the bid request. You can review more details in the realtime-bidding-proto.txt file.
3. Not allowed in private auction means that your bid is being filtered for a preferred deal or private auction impression that you were not allowed in. Using the Preferred Deals UI, view Open Offers and consider negotiating your own deal or private auction with publishers of interest.
New! RTB Dashboard is a tool designed to bring greater transparency to you, as a buyer, and help you refine your bidder to produce more efficient bidding and better results for your campaigns. With RTB Dashboard, you have the ability to review the “RTB insights” section which helps you understand which bids are being filtered out and why:
So, what can you do with the information available in ‘Insights’? Two of the most common auction loss reasons and solutions are:
For both auction loss reasons you may want to find out more. Under the ‘Action’ column a ‘Details’ link allows you to view the auction loss count aggregated by either publisher domain or your creative ID for the specific auction loss reason.
Have questions or feedback? Reach out to your Ad Exchange account team.
Posted by the Ad Exchange Team
We've noticed a lot of interest in having the Google Ads APIs Python Client Library made available on PyPI, so we're happy to announce that we've recently added support for it. If you use a tool such as pip, you can now install or update to the latest version of the library with all its dependencies using one simple command, for example:
pip install [--upgrade] adspygoogle
This feature was added based on community feedback, so if you have additional feature requests or a bug to report, feel free to let us know about it by creating an issue on our issue tracker or contacting us on our Google+ page.
