Google Display Network to Serve Ads with No Targeting Begining Jan 18th

Ad groups with no targeting method selected will automatically show ads on Google Display Network, so long as they have a bid set and at least one approved ad.

Share online:

Google has announced of makeing advertising for display and video campaigns simpler, which will take effect starting January 18th, 2017.

So what's changing? According to Google, begining Jan 18, if an ad groups with no targeting method selected has a bid set with at least one approved ad, "will automatically be eligible to show ads on the Google Display Network."

And, the current display and video ad groups, that don't have a targeting method will be paused on Jan. 18th, ensuring "they don't show ads you don't intend to show."

Further, Google advising advertisers said, to manually pause any new ad groups that aren't ready or that you don't want to show ads. As well as, as a best practice "evaluate your targeting options whenever you create an ad group."

For more about this upcoming change, you can refer the AdWords Help Center.

Are you worried about to know if other sites are using your AdSense ad code? So, what to do when you see sites under your performance reports or sites list that don't belong to you, "the most common reason is another site has copied your site code and pasted it onto their site" without modifying the HTML, they also copied the ad code in the process, explains Google.

Since your publisher id is still in their ad code, so those site(s) are appearing in your AdSense account, but to combat, Google advising yo verify your sites and turn on site authorization. To make following two changes in to your account:

First up, verify your sites in the account, "Sign in to your AdSense account, then click Settings in the sidebar, next up in the dropdown, select My sites, and in your site list, locate the site you want to verify and click the Down arrow, finally next to "Verified site", turn the switch on."

Once you've verified your sites, enable site authorization, and optional feature that lets you identify your verified sites as the only sites that are permitted to use your Google ad code:

Click Settings in the sidebar, next in the dropdown, select My sites, and on the "Manage sites" page, click More, then click Site authorization, and next to "Only authorize my verified sites to use my ad code", turn the switch on, finally click Save. The changes made will take effect within 48 hours.

Once the autherization is turned on, Google notes, "the ads will however still show on the unverified site(s), with impressions and clicks recorded as well. However, advertisers willn't be charged, and you won't receive any earnings for that site." And most importantly, "any policy violations that occur on these sites also won't count against you."

Since these URLs will still show up in your list of sites, you can set up your report type to "Verified Sites" to ensure you are only seeing data related to your verified sites.

In an Mobile Ads Garage episode, you'll learn how to integrate Native Express ads into an iOS app that uses a UITableViewController for its primary UI. Along the way you'll also get a detailed set of step and see screencasts of an implementation in Xcode.

In addition, this episode also covers a handy technique for tapping into the ad lifecycle to load native express ads sequentially, from the top of the list to the bottom.

native express in a uitableview

Watch the video below:

Google recipe search results on mobile update in the US, now sporting a carousel of keywords at the top of search results. Alongside keywords, there's also a recipe cards carousel, which when tapped take you to a page where the recipe is published. While tapping a keyword in the carousel will bring up a new set of Google search results.

Tapping on a recipe idea in the new keyword carousel will help you refine the search. Google brings you to a new page full of relevant recipe cards. In the new page you can continue to tap on the keywords to narrow down your search even further, Google will dynamically update its search results with each selection.

google mobile receipe search results

Update 01/04: The AdWords team has announced of an upcoming new major version 2.0 of AwReporting, an open-source Java framework that is optimized for large-scale retrieval of AdWords API reports.

The release will take place within the next few months and that will provide a full suite of reports with a full list of fields, as well as support using raw enum values and excluding hidden accounts. In addition, this release will have some backwards incompatible changes, such as

  • uses report type names with "AW_" prefix as database table names
  • uses field names as database column names
  • renames setting "mccAccountId" to "managerAccountId" in properties file
  • renames setting "aw.report.downloader.retries.count" to "aw.report.downloader.num.attempts"
  • renames processor type setting's options from "ON_FILE" to "FILE", and "ON_MEMORY" to "STREAM"
  • removes "-debug" and "-verbose" command line options, and depends on log configuration file (default one is log4j.properties) for setting logging granularity
  • removes server modules (aw-reporting-server and aw-reporting-server-appengine) in the new release since they have third-party dependencies that are not actively maintained

Google is also sunsetting DFP API v201602, on February 28, 2017, with that any requests made to this version at that time will return errors, google said.

To avoid issues later, Google advising to upgrade to latest release, to start taking advantage of new features like HTML5 creatives, programmatic support, and retrieving saved report queries. Significant changes include:

  • reporting format CSV_EXCEL has been renamed TSV_EXCEL to more accurately describe its actual format.
  • Team.companyIds, Team.adUnitIds, and Team.orderIds have been removed. Use Company.appliedTeamIds, AdUnit.appliedTeamIds, and Order.appliedTeamIds instead.
  • Order.programmaticSettings has been replaced by Proposal.ProposalMarketplaceInfo.
  • getCustomTargetingValuesByStatement() now enforces the requirement of a custom targeting key ID in the filter statement.

Update 01/06: Google Best Practices for AdWords a new guide published today to testing and experimentation by using all of the tools available including campaign drafts and experiments in AdWords, you can test and understand whether any proposed changes to your account will help you reach your business goals.

The guide covers topics such as: "Testing changes to your AdWords account, Creating experiments that produce clear results, Analyzing results to choose experiment winners."

Experimenting with your own account, you can use this guide to take full advantage of AdWords campaign drafts and experiments.

Update 01/10: Google began notifying advertisers that as of January 19, it may show location-specific phone numbers when location extensions display, even if a different number is used in call extensions. Advertisers that have location extensions are advised to ensure their Google My Business listings have the accurate phone numbers for each location.

In another update, the company is notifying advertisers that as of February 6, 2017, call extensions will start generating automatically. "landing pages prominently featuring a phone number," the email stated.

Google Location-specific phone

Google automated call extension in mobile ads