Google Ads Developer Blog: July 2014

Support for v201406 reports in AdWords scripts

Thursday, July 31, 2014

Change

Comments

ValuePerConvManyPerClick

Removed

Use ValuePerConversionManyPerClick instead.

ValuePerConv

Removed

Use ValuePerConversion instead.

TotalConvValue

Removed

Use ConversionValue instead.

PrimaryUserLogin

Removed

AccountId

Removed

Use ExternalCustomerId as unique account ID instead.

TargetingSetting

Removed

This column is now called IsRestrict and returns a proper boolean value.

NonDeletedAdGroupCount

Removed

New column name is NonRemovedAdGroupCount.

NonDeletedAdGroupCriteriaCount

Removed

New column name is NonRemovedAdGroupCriteriaCount.

NonDeletedCampaignCount

Removed

New column name is NonRemovedCampaignCount.

We also made changes to some enumerations for relevance and consistency:

Status value for an enabled object is now ENABLED across all reports. Before, it was ACTIVE for some objects.
Removed objects now have a status of REMOVED instead of DELETED.
The PRODUCT_LISTING_AD_CLICKS display name has changed from Offer to Product listing ad.

If your scripts use these fields in reports, make sure you fix the AWQL when migrating to the new version of the reporting API. Keep in mind that if you don’t use API versioning in your reports, then your code will now be using reports API version v201406 by default.

New report fields

Several new report fields were introduced:

Report Name	New columns
Campaign Performance Report	ServingStatus
Click Performance Report	UserListId
Product Partition Report	date fields, CampaignName, AdGroupName
Multiple reports	ExternalCustomerId, IsRestrict, BiddingStrategyType
Campaign, AdGroup, Ad, and Keyword Performance Reports	Labels

You can refer to https://developers.google.com/adwords/api/docs/appendix/reports for the list of supported reports and columns.

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

Anash P. Oommen, AdWords Scripts Team

We are announcing support for AdWords API v201406 reports in AdWords scripts. This version introduces several changes to the reporting columns.

Columns and fields cleanup

We've removed duplicates and changed column and display names in some reports:

Column Name	Change	Comments
ValuePerConvManyPerClick	Removed	Use ValuePerConversionManyPerClick instead.
ValuePerConv	Removed	Use ValuePerConversion instead.
TotalConvValue	Removed	Use ConversionValue instead.
PrimaryUserLogin	Removed
AccountId	Removed	Use ExternalCustomerId as unique account ID instead.
TargetingSetting	Removed	This column is now called IsRestrict and returns a proper boolean value.
NonDeletedAdGroupCount	Removed	New column name is NonRemovedAdGroupCount.
NonDeletedAdGroupCriteriaCount	Removed	New column name is NonRemovedAdGroupCriteriaCount.
NonDeletedCampaignCount	Removed	New column name is NonRemovedCampaignCount.

We also made changes to some enumerations for relevance and consistency:

Status value for an enabled object is now ENABLED across all reports. Before, it was ACTIVE for some objects.
Removed objects now have a status of REMOVED instead of DELETED.
The PRODUCT_LISTING_AD_CLICKS display name has changed from Offer to Product listing ad.

Report Name	New columns
Campaign Performance Report	ServingStatus
Click Performance Report	UserListId
Product Partition Report	date fields, CampaignName, AdGroupName
Multiple reports	ExternalCustomerId, IsRestrict, BiddingStrategyType
Campaign, AdGroup, Ad, and Keyword Performance Reports	Labels

Anash P. Oommen, AdWords Scripts Team

AdWords API Workshops: Feedback in Action!

Tuesday, July 29, 2014

If you’ve attended one of our AdWords API Workshops, you will know how important we think your feedback is to the growth of the API. We also have surveys you can fill in to let us know what you think. Many of the changes brought about in AdWords API v201406 were influenced by your requests, including:

Labels have been introduced to the API, for filtering and in reporting, which has been our most asked for feature for over a year now.
Destination URL customization has been improved, which along with greater Analytics functionality, improves your ability to track and manage actions from your Ads.
The Status fields of all the entities have been made more consistent. This has meant changing some enumeration fields, for instance, but the result should cause less confusion going forward.
Shared Sets are back - currently for whitelisted customers only.
Managed Customer Service can now move whole subMCC trees between MCCs.

We want to thank you again for your feedback, and ask that you continue to let us know what you need to use the API more effectively. Your input really does matter, and makes things happen.

Finally, if you want to see the content of our last AdWords API Workshops round, we’ve recorded a series of videos of the presentations we gave. We hope you find them useful and interesting.

- Mark R. Bowyer, AdWords API Team

Reminder: AdWords Migration to Search Network with Display Select

Tuesday, July 29, 2014

In April, we announced that Search Network with Display Select support would begin in AdWords API v201402. Now that all previous API versions have been sunset, we’re on schedule to begin migrating all Search and Display Network campaigns to Search Network with Display Select beginning September 16, 2014.

This blog post will walk through everything you need to know about setting up your campaigns, including what this migration means for your campaign-creation code. You can proactively migrate your campaigns by setting their displaySelect property to true.

Remember, this will not affect Search-only or Display-only campaigns. Only campaigns that target both networks simultaneously will be migrated.

If you have any questions about this change, please contact us on the forum or via our Google+ page.

- Michael Cloonan, AdWords API Team.

Real-time Bidding with OpenRTB and DoubleClick Ad Exchange

Monday, July 28, 2014

Working with multiple exchanges is a key pain point for those developing real-time bidders. To-date, individual exchanges have used their own distinct protocols requiring the time-consuming development of a separate model for each exchange. In response, the OpenRTB consortium introduced standards for communication in real-time bidding that greatly simplifies the process of adding support for new exchanges. That’s why we are pleased to announce two new open source libraries that implement the OpenRTB specification and are now available on GitHub—google/openrtb and google/openrtb-doubleclick.

The openrtb library provides support for the core OpenRTB model and was designed with extensibility in mind to support the development of libraries for other exchanges. The openrtb-doubleclick library is an extension of openrtb for DoubleClick Ad Exchange that provides interoperability between the OpenRTB model and DoubleClick's Real-Time Bidding protocol. The library also includes DoubleClick-specific utilities. In summary, these libraries provide the following:

The model - The RTB model, as seen in the OpenRTB specification.
The mapper - Translates DoubleClick’s native model to/from OpenRTB.
The serializer - Translates JSON to/from the OpenRTB model.
DoubleClick Ad Exchange utilities - Utilities to handle bid validation, DoubleClick crypto and metadata.

For more information about the OpenRTB specification, check out the documentation on their Github page.

- Mark Saniscalchi, Ad Exchange Team

Ad Exchange Real-Time Bidding Optimization Series: Video Best Practices

Wednesday, July 23, 2014

Two years ago, we introduced the Ad Exchange Real-Time Bidding Optimization Series on the developer's blog with our first post on post-filtered bids. Since then we’ve added tons of new formats and options for buying. Today, we’ll direct you to our Developers site for more information about how the video review process works, how throttling and filtering occur and highlight best practices to ensure smooth delivery.

The first step is to know your video-specific terms. Check out the in-stream video glossary to find definitions for terms with which you’re not familiar. Once you've created your in-stream video ad, you will need to monitor your video ads. The Video Best Practices Guide provides a list of ways to confirm your video ads are serving:

Have questions or feedback? Reach out to your Ad Exchange account team.

Posted by the Ad Exchange Team

AdWords API - Upgrading to account-level location extensions

Wednesday, July 23, 2014

Update: All new location extensions created on or after October 16th, 2014 can only be created as new account-level feed-based location extensions.

On July 14th, 2014, AdWords announced upgraded location extensions, a more efficient way to manage and use business locations in ads by linking Google My Business and AdWords accounts.

The upgrade is taking place in phases for AdWords accounts throughout the coming months. The next phase of account upgrades is scheduled to start on August 25, 2014. All AdWords accounts will to be upgraded by November, 2014.

The upgrade has direct impact to AdWords API client applications. If you are using the CampaignAdExtensionService to manage LocationExtensions or LocationSyncExtensions, then you’re using the legacy location extensions that are being phased out. After an account is upgraded, you’ll need to use the new account-level feed-based location extensions.

How will existing location extensions be upgraded by Google?

Please review the AdWords Help Center article for all upgrade scenarios. For AdWords API developers, most accounts will fall into one of these scenarios:

Accounts that don’t have any existing legacy location extensions.
Accounts that have existing legacy location extensions not sourced from a Google My Business account (i.e., using LocationExtensions only).
Accounts that have existing legacy location extensions sourced from a Google My Business account (i.e., using LocationSyncExtensions).

If you programmatically create AdWords accounts that are not associated with any user, please get in touch with your Google representative for migration support.

Accounts that don’t have any existing legacy location extensions

For accounts that aren’t using any LocationExtensions or LocationSyncExtensions but will begin using location extensions, you should use feed-based location extensions instead.

Accounts that have existing legacy location extensions not sourced from a Google My Business account

If you’re using LocationExtension entities to manage individual locations, the automatic upgrade process will perform the following:

A Google My Business account will be created and linked with the AdWords account. All administrators of that AdWords account will have access to locations in the linked Google My Business account.
A CustomerFeed with the Location placeholder type will be created.
Existing locations in LocationExtension entities will be copied into the Google My Business account. Existing LocationExtension entities will then be removed.
Ads in all campaigns will be served with locations from the linked Google My Business account (you can create a CampaignFeed to further filter or disable location extensions served for a given campaign).

Accounts that have existing legacy location extensions sourced from a Google My Business account

If you’re using LocationSyncExtension to link campaigns to a Google My Business account, then the automatic upgrade process will perform the following:

The campaign-level links to the Google My Business account will be switched to a single link at the account level.
- A CustomerFeed with the Location placeholder type will be created for the account.
Any existing LocationExtension entities will be removed, so make sure they’re copied to the linked Google My Business account before the upgrade.
Ads in all campaigns will be served with locations from the linked Google My Business account (you can create a CampaignFeed to further filter or disable location extensions served for a given campaign).

If an AdWords account is already linked to Google My Business at the account level using CustomerFeed, any existing legacy location extensions will be removed during the upgrade process.

How do I know if an account has been upgraded?

An account is considered upgraded if either condition is true:

It has a CustomerFeed for the Location placeholder type. You can query CustomerFeedService to check:
```
select FeedId, PlaceholderTypes where PlaceholderTypes = 7
```
It has neither a CustomerFeed nor legacy LocationExtension or LocationSyncExtension entities.

In an upgraded account, any attempts to create legacy location extensions using the CampaignAdExtensionsService will return the AdExtensionError.INVALID_ADEXTENSION_TYPE error.

How do I continue to manage locations?

There’s currently no API support for Google My Business. Locations are managed via the Google My Business Locations interface, which supports bulk management.

Can I start using upgraded location extensions before an account is upgraded?

Since the upgrade process is complicated for many accounts, the simplest approach is to allow accounts using legacy location extensions to be automatically upgraded (account owners will be notified 30 days before the upgrade).

What about reporting?

For upgraded accounts, you’ll need to use the Placeholder Feed Item Report rather than the Ad Extensions Performance Report to download statistics for each location.

We are here to help

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the AdWords API forum or via the Google Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Google Media Framework: Making online video simple

Wednesday, July 23, 2014

Google Media Framework for Android

GMF Features

Ready to use Video player for your apps and websites
Demo apps include production ready integrations with the IMA ads SDK
GMF is free and open source, so can be customized to meet your specific needs (Send us a pull request!)
Easily customize the UI color and add or remove buttons
Support for iOS 7+ and Android 4.1+

We hope these frameworks enable you to simply make great mobile video apps and awesome web video experiences. You can send us thoughts or questions via the GMF Google group.

GitHub Links

Stay tuned as well for a deeper dive into Video.js with IMA soon!

-- The Google Media Framework Team

We’re excited to announce an open source video player framework to make online video and video monetization with the IMA SDK easier than ever. The Google Media Framework (GMF) is available for iOS and Android, and we have a Video.js plugin for web based video players.

Google Media Framework for iOS

Google Media Framework for Android

GMF Features

Ready to use Video player for your apps and websites
Demo apps include production ready integrations with the IMA ads SDK
GMF is free and open source, so can be customized to meet your specific needs (Send us a pull request!)
Easily customize the UI color and add or remove buttons
Support for iOS 7+ and Android 4.1+

We hope these frameworks enable you to simply make great mobile video apps and awesome web video experiences. You can send us thoughts or questions via the GMF Google group.

GitHub Links

Stay tuned as well for a deeper dive into Video.js with IMA soon!

-- The Google Media Framework Team

Preserving and renewing your AdWords scripts

Monday, July 21, 2014

To help streamline management of your AdWords scripts, we’ve made it easier to preserve scripts created in your AdWords account even after the original author becomes inactive.

In the past, a script in an AdWords account would become unavailable if the script’s original author was no longer associated with the AdWords account. Other users on the AdWords account would need to recreate the script on their own or else risk losing it entirely.

With the new changes we’re launching, scripts from an inactive user will continue to be available in the AdWords account where they were created. To keep these scripts running, the remaining users in the AdWords account will need to log into AdWords and reauthorize the script.

We’ll e-mail the administrators on the AdWords account if the author of a scheduled script goes inactive and here’s what you’ll need to do to get the script running again:

Log in to your AdWords account, and navigate to the Scripts section under Bulk Operations (or the Scripts section of your MCC account).
In the “Script” column, find the relevant script.
Click the "Edit" link.
Click the "Authorize now" button in the yellow bar at the top of the script editor.
Click the “Accept” button.

We are applying this change with an effective date of March 15, 2014. If an author went inactive before that date, his or her scripts will continue to be unavailable. Scripts created in your AdWords account after March 15 will remain available as long as the AdWords account remains open.

Anash P. Oommen, AdWords Scripts Team

Generating the Snippet Status Report with Ad Exchange Buyer REST API

Friday, July 18, 2014

If you are running DoubleClick Ad Exchange Real-Time Bidding campaigns, you can now use the Snippet Status Report Generator to obtain a Snippet Status Report for your creatives. The Snippet Status Report contains the approval status of your creatives, as well as the sensitive and product categorization that Ad Exchange automatically detects. The Snippet Status Report Generator produces reports using the Ad Exchange Buyer REST API.

There are three versions of this report available through the generator: a human readable text format, a binary protocol buffer format, and a spreadsheet-friendly CSV format. The text and protocol buffer version of the report can also be obtained via Google Cloud Storage. The CSV version can be used with spreadsheet programs such as Google Sheets, Microsoft Excel or LibreOffice Calc:

The Snippet Status Report Generator is available on GitHub as a python program. You are encouraged to download it and make modifications to generate reports in your desired format.

If you have any questions or feature requests for the Snippet Status Report Generator, please create an issue on the project’s issues page.

For any questions about the Ad Exchange Buyer API, visit us on the forum or our Google+ page.

- John Qin, Ad Exchange RTB API team

Deprecating PHP 5.2 support for the Ads PHP Client Library

Thursday, July 17, 2014

Starting January 1st, 2015, the PHP Ads client library will stop supporting PHP 5.2:

We will no longer test against PHP 5.2, or fix bugs that only affect PHP 5.2 users
Newer versions of the library may not work with PHP 5.2

This will impact PHP client library users of the AdWords API, the DoubleClick for Publishers API, and the DoubleClick Ad Exchange Buyer APIs.

PHP 5.2 hasn’t been supported since 2011 and should be upgraded to a current, stable version. Upgrading ensures you’ll receive the latest security updates.

In addition, there are numerous issues when using the PHP 5.2 SOAP client, such as:

No support for chunked encoding
Inability to set HTTP protocol version
Inability to set custom HTTP headers

In particular, custom HTTP headers are required for the DoubleClick for Publishers API starting from DoubleClick for Publishers API v201405 - the OAuth 2.0 access token must be passed via the HTTP headers rather than the URL parameter. In this case, PHP 5.2 users must upgrade in order to use DoubleClick for Publishers API v201405.

As always, if you have any questions, drop us a line on the forums (AdWords API, DoubleClick for Publishers API, DoubleClick Ad Exchange Buyer API) or Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

AdWords - Meaningful Return Values

Tuesday, July 15, 2014

We are always striving to make sure the data you fetch from the AdWords API is as meaningful as possible, and in v201406 we've made a few changes to some return values that should be more intuitive.

First, in the TrafficEstimatorService, we used to return 0 for values which we couldn't calculate, for example if a field requires division by zero. However, this could’ve given the false impression that the actual value was 0, rather than that it couldn't be calculated. For this reason, we’ve changed the logic to return null in cases where the value couldn't be calculated at all. This affects the averageCpc and averagePosition fields in StatsEstimate, as these values will not be returned in SOAP responses when they can’t be calculated.

Second, when using the Keyword Performance Report, we formerly returned all negative keywords as having a "pending review" approval status. Since negative keywords don't need to go through the same process as normal keywords, we will now return a null value instead for the ApprovalStatus field for all negative keywords.

This change only affects version v201406 going forward, and doesn’t affect existing versions v201402 or v201309.

As always, we are constantly looking to improve the API. If you have any questions about this or other API features, please feel free to ask on the forum or on our Google+ page.

- Michael Cloonan, AdWords API Team

Changes to Ads API .NET client library

Tuesday, July 15, 2014

We have made a few changes to the Ads API .NET client library to allow better maintenance and support.

Unified repository

For ease of maintenance and to reduce duplication, we have combined the AdWords, AdXBuyer, DFP and DFA API .NET libraries into one repository: https://github.com/googleads/googleads-dotnet-lib

Going forward, please use the new repository for downloading Ads API .NET client library releases, reporting issues, requesting features, and providing source contributions.

We have updated wiki articles, consolidated open issues, and imported source code of past releases.

New runtime requirement

We have increased the runtime requirement for the client library to Microsoft .NET Framework 4. This upgrade allows us to enhance the library using features available in newer versions of the Microsoft .NET framework, while moving away from .NET 2.0, which is past its mainstream support period.

In case you are still using Microsoft .NET Framework 2.0, you may continue using the legacy library until July 1st, 2015, at which time we will stop providing bug fixes and enhancements to the library. Major feature enhancements and support of newer versions of the APIs will be limited to the newer library that uses Microsoft .NET Framework 4.

Updates to version numbers

We have updated the version number of the Ads API .NET client library to 18.0.0. The Common library version has been updated to 3.0.0. Going forward, all the API-specific client library assemblies will share a single version number, while the Common library will continue to maintain its own version number.

The legacy library assemblies will only have minor releases, and will use the following versioning scheme on both Github and Nuget:

Google.Ads.Common: 2.x
Google.AdWords: 17.x
Google.Dfp: 7.x
Google.Dfa: 5.x

If you have questions or feedback, let us know on our forum or our Google+ page.

Anash P. Oommen, Ads Developer Relations

A day in the life of a mobile line item (part 1)

Friday, July 11, 2014

Imagine for a moment that you're a mobile line item. You've just been initialized locally, and all of a sudden you’re having an existential crisis -- what makes you, you? How are you different from all the other line items? Sure your associated creative might be a bit different from other line items and you might have a few extra impressions allotted to your goal, but what truly makes you... unique? In this series of posts, we'll take you on an incredible journey through a day in the life of a mobile line item -- from how to target mobile to the actual delivery on a device.

Adding mobile specific targeting
It all starts similarly enough: you need a name, an order ID, start and end dates, a goal, and all the usual suspects -- but wait, there's more! Instead of just having custom criteria, ad units, and geo-targeting, you find that you also have TechnologyTargeting fields specified, like:

DeviceCategoryTargeting
OperatingSystemTargeting
MobileCarrierTargeting
Now, say you're being created as a line item to advertise Android tablet cases. It doesn't make much sense for you to be delivered to an iPad or an iPhone, so we need to add technology specific targeting.
To do so using Java, we would first set the DeviceCategory object with the targeting ID of the 'Tablet' category and the OperatingSystem object with the targeting ID of 'Android', both of which we'd pull from the PublisherQueryLanguage service:
`DeviceCategory deviceCategory = new DeviceCategory(); OperatingSystem operatingSystem = new OperatingSystem(); deviceCategory.setId(30002L); operatingSystem.setId(501013L); These would then be set on the DeviceCategoryTargeting and OperatingSystemTargeting objects:`DeviceCategoryTargeting deviceCategoryTargeting = new DeviceCategoryTargeting(); OperatingSystemTargeting operatingSystemTargeting = new OperatingSystemTargeting(); deviceCategoryTargeting.setTargetedDeviceCategories(new DeviceCategory[] {deviceCategory}); operatingSystemTargeting.setOperatingSystems(new OperatingSystem[] {operatingSystem}); Finally, the Targeting object will have a TechnologyTargeting object set for DeviceCategoryTargeting and also OperatingSystemTargeting: TechnologyTargeting techTargeting = new TechnologyTargeting(); technologyTargeting.setDeviceCategoryTargeting(deviceCategoryTargeting); technologyTargeting.setOperatingSystemTargeting(operatingSystemTargeting); Targeting targeting = new Targeting(); targeting.setTechnologyTargeting(techTargeting); Now what happens? You're a line item that has a bit of technology targeting specified, but where are you off to next? Stay tuned for what happens next in - 'A day in the life of a mobile line item, part 2.' - Nicholas Chen, DFP API Team





New OAuth 2.0 Scope for the AdWords API





Thursday, July 10, 2014







    

                        














                        Google
                      


Labels:



adwords_api


                                ,
                              

oauth2








New labels features in AdWords API v201406





Thursday, July 10, 2014







    

                        














                        Google
                      


Labels:



adwords_api


                                ,
                              

adwords_api_v201406


                                ,
                              

labels


                                ,
                              

reporting








Announcing v201406 of the AdWords API





Wednesday, July 9, 2014








If you're still using v201309 of the AdWords API, please note that it's being sunset on July 21st, 2014. We encourage you to skip v201402 and migrate straight to v201406. If you're using v201402, be aware it's now marked deprecated and will be sunset on November 6th, 2014.



As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201406 migration guide. The updated client libraries and code examples will be published shortly. With this release, we've also updated the Required Minimum Functionality document to include some of the newly added features that are now required in third-party tools. If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page.



 - Danial Klimkin on behalf of AdWords API Team.




    

                        














                        Google
                      


Labels:



adwords_api


                                ,
                              

adwords_api_v201406








Changes to Pretargeting for Ad Exchange Buyer RTB Campaigns





Tuesday, July 8, 2014







    

                        














                        Google
                      


Labels:



ad_exchange


                                ,
                              

ad_exchange_rest


                                ,
                              

ad_exchange_rtb


                                ,
                              

ad_exchange_soap








Line item duration issues in the DFP API v201405





Wednesday, July 2, 2014







 - Vincent Tsao, DFP API Team



    

                        














                        Google
                      


Labels:



dfp_api








New AdWords API guides





Wednesday, July 2, 2014







 - Danial Klimkin, AdWords API Team.



    

                        














                        Google
                      


Labels:



adwords_api


                                ,
                              

analytics


                                ,
                              

dsa


                                ,
                              

optimization








AdWords and DoubleClick Ad Exchange API users - Only 3 weeks left to migrate from ClientLogin to OAuth 2.0!





Tuesday, July 1, 2014







    

                        














                        Google
                      


Labels:



adwords_api


                                ,
                              

oauth


                                ,
                              

oauth2


                                ,
                              

sunset








                      
                    




                          
                        





                          
                        





















Labels


                      
                    





account_management




ad_clicks




ad_customizers




ad_exchange




ad_exchange_buyer




ad_exchange_optimization-series




ad_exchange_rest




ad_exchange_rtb




ad_exchange_seller




ad_exchange_soap




ad_extensions




ad_inspector




ad_manager




ad_manager_api




ad_manager_api_v201805




ad_manager_api_v201808




ad_manager_api_v201811




ad_manager_api_v201902




ad_manager_api_v201905




ad_manager_api_v201908




ad_manager_api_v201911




ad_manager_api_v202002




ad_manager_api_v202005




ad_manager_api_v202008




ad_manager_api_v202011




ad_manager_api_v202102




ad_manager_api_v202105




ad_manager_api_v202108




ad_manager_api_v202111




ad_manager_api_v202202




ad_manager_api_v202205




ad_manager_api_v202208




ad_manager_api_v202211




ad_manager_api_v202302




ad_manager_api_v202305




ad_manager_api_v202308




ad_manager_api_v202311




ad_manager_api_v202402




ad_manager_api_v202405




ad_manager_api_v202408




ad_manager_api_v202411




ad_param




ad_speed




adexchangebuyer




AdGroup




AdGroupAd




admanager_api




admob




admob_api




admob_api_v1




admob_mediation




admob_sdk




admob_v4.3.1




admob_v5.0.5




admob_v6.0.1




ads




adsense




adsense_api




adsense_host_api




adsense_host_api_v3




adsense_management_api




adsense_management_api_v1




adsense_management_api_v1.1




adsense_management_api_v1.2




adsense_management_api_v1.3




adsense_management_api_v1.4




advanced_apis




adwhirl




adwhirl_v3.1.1




adwords




AdWords Scripts




adwords_AdGroupCriterionService




adwords_api




adwords_api_v201302




adwords_api_v201306




adwords_api_v201309




adwords_api_v201402




adwords_api_v201406




adwords_api_v201409




adwords_api_v201502




adwords_api_v201506




adwords_api_v201509




adwords_api_v201601




adwords_api_v201603




adwords_api_v201605




adwords_api_v201607




adwords_api_v201609




adwords_api_v201702




adwords_api_v201705




adwords_api_v201708




adwords_api_v201710




adwords_api_v201802




adwords_api_v201806




adwords_api_v201809




adwords_api_workshops




adwords_BatchJobService




adwords_CampaignService




adwords_CreateAccountService




adwords_for_video




adwords_ManagedCustomerService




adwords_MutateJobService




adwords_ReportDefinitionService




adwords_scripts




adwords_v201109




adwords_v201206




adwords_v201209




adwords_v201302




adwords_v201306




adwords_v201309




adwords_v201601




adwords_v201605




adwords_v201607




adwords_v201609




adwords_v201702




adwords_v201802




adwords_v201806




adwords_v201809




alerting




amp




analytics




analyticsapi




android




android_layout




animation




announcement




annual developer survey




api




app_engine




asset_group




asset_group_listing_group_filter




asset_group_signal




assets




attribution_reporting_api




audiences




authentication




authorization




authorized_buyer




authorized_buyers




aw_reporting




awql




batch_processing




beacon_api




best_practices




beta




bid_manager_api




bid_modifiers




bidding




billing




budget_order_service




budgets




builders




bulk_upload




c#




caf_sdk




call_extensions




call_metrics




call_only




call_tracking




call-only




callout_extensions




campaign




CampaignCriterion




case_study




cast




certificates




certification




chart_tools




chrome




chromecast




click




click_tracking




click_type




click-to-download




clicks




client_libraries




client_library




cm360




code_examples




common_questions




conference




content




content_api




conversion




conversions




ConversionTrackerService




converted_clicks




creative_platforms




creatives




custom_fields




DAI




dart




dbm_api




debugging




decorators




deprecation




developer




dfa_ad_service




dfa_api




dfa_api_v118




dfa_creative_service




dfa_reporting_api




dfa_site_service




dfa_v1.16




dfa_v1.17




dfa_v1.18




dfa_v1.19




dfa_v1.20




dfp




dfp_api




dfp_appengine




dfp_creatives




dfp_inventory




dfp_mobile




dfp_pql




dfp_reports




dfp_sales




dfp_teams




dfp_v201111




dfp_v201201




dfp_v201203




dfp_v201204




dfp_v201206




dfp_v201208




dfp_v201211




dfp_v201302




dfp_v201308




dfp_v201608




dfp_v201711




display




display_network




display_select




display_smart_campaign




docs




dotnet




doubleclick




DoubleClick_Rich_Media




doubleclick_studio




drafts




dsa




dv360




dv360_api




dynamic_creative




enhanced_campaigns




entity_read_files




erf




error handling




eta




examples




excluded_placement_lists




exoplayer




expanded_text_ads




experiment




experiments




faq




feedback




feeds




firebase




flash




flash_sdk




floc




forecast_service




games




gaql




gclid




gdc




gdl




geo_targets




geotargeting




gmail_ads




gmail_image_ads




gmail_multi_product_ads




gmail_single_promotion_ads




GMF




gmp




golang




google_ads




google_ads_api




google_ads_api_migration_workshop




google_ads_api_v0




google_ads_api_v0_1




google_ads_api_v0_3




google_ads_api_v0_4




google_ads_api_v0_5




google_ads_api_v0_6




google_ads_api_v0_7




google_ads_api_v1_0




google_ads_api_v1_1




google_ads_api_v1_2




google_ads_api_v1_3




google_ads_api_v2_1




google_ads_api_v3_0




google_ads_api_v3_1




google_ads_api_v4




google_ads_api_v5




google_ads_api_v6




google_ads_scripts




google_ads_solutions




google_apis




google_apps_script




google_drive




google_play_services




google_plus




gpt




guide




guides




hangout




hotel_ads




hotel_campaigns




html5




html5_ads




https




i18n




ids




ima_android




ima_flash




ima_html5




ima_ios




ima_sdk




image




image_ads




implementation




impression_share




interstitial




interview




io13




iOS




iOS9




java_app_engine




java_dart_api




jdbc




keyword_optimizer




keywords




kotlin




labels




limits




line_item




linq




listing_groups




location_extensions




location_feeds




LocationExtensionOperand




LocationGroups




logging




manager_accounts




maps_api




marketplace




maximize




mcc




media




media_bundle




mediation_test_suite




merchant_api




migration




mobile




mobile_ads




mobile_ads_garage




mobile_ads_sdk




mobile_sites




mobile_speed




mobile_targeting




mobile_ux




monitoring




native




native_ads_express




new_features




oauth




oauth2




offline_conversions




OfflineConversionFeedService




open_source




openrtb




optimization




Performance Max




performance_max




performance_max_api_workshop




php




PLA




placements




PMax




policy




policy_violation




PQL




price_extension




privacy




privacy_sandbox




product_listing_ads




proguard




promotion_line




publisher_ads_audits




python




qa




quality_score




query_builder_blog_series




query_language




quota




rate_limiter




rate_sheet




RateExceededError




realtime_bidding




realtime_bidding_api




realtime_bidding_protocol




realtimebidding




recommendations




referer




release




remarketing




reporting




reports




responsive_ads




rewarded_video




rmf




ruby




sa360




sandbox




scripts




sdf




sdkless




search




search audience




search terms




search_audience




search_network




search_theme




selector




sendbeacon




service_accounts




shared_negative_keywords




shopping




simulations




sitelinks




smart




snds




spend




ssl




StepInsideAdWords




success_stories




suggested_ad_units




sunset




survey




swift




swiftui




target




target_cpa




targeting




template_ads




terms




test_accounts




test_network




testing




text_ads




text_asset_automation




tools




trials




turtledove




ui




unity




update




updates




upgrade




upgraded_urls




v201509




vast3




vcpm




video




viewable-cpm




webinar




workshop




workshops




wp8




xml




youtube








                      
                    

Archive


                      
                    









                    
                  




                        
                      
                       
                    



2024







Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2023







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2022







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2021







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2020







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2019







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2018







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2017







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2016







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2015







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                      



2014







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2013







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2012







Dec










Nov










Oct










Sep










Aug










Jul










Jun










May










Apr










Mar










Feb










Jan














                    
                  




                        
                      
                       
                    



2011







Dec










Nov

















  






Give us feedback in our developer product forums:


Google Ads API

Google Ads scripts

Google Ad Manager API

DCM API

Google Mobile Ads SDK

Google AdMob API

Google Interactive Media Ads SDK

Google Content API for Shopping

Authorized Buyers API

















              Google
            



              Privacy
            



              Terms