7-22-2015 3pm PST
New guide for setting up AdWords API authorization using the OAuth 2.0 Playground by JoshRadcliffe, AdWords API Team
Article from Google Ads Developer Blog
link to artice
http://googleadsdeveloper.blogspot.com/
New guide for setting up AdWords API authorization using the OAuth 2.0 Playground
Posted: Wednesday, July 22, 2015
For those of you who’d prefer to generate an OAuth refresh token using only a browser, there's a new guide on how to use the OAuth 2.0 Playground:
https://developers.google.com/adwords/api/docs/guides/oauth_playground
The guide walks you through the authorization setup required by the AdWords API for a Web application--via a browser session--without the need to execute any command-line scripts.
More OAuth resources
OAuth 2.0 Authentication for the AdWords API
Using OAuth 2.0 to Access Google APIs
Still have questions? Feel free to visit us on the AdWords API Forum or our Google+ page.
- Josh Radcliff, AdWords API Team
Labels: adwords_api, oauth
FeedMappings for location targeting available via the AdWords API
Posted: Wednesday, July 15, 2015
What's changing?
Starting on or after July 23, 2015, if you are using v201506 of the AdWords API, then FeedMappingService.get and FeedMappingService.query will return FeedMapping objects created for location targeting. These FeedMapping objects will have criterionType 77, and will not have a value for placeholderType. There will be no change in behavior for v201409 or v201502.
You will start seeing these objects if either of the following is true:
You created a Feed linked to your Google My Business account.
You created a Location targeting feed through the AdWords user interface, under Shared library -> Business data.
Why the change?
Starting with v201506, LocationGroups.feedId is required if your matching function includes a LocationExtensionOperand.
Specifying a feedId in this situation allows AdWords to target the areas surrounding the locations in a location targeting feed. This may be the same feed you are using for location extensions, or a separate feed containing additional locations you want to use strictly for targeting. The key point is that the Feed referenced by LocationGroups.feedId must have a FeedMapping with criterionType 77.
What should you do?
If your application retrieves FeedMapping objects, make sure it will properly handle objects where placeholderType is null and criterionType is set.
If you want to create LocationGroups objects that use a LocationExtensionOperand, you can now use FeedMappingService to find the ID of feeds that have a FeedMapping with criterionType 77.
Learn more
Check out the following resources for more information on Location Groups:
The updated placeholders documentation describes the required fields for a location targeting feed.
The AddCampaignTargetingCriteria example in the targeting folder of each client library shows how to set up a LocationGroups object using the ID of your location targeting feed.
The AdWords Help Center has an overview of using Location Groups.
Still have questions? Feel free to visit us on the AdWords API Forum or our Google+ page.
- Josh Radcliff, AdWords API Team
Labels: adwords_api, LocationExtensionOperand, LocationGroups
