This year, mobile search engines are predicted to drive nearly 33 billion clicks-to-call to businesses globally, almost 19% more calls than from mobile landing pages alone (BIA/Kelsey, July 2016). Using Google call extensions, you can get more calls by making it easy for people to contact you right from your mobile search ads.
If you manage accounts with ads that take users to landing pages prominently featuring a phone number, starting February 6, 2017 you will see call extensions automatically added for these mobile search ads via the extension setting services.
When added automatically, the new feed will have ORIGIN of "USER". You can update call extensions yourself directly with Feed services, Call Extensions or the AdWords user interface at any time.
You’ll be able to get detailed reporting insights (API report) about your calls performance (including call duration, call start and end time, caller area code) and whether the call was connected. You can also set up call conversion tracking to see which parts of your campaigns are driving the most valuable calls.
These extensions will only be added automatically once to each campaign or ad group and will not be re-added if modified or removed in the user interface or via the API. You can also indicate if you don't want extensions to be created for a specific account in the AdWords user interface:
- On the Ad extensions tab select “View: Automated extensions report”
- Scroll down to “Automated extension options (advanced)” and click on “Edit”
- Uncheck the option for “Automatic call extensions” under “Do not use specific automated extensions in this account”.
Accountstatusesto match the changes to Productstatuses from last August, so
Accountstatuseswill now report validation issues as well as data quality issues. This means that developers may see more issues returned by
If you have any questions or feedback about the changes to issue reporting or other questions about the Content API for Shopping, please let us know on the forum.
What does this mean for the Flash SDK?
We will not actively prevent ad serving to the Flash SDK. However, new releases will stop after June 1st and we will no longer fix bugs or answer support questions. If ad serving or playback stops working after this date for the Flash SDK, it will not be fixed. We strongly encourage you to migrate to the HTML5 SDK.
What does this mean for the HTML5 SDK?
As always, if you have any questions, feel free to contact us via the support forum.
On Tuesday, February 28, 2017, in accordance with the deprecation schedule, v201602 of the DFP API will be sunset. At that time, any requests made to this version will return errors.
If you're still using this version, now's the time to upgrade to the latest release and take advantage of new features like HTML5 creatives, programmatic support, and retrieving saved report queries. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.
Significant changes include:
- The 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.
This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.
We plan to release a new major version (v2.0) within the next few months that will
- provide a full suite of reports with a full list of fields
- support using raw enum values and excluding hidden accounts
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
Episode twelve of The Mobile Ads Garage is live on YouTube! If you haven't seen it before, The Mobile Ads Garage is a video tutorial series that covers how to use the Mobile Ads SDK to display ads from AdMob and DoubleClick for Publishers. Each episode covers one aspect of the SDK, breaks down the feature, and shows screencasts of real implementations on both Android and iOS – all in a friendly format.
With their customizable presentations and ability to be precached, Native Express ads fit right in with list-based user interfaces:
In this deep dive episode of the Mobile Ads Garage, 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 get a detailed set of step and see screencasts of an implementation in Xcode. The 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.
If you like the video, save the Mobile Ads Garage playlist to your YouTube Playlist collection and you'll never miss an episode.
We'd love to hear which AdMob features you'd like to learn more about. The comment sections for the videos are open, and you're welcome to toss out ideas for new episodes and examples you'd like to see. If you have a technical question relating to something discussed in one of the episodes, you can bring it to our support forum.
Hello ads PHP developers! Today we're pleased to announce the stable release of the new ads PHP client library. This has been in beta for a while now, is a huge overhaul of the library, and offers the following improvements:
- Uses namespaces and conforms to PSR-4 autoloading.
- Conforms to PSR-3 for logging.
- Supports installation via Composer.
- Uses the Google PHP auth library for OAuth2, offering more features, flexibility, and service account support.
- Uses Guzzle for non-SOAP HTTP calls, conforming to PSR-7.
- Contains better object-oriented library design and stub interfaces, including builders to configure settings.
- Contains upgraded and easier to use utilities for AdWords reporting, AdWords batch jobs, and DFP reporting.
- Enables SSL by default for SOAP API calls and non-SOAP HTTP API calls.
This library has been pushed to the master branch on GitHub. The old library is now deprecated and moved to a deprecated branch with reduced support until it reaches end of life (EOL) on July 31, 2017. Reduced support details can be found in issue #193. To help you upgrade, we've written an upgrading guide.