Historically, some types of audiences have only been available for targeting and bidding in Display campaigns, as indicated by
UserList.isEligibleForSearch = falsein the AdWords API.
Starting at the end of September, 2016, both AdWords and the AdWords API will allow you to target additional audiences in Search and Shopping campaigns.
What you should do
- Make sure that your application does not make assumptions about which user lists are available for Search and Shopping campaigns. Instead, your application should check the value of the
isEligibleForSearchattribute of each UserList.
- You can discover the audiences in your AdWords account and their eligibility for Search, Shopping, or Display campaigns by issuing an AdwordsUserListService
queryrequest that includes the
IsEligibleForDisplayselector fields. On an ongoing basis, you should periodically check for user lists where eligibility has changed due to improvements in AdWords.
- If you'd like to add additional audience targeting to your Search or Shopping ad groups, add a BiddableAdGroupCriterion with a
criterionset to an instance of the appropriate type of UserList. Make sure that your application can handle an OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE error, which will occur if the particular
UserListin your request is not currently available for Search and Shopping campaigns.
For an overview of remarketing and audience targeting in the AdWords API, check out the Remarketing and audience targeting guide.
If you have any questions, please post on the forum or the Ads Developers Plus Page.
- Josh Radcliff, AdWords API Team
If you need help updating your script, or have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
Anash P. Oommen, AdWords Scripts Team
With the Firebase
3.6.0 launch comes the release of version 7.11.0 of the Google Mobile Ads
SDK, which has been optimized for the latest release of iOS. Any app that
supports iOS 10 should be built against v7.11.0 or higher of the Mobile Ads SDK.
AdMob publishers can grab the latest version of the SDK using the
Firebase/AdMob CocoaPod or via the Firebase manual
download. DFP publishers can get the latest version from the
Google-Mobile-Ads-SDK CocoaPod or via the Mobile Ads SDK
"This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data."
"This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSBluetoothPeripheralUsageDescription key with a string value explaining to the user how the app uses this data."
The latest version of the Mobile Ads SDK has been updated for iOS 10, and will no longer cause these errors to appear.
Information for MRAID creative designers
To comply with the App Store privacy changes, we removed support for the
mraid.storePicture() methods. You will now see that the
methods always return
false. Per the MRAID v2 spec,
MRAID creatives should check for support of these features before using them,
and correctly handle the case where they’re unavailable.
If you have any questions regarding these changes, please contact us through our forum.- Tristan Emrich, Mobile Ads Developer Relations
Starting on January 31, 2017:
- You’ll no longer be able to create standard text ads.
- The only change you'll be able to make to a standard text ad will be to update the status of its associated AdGroupAd.
- Existing standard text ads will continue to serve alongside expanded text ads.
Questions? Visit us on the AdWords API Forum or our Google+ page.
Nadine Sundquist, AdWords API Team
ExperimentServicefunctionality in existing API versions up until the final shutoff date.]
In v201603, we introduced campaign drafts and experiments to the AdWords API for Search campaigns, which is a more flexible alternative to the existing ExperimentService. Now that you can run experiments on Display campaigns as well, campaign drafts and experiments do everything the
ExperimentServicecan do and more.
As a result of this expanded functionality, the
ExperimentService will be sunset. If you’re still using the
ExperimentService, please take the time to update your code to use campaign drafts and experiments instead.
On February 1, 2017, all experiments running via the
ExperimentService will be stopped. After this date, all
ExperimentService experiments will be deleted, stats will be unavailable, and API calls to the
ExperimentService across all API versions will result in an error.
Please move off the
ExperimentService before February 1, 2017 to ensure that you are able to continue running experiments.
If you have any questions, please post on the forum.
- Mike Cloonan, AdWords API Team
Why are runtime requirements changing?On January 12th, 2016, Microsoft ended support for .NET Framework versions 4, 4.5, and 4.5.1. To ensure the continued security and stability of our client library, we will also stop supporting these legacy framework versions.
Additionally, increasing the runtime requirement allows us to make use of new framework functionality, to further improve and modernize the library.
How can you prepare?If your application currently targets .NET Framework 4.5.2+, then no action is required. Users of .NET Framework versions <= 4.5.1 will need to upgrade to 4.5.2 in advance of the November 2016 release. Users on non-Windows platforms should similarly ensure that their version of Mono supports the .NET Framework 4.5.2 target.
If you have any questions or concerns, feel free to open an issue on the client library's issue tracker.
- Jonathon Imperiosi, Ads Developer Relations Team