| Changes to conversion counting in AdWords scripts Posted: 14 Mar 2014 11:39 AM PDT We recently announced changes to conversion counting and column names in AdWords. We are making the following changes to AdWords scripts to match the updated naming conventions: - We have deprecated the getConversions and getConversionRate methods in the Stats class. These methods will work for now, and will return the "converted clicks" and "converted click rate" values as per the new naming conventions.
- We have introduced two new methods, namely getConvertedClicks and getClickConversionRate to replace the deprecated methods. Please use these methods in your new scripts.
- We are keeping the column names unchanged in reports available through AdWordsApp.reports(). However, the meaning of values returned by these columns will reflect the new methods of counting conversions.
- The following columns refer to "converted click" columns under the new naming convention.
- Conversions
- ConversionRate
- CostPerConversion
- ValuePerConv
- ValuePerConversion
- ConversionSignificance
- ConversionRateSignificance
- CostPerConversionSignificance
- The following columns in AdWords scripts reports refer to the "conversion" columns under the new naming conventions. These columns will either return "All Conversions" or "Unique Conversions" values depending on the user preference for counting conversions. By default, this preference defaults to "All Conversions", so these reporting columns will continue returning the same values as they do today, unless the user changes this preference to "Unique Conversions".
- ConversionManyPerClick
- ConversionRateManyPerClick
- CostPerConversionManyPerClick
- ValuePerConvManyPerClick
- ValuePerConversionManyPerClick
- ConversionManyPerClickSignificance
- ConversionRateManyPerClickSignificance
- CostPerConversionManyPerClickSignificance
If you have questions or feedback about this change, let us know on our forum or via the Google Ads Developers Google+ page.  Anash P. Oommen, AdWords Scripts Team  |
| New feed-based location extensions in v201402 of AdWords API Posted: 14 Mar 2014 08:34 AM PDT As previously announced, AdWords API v201402 lets you manage your upgraded, feed-based location extensions in addition to your campaign location extensions. Upgraded location extensions are linked to your Google Places for Business account and offer significant benefits over manually entered location extensions. Most importantly, once you configure your upgraded location extensions you don't have to worry about keeping them up to date with changes in your Google Places for Business account -- AdWords does it for you! As mentioned in our detailed guide to upgraded location extensions, you can use the AdWords API to set up your extensions in a few easy steps: There are a few key differences between feeds with systemFeedGenerationData ("location feeds") and other feeds you may have created for sitelinks, app or call extensions. Type or Attribute | Location Feeds | Other Feeds | | Required
Defines the link between your AdWords and Places for Business accounts. | Not applicable | | Not applicable
AdWords maintains the feed item attribute -> placeholder field relationship for you. | Required
You maintain the feed item attribute -> placeholder field relationship. | | Automatically managed by AdWords. | | | Required | Not applicable | | Optional
Only needed if you want more control over which businesses from your Places account are used for location extensions on a particular Campaign. | Required | | Optional | Optional |
| Only needed if you want more control over which businesses from your Places account are used for location extensions on a particular AdGroup. |
|
Just as for other feed types, you can get stats for a location feed's extensions from the PLACEHOLDER_FEED_ITEM report. This is just a quick overview of the AdWords API support for upgraded location extensions. For more information, check out our feed services guide for location extensions and the accompanying code sample in each client library ( Java, Perl, PHP, Python, Ruby, .NET). Still have questions? Feel free to visit us on the AdWords API Forum or our Google+ page.  - Josh Radcliff, AdWords API Team |
No comments:
Post a Comment