Google Ads Developer Blog: נובמבר 2017

AdWords scripts now supports v201708 and v201710 in reports

יום רביעי, 29 בנובמבר 2017

We have added support for AdWords API v201708 and v201710 reports in AdWords scripts.

The major changes in v201708 are:

New fields in various report types.
The TABLE_EXTENSION enum value for ClickType was renamed to PRICE_EXTENSION.
See the full AdWords API release notes for more details.

The major changes in v201710 are:

The Automated field was added to the AD_PERFORMANCE_REPORT.
The EnhancedCpvEnabled field was removed from all reports.
See the full AdWords API release notes for more details.

In addition to these changes, v201705 is now the default version for reports. You can use one of the newly supported versions instead by specifying the apiVersion in your report request:

var report = AdWordsApp.report(query, {
    apiVersion: 'v201710'
});

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

- Mike Cloonan, AdWords API Team.

Announcing v3.0 of the DCM/DFA Reporting and Trafficking API

יום חמישי, 16 בנובמבר 2017

Today we're releasing v3.0 of the DCM/DFA Reporting and Trafficking API. Highlights of this major version release include:

Advertiser landing pages
Creative polite load and placement video orientation options
Support for global site tags

Although we strive to maintain backwards compatibility between releases, a number of enhancements in this release necessitated breaking changes to existing API workflows. Details of these and all other changes 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.8, which will sunset on August 31st, 2018. After this date, any requests made against v2.8 will begin returning errors.

As a final reminder, API version 2.7 will be sunset on December 7th, 2017. To avoid an interruption in service, all users are required to migrate to a newer version before 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!

- Jonathon Imperiosi, DCM API Team

Announcing v201711 of the DFP API

יום שלישי, 14 בנובמבר 2017

Today we're pleased to announce several additions and improvements to the DFP API with the release of v201711. This release includes a new service, CdnConfigurationService, which manages the configuration of DAI (Dynamic Ad Insertion) content ingestion and delivery networks. Please note that Ad Exchange historical reports will be run in the Pacific timezone in v201711. This will allow you to report on Bid and Deals metrics. If you need to continue running Ad Exchange historical reports in your network timezone, please stay on v201708. Future versions will support both options. Additionally, the release adds the ability to generate in-site preview URLs for native styles, and you can now determine if an AdUnit supports fluid sizes by looking at the new isFluid attribute. For a full list of API changes in v201711, see the release notes. With each new release comes a deprecation. If you're using v201611 or earlier, it's time to look into upgrading. Also remember that v201702 will be sunset at the end of February 2018. As always, if you have any questions, feel free to drop us a line on the DFP API forum.

- Gabe Rives-Corbett, DFP API Team

Changes to AdWords Express campaigns in AdWords API reports

יום שישי, 10 בנובמבר 2017

If you use AdWords API reports to retrieve performance statistics for AdWords Express campaigns, please read on as these changes will affect you.

What's changing?
In preparation for upcoming improvements, an ongoing migration process is modifying campaigns managed by AdWords Express.

Currently, when you enable an AdWords Express promotion, it creates up to two AdWords campaigns:

A Search Network campaign with:
- AdvertisingChannelType = SEARCH (appears as Search)
- AdvertisingChannelSubType = SEARCH_EXPRESS (appears as Search Express)
A Display Network campaign with:
- AdvertisingChannelType = DISPLAY (appears as Display)
- AdvertisingChannelSubType = DISPLAY_EXPRESS (appears as Display Express)

As part of the migration, the two campaigns above will be paused and replaced by a single AdWords campaign with:

AdvertisingChannelType = EXPRESS (appears as Express)
AdvertisingChannelSubType = UNKNOWN (appears as an empty string)

After the campaigns for a promotion are migrated, performance statistics for the AdWords Express promotion will be available in reports as follows:

Performance statistics for dates prior to the migration will be attributed to the original campaigns with SEARCH / SEARCH_EXPRESS and DISPLAY / DISPLAY_EXPRESS.
Performance statistics for dates after the migration will be attributed to the new campaign with EXPRESS / UNKNOWN. The new campaign will only appear in the CAMPAIGN_PERFORMANCE_REPORT.

For example, assume an AdWords Express promotion manages the following two AdWords campaigns today:

Campaign ID	Campaign Status	Advertising Channel Type	Advertising Channel Sub Type
1000	ENABLED	SEARCH	SEARCH_EXPRESS
2000	ENABLED	DISPLAY	DISPLAY_EXPRESS

After the migration, the account will contain the following campaigns for the AdWords Express promotion:

Campaign ID	Campaign Status	Advertising Channel Type	Advertising Channel Sub Type	Performance statistics
1000	PAUSED	SEARCH	SEARCH_EXPRESS	Before the migration
2000	PAUSED	DISPLAY	DISPLAY_EXPRESS	Before the migration
3000	ENABLED	EXPRESS	UNKNOWN	After the migration

What should you do?
Ensure that your application properly handles all three combinations of AdvertisingChannelType and AdvertisingChannelSubType. For example:

If your application inspects AdvertisingChannelType or AdvertisingChannelSubType to handle AdWords Express campaigns, please adjust the logic to handle the new combination of EXPRESS / UNKNOWN.
If you use predicates on AdvertisingChannelType or AdvertisingChannelSubType to include or exclude AdWords Express campaigns, make sure that your predicate takes the new combination into account.

Reminder: The AdWords API only supports retrieving AdWords Express entities. You cannot modify AdWords Express entities in your account using the AdWords API.

If you have any questions about this change, please contact us via the forum.

- Josh Radcliff, AdWords API Team

DCM/DFA Reporting and Trafficking API v2.7 sunset reminder

יום רביעי, 8 בנובמבר 2017

DCM/DFA Reporting and Trafficking API v2.7 will be sunset on December 7th, 2017. From this date onwards, all requests made against v2.7 of this API will fail. If you're still actively working with this version, we strongly encourage you to begin migrating to the most current release to avoid an interruption in service.

For most, migrating will be as easy as adopting the latest version of your preferred client library. However, all users are advised to review the release notes to learn about important version differences you may need to be aware of.

If you have questions about this or anything else DCM API related, feel free to reach out to us on our support forum.

- Jonathon Imperiosi, DCM API Team

Search impression share data will be updated more frequently

יום שלישי, 7 בנובמבר 2017

Starting mid-November, we’ll be updating AdWords API impression share reporting data more frequently. As a result, you'll be able to get the previous day's data by 12 PM (your local time). Previously, you might have had to wait up to 48 hours for the previous day’s data. This change affects the following reporting fields:

SearchBudgetLostImpressionShare
SearchExactMatchImpressionShare
SearchImpressionShare
SearchRankLostImpressionShare

With this change, you may see data fluctuate for report definitions that contain any of the above fields along with one of the following date ranges:

YESTERDAY, TODAY, LAST_7_DAYS, THIS_MONTH, ALL_TIME, LAST_14_DAYS, LAST_30_DAYS, THIS_WEEK_SUN_TODAY, THIS_WEEK_MON_TODAY
CUSTOM_DATE that includes the current date or the day before the day when you make a report request

This change allows for more real-time monitoring of search impression share. If you prefer to see more stable values, make sure the date range in your request doesn’t include the current date or yesterday if it’s not yet 12 PM in your time zone.

As always, if you have any questions, please post on the forum.

- Thanet Praneenararat, AdWords API Team

Ads Developer Blog