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  new  questions  release  sdk  support  team  text ads  text  version 
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-01-19T12:16:37.048-08:00

 



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)



Customize AdWords ads with ad customizer default values or text ad IF functions

2016-12-09T11:13:20.277-08:00

Update December 9, 2016: The previous version of this announcement indicated that this would be rolled out within the next month. This is now going to be rolled out over the next few months. If you would like to check to see if your account has this feature enabled, try editing one of your ads and adding a {. A drop-down should appear. If the option IF function is available, then the feature has been enabled for the account. Over the next month, AdWords is rolling out to all accounts two new ways to customize your ads. Default values in Ad Customizers give you an option of providing a default value when referencing a custom value from a feed. This means that you will no longer be required to provide a static ad in your ad group when using ad customizers. Woohoo! IF functions let you insert a customized message in your ad based on who’s searching and what device they’re searching on, all without using a feed. Default values in Ad Customizers What’s changing? The existing syntax for inserting a custom value from a feed is {=FeedName.AttributeName}. The new syntax allows for an optional default value {=FeedName.AttributeName:default value}, but you can still use the existing syntax if you don’t want to specify a default value. Check out the Customizing text ads guide to learn more about setting up an ad with ad customizers. How does this affect me? If you have colons in your Feed.name or in your FeedAttribute.name, then add a backslash before the colon to escape the colon. Having a colon without a backslash causes anything after it to be interpreted as a default value when used in an ad customizer. If you no longer want to have a static ad in your ad group, then start adding default values to your ad customizers and delete the static ad. IF functions What’s changing? The new IF function allows text to be specified in a text ad based on device or audience, with the default text being optional. If default text is not specified, then a static ad is required in the ad group. The syntax is: {=IF(device=mobile,text to insert):optional default text} {=IF(audience IN(,),text to insert):optional default text} How does this affect me? If you want to add customized text to your ad based on device or audience, start adding the IF functions to your text ads. For examples, check out the Customizing text ads guide. Questions? Visit us on the AdWords API Forum or our Google+ page. Nadine Sundquist, AdWords API Team[...]



IMA SDK-owned ad playback for Android is here

2016-11-14T11:37:25.499-08:00

Integrating with the IMA SDK for Android has historically meant implementing the VideoAdPlayerinterface and playing video ads in your content player. While this approach offers maximum flexibility, it also requires a lot of extra work to get up and running. In our mission to make developers' lives easier, we are proud to offer an alternative: SDK-owned ad playback, added in our newest release, v3.5.2.

Using SDK-owned ad playback, the SDK takes care of playing ads in its own player, allowing you to focus on content playback and the normal ad request flow in your player. With SDK-owned playback, you no longer have to implement a VideoAdPlayer, or worry about VideoAdPlayerCallbacks. Enabling SDK-owned playback is straightforward: simply omit the setAdPlayer call on your AdDisplayContainer.

With the new, simplified integration flow using SDK-owned playback, integrating with the IMA SDK for Android is easier than ever! For a step-by-step guide, head over to our revamped Get Started guide or download the BasicExampleproject from GitHub and try it out.

SDK-owned ad playback allows publishers to simplify their IMA implementation, but using it is not required. If you already have a VideoAdPlayerimplementation or want to use a single video player for both ads and content, you can keep using custom playback. SDK-owned playback merely gives you the option to let the SDK handle some of the implementation complexity for you.

If you have any questions about SDK-owned playback, feel free to contact us via the support forum.

(image)



Support for internationalization in price extensions for AdWords API

2016-11-14T08:02:13.428-08:00

Earlier this year, we added support for managing price extensions to the AdWords API. This included the addition of PriceFeedItem to extension setting services in v201607, and placeholder type ID 35 to feed services in all versions of the AdWords API. At that time, both supported only English price extension type, price qualifiers and price units. Starting today, we are rolling out support for additional languages in price extension types, price qualifiers and price units. Price extensions’ headers and descriptions will be reviewed in the context of the specified language, and those written in languages other than the specified one will be disapproved. How to use this feature Extension setting services: Set language to the locale of your desired language and use priceExtensionType, priceQualifier and priceUnit in the same way as before. Feed services: Check out the translated price extension types, price qualifiers and price units, and ensure that you use the translated price feed type (placeholder field ID 1), price qualifier (placeholder field ID 2) and price units (placeholder field ID 103, 203, …, 803) that match with the language code you specify as placeholder field ID 4. For all available placeholder fields for price feeds, refer to the feed placeholders page. Note: All PriceTableRow entries must have the same currencyCode or you will get the ExtensionSettingError.INCONSISTENT_CURRENCY_CODES error. If you have any questions, please post on the forum or the Ads Developers Plus Page. - Thanet Praneenararat, AdWords API Team[...]



How to properly refresh your OAuth2 access token in DFP API

2016-11-14T07:12:50.235-08:00

In July we announced that starting in August 2016, all versions of the DFP API would return HTTP 401 errors instead of SOAP AUTHENTICATION_FAILED errors. We have learned that some developers have been relying on catching an AUTHENTICATION_FAILED error to know when to refresh an access token. This is not the recommended way to determine when your access token needs refreshing and is not supported.

The change described above will break code that relies on catching an AUTHENTICATION_FAILED error. We have temporarily rolled back the change to give developers who haven’t migrated more time to update their code and will roll this change out again on November 30, 2016 and ask that you update your code before then.

Note: If you’re taking advantage of our client libraries, no change is required; our client libraries handle refreshing an access token with our recommended approach.

Instead of relying on an AUTHENTICATION_FAILED error, the recommended way is to calculate how soon the access token is going to expire before making an API call, and refresh it if it’s about to expire soon.

  • Whenever you obtain a new access token, calculate the token’s expiration time by adding the expires_in time returned with the access token to the current time.
    • For example, if you received an access token on Oct 21, 16:05 EDT and the access token lasts for 3600 seconds, the token would expire on Oct 21, 17:05 EDT.
  • Then, before every DFP API call, check when the access token will expire before using it: if it is going to expire within a certain time window (say, in the next 60 seconds), you should refresh it before making the API call.
    • To calculate this, subtract the current time from the token’s expiration time that you calculated above.
You can see an example of how this is done in our Java client library and use it as a reference to help you implement the above.

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)



Upcoming change to AdWords Display ad groups with no targeting options specified

2016-11-10T07:58:56.030-08:00

Historically, ad groups in Display campaigns have not served until you added at least one positive ad group targeting criterion, such as Placement or CriterionUserList. This behavior worked well if your goal was to target specific criteria on Display, but not if your goal was to target as broad an audience as possible. What's changingStarting January 11, 2017, a Display ad group will be eligible to serve ads as soon as its status is set to ENABLED and it has a bid, a budget, and an approved ad. If the ad group does not have any ad group level positive targeting criteria, then the ad group will target the entire Display network, subject to exclusions and campaign-level targeting settings (such as geo, language, etc.), with the potential to quickly exhaust your campaign budget. This change only impacts campaigns with AdvertisingChannelType of DISPLAY or VIDEO. Before this feature is enabled on your account, any existing Display ad groups without ad group level positive targeting criteria will be set to PAUSED. What you should doFor existing Display campaigns and ad groups: If you want to target the entire Display network (subject to exclusions and campaign-level targeting settings), then after the feature is enabled, make sure you set those ad groups to ENABLED, since they will be in the PAUSED state. Otherwise, add the desired positive targeting criteria to each ad group, and then set it to ENABLED. For new Display campaigns and ad groups, review your application's ad group creation workflow to ensure that it does the following: Sets the AdGroup status field to PAUSED when creating a new ad group via AdGroupService.mutate and an ADD operation. Only sets the AdGroup status to ENABLED after adding targeting criteria (if desired). You can update the status of your AdGroup via AdGroupService.mutate and a SET operation. In addition, if your application adds and removes targeting criteria from existing Display ad groups, make sure that it will also properly update the the ad group's status to PAUSED or ENABLED if the intended side-effect of criterion addition or removal is to pause or start serving. This is particularly important when removing the only positive criterion for an ad group, since this will change its reach from very narrow to very broad. If you have any questions, please post on the forum or the Ads Developers Plus Page. - Josh Radcliff, AdWords API Team[...]



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

2016-11-08T11:58:05.060-08:00

Today we're releasing v2.7 of the DCM/DFA Reporting and Trafficking API. This release introduces a number of video trafficking workflow enhancements, including:

Details of these and other improvements are covered in our release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.6, which will sunset on May 31st, 2017. After this date, any requests made against v2.6 will begin returning errors.

As a final reminder, API v2.4 will be sunset on November 30th, 2016. To avoid an interruption in service, all users are required to migrate off of this version 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!

(image)




Need help upgrading to expanded text ads?

2016-11-07T07:30:13.156-08:00

In an earlier blog post, we announced that you have until January 31, 2017 to upgrade from standard text ads to expanded text ads. You will no longer be able to create new standard text ads starting on January 31st even though those ads will continue to serve.

Many of you have already taken advantage of the new ad format, but there are some developers who are still creating new standard text ads. If you need help upgrading to expanded text ads or if you have any questions, please add to this forum post or start a new forum post. Let us help you get these ads upgraded!
(image)