Subscribe: AdWords API Blog
http://adwordsapi.blogspot.com/atom.xml
Added By: Feedage Forager Feedage Grade A rated
Language: English
Tags:
ads  adwords api  adwords  api team  api  flash  forum  mobile ads  new  questions  release  sdk  support  team  text ads 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: AdWords API Blog

Google Ads Developer Blog



The official blog for information about the AdWords, AdSense, DoubleClick and AdMob APIs and SDKs.



Updated: 2017-02-21T09:48:37.328-08:00

 



Upcoming DCM/DFA Reporting and Trafficking API system maintenance

2017-02-21T09:48:37.399-08:00

Starting in March, DoubleClick Campaign Manager (DCM) will be undergoing scheduled maintenance to make important updates to our systems. Every DCM account will be assigned a single maintenance window. However, these windows may be on different days for different accounts. More information about how this will affect the DCM product can be found in our help center.

How will this affect API users?

Maintenance is expected to last up to 8 hours per account. During that time DCM Trafficking will be read-only. While in read-only mode, all API delete, insert, patch, and update methods requiring the DCM Trafficking scope will be disabled. See the Scheduled Maintenance page on our developer site to learn more about the methods that will be impacted and the errors you may encounter.

What can API users do to prepare?

If your application accesses a single DCM account, we recommend simply planning ahead to avoid running workflows that use affected API methods during your account's maintenance window. Details of when this window will occur will be communicated in advance via in-product notification.

If your application accesses multiple DCM accounts, you may be subject to multiple maintenance windows. If it's not possible to plan around these windows, you should prepare your application to catch and handle maintenance related errors. Recommended error handling strategies include:

  • For user initiated requests, return an error to the user along with instructions to wait up to 8 hours before retrying the request.
  • For server initiated requests, retry automatically using an exponential backoff strategy. For example: pause 30 seconds before the first retry, 1 minute before the second, 2 minutes before the third, and so on up to a maximum of 8 hours. This strategy helps ensure you're not calling the API too aggressively and that your request quota is not being wasted.

Questions about this or anything else DCM API related? Contact us via our support forum.

(image)




Announcing v201702 of the DFP API

2017-02-14T10:35:21.814-08:00

Today we're pleased to announce the v201702 release of the DFP API. This release adds a new PublisherQueryLanguageService table: Change_History. This table contains entries for changes to entities in your network. This allows for the long-awaited ability of querying for DFP entity changes programmatically.

Additionally, v201702 adds the NativeStyleService, which allows you to read, create, and update native styles.

For a full list of API changes in v201702, see the release notes.

With each new release comes a new deprecation. If you're using v201605 or earlier, it's time to look into upgrading. Also remember that v201602 will be sunset at the end of February 2017.

As always, if you have any questions, feel free to drop us a line on the DFP API forums or the Ads Developer Google+ page.

(image)




Latency best practices in the IMA SDKs

2017-02-09T10:35:36.784-08:00

One of the most important factors in keeping users on your page or in your app is latency - the lower your latency, the more likely your users are to stick around. With this in mind, we'd like to remind you about our best practices for reducing latency with the IMA SDKs. In general, you can reduce latency by doing as much IMA set-up work as possible on page or app load, before your user tries to play a video. The following can be done in all of the SDKs before the user attempts to play a video:

  • Creating your ads loader.
  • Creating your ads request.
  • Requesting ads.
  • Obtaining the ads manager.
  • Registering ads manager event handlers.

You can find more information on optimizing latency in each of our SDKs at the links below:

As always, if you have any questions, feel free to contact us via the support forum.

(image)



Budget Optimizer and Conversion Optimizer Sunset in AdWords

2017-02-08T12:38:07.121-08:00

What’s happening?In March 2017, we will stop supporting the Budget Optimizer and Conversion Optimizer bidding strategies in AdWords. These strategies have long been unavailable for user opt in. We will migrate existing campaigns that use these legacy strategies to use their replacement counterparts which offer identical features: Budget Optimizer -> Target Spend Conversion Optimizer -> Target Cpa or Manual CPC There will be no change in performance after the migration. What do I need to do?If you are satisfied with your current Budget Optimizer or Conversion Optimizer setup, then you don't need to do anything to your existing campaigns -- Google will automatically migrate them for you. If you prefer manually migrating your campaigns before the automatic migration begins, you may refer to the automatic migration steps below. Refer to our bidding guide and help center articles on target CPA and target spend strategies to learn more about the new bidding strategies. What will the automatic migration do for Conversion Optimizer campaigns? Convert the campaign's bidding strategy to standard target CPA. Identify all ad groups of the campaign and their CPA bids, calculate the most common CPA bid value, and set the campaign's target CPA value to this value. If no CPA bids exist, Google sets the campaign's target CPA to the minimum billable unit. Pause any ad groups that do not have a CPA bid. This prevents previously inactive ad groups from inheriting the campaign's new target CPA value and inadvertently serving. What will the automatic migration do for Budget Optimizer campaigns? If no ad group level bidding strategy overrides exist, update the campaign’s bidding strategy to a standard target spend strategy. If the enhancedCpcEnabled field is set to true for the budget optimizer strategy, set it for the target spend strategy also. If some--but not all--ad groups have overrides, update the the campaign’s bidding strategy to a new portfolio target spend strategy. This preserves the ad group level bidding strategy overrides. In the rare case that all ad groups have overrides, update the campaign’s bidding strategy to standard manual CPC. The campaign level bidding strategy doesn’t matter in this case since all the ad groups have overrides. However, changing the campaign’s bidding strategy to manual CPC helps us avoid creating portfolio target spend strategies for each ad group in the campaign. As always, if you have any questions about this change or other API features, please post on the forum. - Mike Cloonan, AdWords API Team[...]



DCM/DFA Reporting and Trafficking API sunset reminder

2017-02-03T09:49:51.506-08:00

In accordance with our deprecation schedule, we'll be sunsetting versions 2.5 and 2.5beta1 of the DCM/DFA Reporting and Trafficking API on February 28th, 2017. On this date, all requests made against these versions will begin returning HTTP 403 errors.

If you're still working with these versions, we strongly encourage you to begin migrating to the most recent release to avoid an interruption in service. If you're not sure, or would like to know more about the migration process, refer to the migration guide.

As always, feel free to reach out to us with any questions that you have.

(image)




Automatic removal of invalid location extension filters

2017-01-24T09:03:01.359-08:00

AdWords offers several different strategies for configuring filters for your Google My Business locations. However, users sometimes choose filters that do not match any locations, which results in no location extensions appearing with ads.

What's changing?
Starting on February 14, 2017, AdWords will perform a daily check to determine if the following location extension feed item filters are not matching any Google My Business locations: If any such invalid filters are found, they will be automatically cleared as outlined in the updated Location Extensions guide.

Please keep the following details in mind:
  • The periodic check will only clear matchingFunction filters on a CampaignFeed or AdGroupFeed for location extensions (placeholderType = 7). It will not clear filters on those objects for location targeting (criterionType = 77).
  • The periodic check will not clear matching functions of the form IDENTITY(false), since these indicate that you want to disable location extensions for a campaign or ad group.
What you should do
  1. To minimize the impact of the periodic check, regularly review your application's location feed setup and ensure that you are choosing filtering options on your PlacesLocationFeedData and matching functions that actually match locations in your Google My Business account.
  2. Make sure that your application will be able to handle the filter changes made by the periodic check.
If you have any questions, please post on the AdWords API Forum.
(image)



Upgrade to AdWords API campaign drafts and experiments before February 1st

2017-01-23T11:01:48.228-08:00

Last year, we announced that you have until February 1st, 2017 to upgrade from ExperimentService to the new campaign drafts and experiments introduced in v201603. After this date, you’ll no longer be able to use ExperimentService.
  • API calls to ExperimentService across all API versions will result in an error
  • All experiments running via ExperimentService will be stopped
  • All ExperimentService experiments will be deleted and their stats will be unavailable
Check out our Campaign Drafts and Experiments guide for examples while upgrading your code. If you have questions while you’re upgrading, please reach out to us on the AdWords API forum.
(image)



Upgrade to expanded text ads and responsive ads before January 31st

2017-01-18T08:04:27.456-08:00

Last year, we announced that you have until January 31st, 2017 to upgrade your standard text ads to expanded text ads or responsive ads. After this date, you’ll no longer be able to create new standard text ads. Existing standard text ads will continue serving alongside expanded text ads and responsive ads.

To prevent any errors when creating ads, it’s important to immediately upgrade to expanded text ads or responsive ads before January 31st, 2017. To help you get started, we’ve put together a few resources: If you have questions while you’re upgrading, please reach out to us on the AdWords API forum.
(image)



Mobile search ads will feature a click-to-call option automatically after Feb 6th

2017-01-19T12:16:37.056-08:00

TL;DR: New feeds and feed items will automatically be added to eligible AdWords accounts.

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:
  1. On the Ad extensions tab select “View: Automated extensions report”
  2. Scroll down to “Automated extension options (advanced)” and click on “Edit”
  3. Uncheck the option for “Automatic call extensions” under “Do not use specific automated extensions in this account”. 
As always, if you have any questions about this announcement, or other questions about the AdWords API, contact us via the forum.
(image)



Accountstatuses to now include validation issues in Content API for Shopping

2017-01-11T08:14:16.271-08:00

Starting on January 17th, 2017, Accountstatuses will return all the errors and warnings present in the Diagnostics tab of Merchant Center. This updates Accountstatuses to match the changes to Productstatuses from last August, so Accountstatuses will now report validation issues as well as data quality issues. This means that developers may see more issues returned by Accountstatuses than before.

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.
(image)



Deprecating Flash in the IMA SDKs

2017-01-04T11:49:26.532-08:00

On June 1, 2017, Google will cease development of Flash in the IMA SDKs. This will end support for the IMA SDK for Flash, as well as support for Flash VPAID ads in the HTML5 SDK. We strongly encourage all publishers still using the Flash SDK to migrate to the HTML5 SDK. We also strongly encourage advertisers still trafficking Flash VPAID ads to migrate those ads to JavaScript VPAID.

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?

We will no longer support Flash VPAID ads in the HTML5 SDK. Flash VPAID ads served to the HTML5 SDK will not be rendered and the SDK will fire an error. We strongly encourage you to migrate your Flash VPAID ads to JavaScript VPAID.

As always, if you have any questions, feel free to contact us via the support forum.

(image)



Sunset of DFP API v201602

2017-01-03T12:54:42.938-08:00

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_EXCELhas been renamed TSV_EXCELto more accurately describe its actual format. Team.companyIds, Team.adUnitIds, and Team.orderIdshave been removed. Use Company.appliedTeamIds, AdUnit.appliedTeamIds, and Order.appliedTeamIdsinstead. Order.programmaticSettingshas 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.  - Chris Seeley, DFP API Team[...]



Upcoming changes to AwReporting

2017-01-03T08:40:51.409-08:00

AwReporting is an open-source Java framework that is optimized for large-scale retrieval of AdWords API reports.

We plan to release a new major version (v2.0) within the next few months that will
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
If you are actively using the aw-reporting-server or aw-reporting-server-appengine module or have any questions about this upcoming release, please let us know on this forum thread.
(image)



Mobile Ads Garage #12: Native Express in a UITableView

2016-12-27T09:28:37.158-08:00

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.

width="560" height="315" src="https://www.youtube.com/embed/chNb7-k6m4M?list=PLOU2XLYxmsIKX0pUJV3uqp6N3NeHwHh0c" frameborder="0" allowfullscreen>

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.

Until next time, be sure to stay connected on all things AdMob by following our Twitter, LinkedIn and Google+ pages.

(image)



Announcing the new ads PHP client library

2016-12-21T17:11:47.670-08:00

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.

As always, if you have any questions, feel free to drop us a line on the AdWords or DFP API forums, or the Ads Developer Google+ page.

(image)




AdMob Native Express ads in a content feed

2016-12-16T09:05:51.360-08:00

Today we're excited to announce iOS and Android sample projects that display AdMob Native Express ads in a feed. These samples address a common use case for monetizing apps with feeds or lists of content. The iOS (Swift and Objective-C) apps display Native Express ads in a UITableView and the Android app shows them in a RecyclerView.

Native Express ads work well in lists of content for two reasons. First, impressions are not counted until the ad is on screen, which enables you to preload the ads ahead of time. Preloading can help with optimizing scroll performance by making sure the ad is ready to be displayed when the user scrolls through the list. Second, you have more control over the styling of the ads, allowing you to create presentations that fit naturally with your content.

You can check out these sample apps by downloading them from our iOS and Android GitHub repos, and you can see them being coded in the Mobile Ads Garage YouTube series. Episode 11 walks you through the implementation for adding native ads into an Android RecyclerView. Episode 12, which will cover the implementation of native ads in an iOS UITableView, is due out next week.

If you have any questions or feedback regarding our SDK, feel free to contact us through our forum.

(image)



Announcing support for video campaigns in AdWords scripts

2016-12-13T13:46:48.680-08:00

Today we're announcing the release of video campaign management support in AdWords scripts. You can now create and manage in-stream, video discovery, and bumper ads in your existing video campaigns, set targeting for your video campaigns and ad groups, and report on performance including views and view rate.

To get started, visit our Video Campaigns guide for an overview of the new functionality. You can also view a variety of samples both in the docs and by using the Show examples button in the script editor. These are pre-built functions that may be useful to drop into your code or use as the basis for expansion into your own custom script.

When you're ready to dig in or when you're ready to learn more, check out the "Video" section of the left navigation bar under our AdWordsApp documentation.

If you have any questions about this new feature or AdWords scripts in general, you can post them on our developer forum.
(image)



DCM display ads go 100% HTML5 on January 2, 2017

2016-12-13T13:13:28.018-08:00

As you've probably heard, DCM will stop serving Flash display ads on January 2nd, 2017. This is part of a wider initiative to go 100% HTML5, which you can learn more about in the DCM help center.

What does this mean for DCM/DFA Reporting and Trafficking API users?

Beginning on January 2, 2017, the following changes will take effect:

  1. Flash uploads will be disabled in API v2.5. Beginning with v2.6, the DCM API stopped supporting uploads of Flash assets and prevented users from creating new Flash In-page creatives. These same restrictions will be applied to v2.5.
  2. Active Flash creatives with no HTML5 equivalent will be deactivated. Existing creatives that have not been converted to HTML5 will have their active field set to FALSE. Users will not be allowed to reactivate these creatives.

What can API users do to prepare?

Users are strongly encouraged to review their active creatives and take immediate action to replace those that will be affected by this change. We've created code samples in Java and Python to help API users identify creatives in their accounts that will be deactivated if no action is taken. See this article for links to tools to help you transition your creatives to HTML5.

Users of DCM API v2.5 are also encouraged to begin migrating to a newer API version immediately. Be aware that this version is already scheduled to sunset on February 28th, 2017.

Questions about this or anything else DCM API related? Contact us via our support forum.

(image)




Updated release schedule for AdWords API

2016-12-13T08:59:27.564-08:00

At the beginning of the year we announced an experimental bi-monthly release schedule for the AdWords API. Based on the results of this pilot and feedback from our developer community, we've decided on a quarterly release schedule for 2017. The 2017 API releases are scheduled for February, May, August and October.

We received positive feedback on increasing the release frequency from the previous three-times-a-year schedule. We also heard that the accompanying sunset schedule was an added burden for some API users. The quarterly release schedule aims to address this feedback. We will continue to monitor the release frequency and your feedback

On average, every AdWords API version released in 2017 will be available for approximately 10 months. One month after every major release, we will sunset the oldest outstanding API version. Similar to the 2016 schedule, we will support 3 releases concurrently at all times and 4 releases for a brief period of 4 weeks at a time to accommodate developers who want to skip two major releases.
(image)
As a reminder, v201605 is scheduled to sunset on February 28, 2017. We will post details about the release and sunset of other AdWords API versions on this blog and our developer site. If you have any questions, feel free to reach out to us on the AdWords API forum.
(image)



Announcing v201611 release of the DFP API

2016-12-07T11:28:06.047-08:00

Today we’re pleased to announce the v201611 release of the DFP API. This release contains the addition of MobileApplicationService, which allows you to claim apps from various app stores to use for targeting in your network. For a full list of API changes in v201611, see the release notes.

With each new release comes a new deprecation. If you're using v201602 or earlier, it's time to look into upgrading. Also remember that a double sunset happened at the end of November 2016 - both v201508 and v201511 have been sunset.

As always, if you have any questions, feel free to drop us a line on the DFP API forums or the Ads Developer Google+ page.

(image)




Final days for migrating AdWords ads from Flash to HTML5

2016-12-06T14:21:10.866-08:00

What do I need to do?
Please migrate any existing Flash display ads to HTML5 by January 2, 2017, when Flash ads will stop serving. In May 2016 we announced that you would no longer be able to upload Flash display ads in AdWords by June 30, 2016 with tips on how to migrate.

If you have video ads built in Flash, they will not be affected at this time. You do not need to migrate these ads.

Where can I learn more?
Questions? Visit us on the AdWords API Forum or our Google+ page.
(image)



Mobile Ads Garage #11: Native Express in a RecyclerView

2016-12-02T09:55:50.688-08:00

Episode 11 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.

In a break with tradition, this video is a deep technical dive on one subject: Native Ads Express in an Android RecyclerView. You'll learn how to modify an existing RecyclerView implementation to include Native Express ads, all the way from updating the adapter to loading the ads. In addition, you'll get a clever trick that makes sure your ads are always sized to match the UI, so they fit right in with your content.

If you haven't used Native Ads Express before, you can see them in action in Episode 7. Andrew and Gary cover all the basics: loading ads, placing them in layouts and storyboards, and using CSS to style the ads to match your app.

width="560" height="315" src="https://www.youtube.com/embed/LZCZSeFTvyk?list=PLOU2XLYxmsIKX0pUJV3uqp6N3NeHwHh0c" frameborder="0" allowfullscreen>

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.

Until next time, be sure to stay connected on all things AdMob by following our Twitter, LinkedIn and Google+ pages.

(image)



Changes in severity for validation issues in the Content API for Shopping

2016-11-22T10:16:59.454-08:00

In August, we announced that returned Productstatuses would include any validation issues. Unfortunately, the way validation issues used the severity field differed from data quality issues, which led to confusion.

To clarify which validation issues are serious and which are just warnings, we will use the same mapping for validation issues as we do for data quality issues. In addition, we have published an accompanying guide, API Issue Severity and Diagnostics Issue Prioritization, which discusses how to compare the issue prioritization used in the Diagnostics section of the Merchant Center to the issue severity provided in the responses from the Productstatuses and Accountstatuses services.

As always, if you have any questions about these changes or any other questions or feedback about the Content API for Shopping, please let us know on the forum!
(image)



Save time creating expanded text ads with the ETA Transition Helper

2016-11-21T12:48:59.001-08:00

Since we introduced expanded text ads (ETA) earlier this year, we’ve recommended that advertisers create and test multiple ETAs to determine what messages perform best for their business. To help you do this at scale, we’ve created the ETA Transition Helper, a powerful tool that allows you to easily create ETAs in bulk using AdWords Scripts and Google Sheets.

This tool helps you save time by using your existing standard text ads (STAs) as a blueprint for your new ETAs. The ETA Transition Helper ensures your expanded text ads are formatted according to the new character limits and that their display URLs use the final URL's domain. After creating the new ETA, the tool displays your current STA and the new ETA side-by-side in a Google Sheet so you can easily compare the two ads. Please note that the tool's interface is only offered in English at this time, but it supports exporting STAs and creating ETAs in all languages.

As a reminder, starting January 31st, 2017, you will no longer be able to create or edit STAs, though existing STAs will continue to serve alongside ETAs.

Get started by checking out the user guide. You can also contribute to the ETA Transition Helper project on GitHub today. If you have any questions or would like to provide feedback, feel free to contact us on the AdWords Scripts Forum.
(image)



Announcing a deprecation policy for older versions of the iOS and Android IMA SDKs

2016-11-17T11:02:11.049-08:00

On February 1, 2017, we will implement a new deprecation policy for the IMA SDKs for iOS and Android. The Flash and HTML5 SDKs are unaffected by this policy because they are downloaded at runtime, so all developers are always using the latest version.

Each release will be deprecated 12 months after its successor is released.

As of February 1, 2017, the following SDK versions will no longer be supported:

  • IMA Android prior to version 3.1.3
  • IMA iOS prior to version 3.1.0

If you are currently on one of these versions, we strongly suggest upgrading to the latest version before the new policy takes effect.

Once an SDK version is deprecated, we cannot guarantee that version will continue to work. If we receive reports of crashes related to a deprecated version of the IMA SDK, we may discontinue serving ads to that version. We will also no longer field support requests for these versions on the IMA SDK support forum.

To maintain support, publishers on the latest version of an SDK will have 12 months to move to a new version once its successor is released. To "support" an SDK means we will investigate bugs in that SDK version and work on fixes. If a bug fix requires a change to the library itself, the fix will be applied to the newest version.

For a list of supported SDK versions and their deprecation dates, see the new deprecation schedule pages for iOSand Android. As always, if you have any questions, feel free to contact us via the support forum.

(image)