Google Ads Developer Blog: dfa

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

Friday, July 31, 2020

- Nikita Agarwal, DCM API Team

Update (Sep 1, 2020): Support for path and path attribution report types is now available in v3.4. It has been added back to this post.

Update (Aug 7, 2020): Support for path and path attribution report types, originally listed in this blog post, was not included in the initial release of v3.4 of the DCM/DFA Reporting and Trafficking API. It has been removed from this post.

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

Support for path and path attribution report types.
Added site-level and placement-level OBA icon settings for video creative settings.
Support for attribution in floodlight activities, and a new status field.

Details of these and 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 v3.3, which will sunset on February 28, 2021. After this date, any requests made against v3.3 will begin returning errors.

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!

- Nikita Agarwal, DCM API Team

Stricter Validation For DCM/DFA Reporting and Trafficking API

Thursday, July 9, 2020

The following list includes the error codes that you might see, as well as the recommended solutions:

"Invalid value - Enum" - Ensure you are using valid enum values. For more information, see the API Reference.
"Invalid value - Bool" - Ensure boolean fields in the request are set to true/false, rather than empty string.
"Invalid value - Integer ####.0" - Ensure integer fields in the request are set to valid integers.
"Invalid JSON Payload - NaN" - Ensure NaN does not appear in the request payload.
"Invalid JSON payload received. - not repeating" - Do not use arrays for non-array fields.

Method specific errors:

dfareporting.reports.run: "Invalid JSON payload received. Unexpected end of string. Expected a value" - Ensure the request body is completely empty.
dfareporting.reports.list: "Request contains an invalid argument." - Ensure that empty fields in the response contain a valid value. For example, empty array fields must be specified by an empty array, rather than an empty string or object.
dfareporting.files.get and dfareporting.reports.files.get: "OAuth token was passed in the query parameter. Please send it in Authorization header instead." - Requests must use the HTTP header Authorization: Bearer [ACCESS_TOKEN] to pass OAuth credentials.

Why is this changing?
Stricter validation helps ensure that problematic requests are not silently ignored, and aligns the behavior of the DCM API with that of other Google APIs.

- Evan Chou, DCM API Team

On July 14th, 2020, we will begin enforcing stricter validation for requests to the DCM/DFA Reporting and Trafficking API. This change will initially be introduced for 5% of API traffic during the week of July 14, 10% the week of July 21, 30% the week of July 28, and all requests by August 7th, 2020.

As a result, your requests might begin returning additional errors. Please update your requests, as needed.

The following list includes the error codes that you might see, as well as the recommended solutions:

"Invalid value - Enum" - Ensure you are using valid enum values. For more information, see the API Reference.
"Invalid value - Bool" - Ensure boolean fields in the request are set to true/false, rather than empty string.
"Invalid value - Integer ####.0" - Ensure integer fields in the request are set to valid integers.
"Invalid JSON Payload - NaN" - Ensure NaN does not appear in the request payload.
"Invalid JSON payload received. - not repeating" - Do not use arrays for non-array fields.

Method specific errors:

dfareporting.reports.run: "Invalid JSON payload received. Unexpected end of string. Expected a value" - Ensure the request body is completely empty.
dfareporting.reports.list: "Request contains an invalid argument." - Ensure that empty fields in the response contain a valid value. For example, empty array fields must be specified by an empty array, rather than an empty string or object.
dfareporting.files.get and dfareporting.reports.files.get: "OAuth token was passed in the query parameter. Please send it in Authorization header instead." - Requests must use the HTTP header Authorization: Bearer [ACCESS_TOKEN] to pass OAuth credentials.

Why is this changing?
Stricter validation helps ensure that problematic requests are not silently ignored, and aligns the behavior of the DCM API with that of other Google APIs.

- Evan Chou, DCM API Team

DCM/DFA Reporting and Trafficking API v3.2 sunset reminder

Monday, August 5, 2019

In accordance with our deprecation schedule, we will be sunsetting version 3.2 of the API on August 31, 2019. Requests to version 3.2 will no longer work after this date, preventing you from updating and accessing information in Campaign Manager. To avoid an interruption in service, you must migrate to a newer API version as soon as possible.

To learn about changes between versions and get tips for migrating, visit the API developer site. Also consider subscribing to this blog to stay up to date about new releases, upcoming sunsets, and changes to the API.

If you have technical questions regarding new versions of the API, please reach out via the developer forum.

- Jonathon Imperiosi, DCM API Team

Subscribe to our RSS feed to get blog posts via email

Friday, February 8, 2019

(If you want to continue getting email updates about our blog posts, read on. If you don't want email updates from this blog, you can skip this post.)

For some products, the Google Ads Developer team has used Google groups as a way to allow API users to subscribe and get new relevant blog posts delivered to their email address. Starting now, the way you can get email updates about blog posts is changing. We will no longer send an email to the Google group for each new blog post. We will continue to use the Google groups for other important updates, however.

For users who still want email updates, we've introduced new FeedBurner links on the right-hand panel of our blog homepage. You can subscribe to the RSS feed by clicking on the link for the product you're interested in, or subscribe by email by clicking on the [+] link to the right of the product name.

If you use any of the APIs that we discuss on this blog, make sure you subscribe to the feed to keep up with the latest news and updates:

- Mike Cloonan, Ads Developer Relations Team

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

Friday, February 8, 2019

- Jonathon Imperiosi, DCM API Team

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

Site-level video creative settings
Additional audio and video creative fields
Support for custom Active View video viewability metrics

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 v3.2, which will sunset on August 31, 2019. After this date, any requests made against v3.2 will begin returning errors.

As a final reminder, API version 3.1 will be sunset on February 28, 2019. 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

DCM/DFA Reporting and Trafficking API v3.0 sunset reminder

Friday, November 2, 2018

- Jonathon Imperiosi, DCM API Team

DCM/DFA Reporting and Trafficking API v3.0 will be sunset on November 30th, 2018. From this date onwards, all requests made against v3.0 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

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

Tuesday, August 14, 2018

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

Support for responsive creatives and placements
Additional signal fields for offline conversions

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 v3.1, which will sunset on February 28, 2019. After this date, any requests made against v3.1 will begin returning errors.

As a final reminder, API version 2.8 will be sunset on August 31, 2018. 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 v3.1 of the DCM/DFA Reporting and Trafficking API

Thursday, May 24, 2018

- Jonathon Imperiosi, DCM API Team

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

Support for in-stream audio creatives
Landing page mobile deep link management

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 v3.0, which will sunset on November 30, 2018. After this date, any requests made against v3.0 will begin returning errors.

As a reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.

Learn More

- Jonathon Imperiosi, DCM API Team

Upcoming changes to reach report metrics in DCM

Wednesday, February 7, 2018

Beginning the week of February 20, a number of reach report metrics in DCM will be renamed. This renaming will modify both API names and column header names in generated report files. These changes are being made to prevent confusion as new reach reports and metrics are developed. The changes are as follows:

Reach Metrics

Old API name	Old column header	New API name	New column header
dfa:activeViewViewableImpressionReach	Active View: Viewable Impression Reach	dfa:activeViewViewableImpressionCookieReach	Active View: Viewable Impression Cookie Reach
dfa:averageImpressionFrequency	Average Impression Frequency	dfa:cookieReachAverageImpressionFrequency	Cookie Reach: Average Impression Frequency
dfa:clickReach	Click Reach	dfa:cookieReachClickReach	Cookie Reach: Click Reach
dfa:impressionReach	Impression Reach	dfa:cookieReachImpressionReach	Cookie Reach: Impression Reach
dfa:incrementalImpressionReach	Incremental Impression Reach	dfa:cookieReachIncrementalImpressionReach	Cookie Reach: Incremental Impression Reach
dfa:incrementalClickReach	Incremental Click Reach	dfa:cookieReachIncrementalClickReach	Cookie Reach: Incremental Click Reach
dfa:incrementalTotalReach	Incremental Total Reach	dfa:cookieReachIncrementalTotalReach	Cookie Reach: Incremental Total Reach
dfa:totalReach	Total Reach	dfa:cookieReachTotalReach	Cookie Reach: Total Reach
dfa:duplicateClickReach	Duplicate Click Reach	dfa:cookieReachDuplicateClickReach	Cookie Reach: Duplicate Click Reach
dfa:duplicateClickReachPercent	Duplicate Click Reach Percent	dfa:cookieReachDuplicateClickReachPercent	Cookie Reach: Duplicate Click Reach %
dfa:duplicateImpressionReach	Duplicate Impression Reach	dfa:cookieReachDuplicateImpressionReach	Cookie Reach: Duplicate Impression Reach
dfa:duplicateImpressionReachPercent	Duplicate Impression Reach Percent	dfa:cookieReachDuplicateImpressionReachPercent	Cookie Reach: Duplicate Impression Reach %
dfa:duplicateTotalReach	Duplicate Total Reach	dfa:cookieReachDuplicateTotalReach	Cookie Reach: Duplicate Total Reach
dfa:duplicateTotalReachPercent	Duplicate Total Reach Percent	dfa:cookieReachDuplicateTotalReachPercent	Cookie Reach: Duplicate Total Reach %
dfa:exclusiveClickReach	Exclusive Click Reach	dfa:cookieReachExclusiveClickReach	Cookie Reach: Exclusive Click Reach
dfa:exclusiveClickReachPercent	Exclusive Click Reach Percent	dfa:cookieReachExclusiveClickReachPercent	Cookie Reach: Exclusive Click Reach %
dfa:exclusiveImpressionReach	Exclusive Impression Reach	dfa:cookieReachExclusiveImpressionReach	Cookie Reach: Exclusive Impression Reach
dfa:exclusiveImpressionReachPercent	Exclusive Impression Reach Percent	dfa:cookieReachExclusiveImpressionReachPercent	Cookie Reach: Exclusive Impression Reach %
dfa:exclusiveTotalReach	Exclusive Total Reach	dfa:cookieReachExclusiveTotalReach	Cookie Reach: Exclusive Total Reach
dfa:exclusiveTotalReachPercent	Exclusive Total Reach Percent	dfa:cookieReachExclusiveTotalReachPercent	Cookie Reach: Exclusive Total Reach %
dfa:overlapClickReach	Overlap Click Reach	dfa:cookieReachOverlapClickReach	Cookie Reach: Overlap Click Reach
dfa:overlapClickReachPercent	Overlap Click Reach Percent	dfa:cookieReachOverlapClickReachPercent	Cookie Reach: Overlap Click Reach %
dfa:overlapImpressionReach	Overlap Impression Reach	dfa:cookieReachOverlapImpressionReach	Cookie Reach: Overlap Impression Reach
dfa:overlapImpressionReachPercent	Overlap Impression Reach Percent	dfa:cookieReachOverlapImpressionReachPercent	Cookie Reach: Overlap Impression Reach %
dfa:overlapTotalReach	Overlap Total Reach	dfa:cookieReachOverlapTotalReach	Cookie Reach: Overlap Total Reach
dfa:overlapTotalReachPercent	Overlap Total Reach Percent	dfa:cookieReachOverlapTotalReachPercent	Cookie Reach: Overlap Total Reach %

Unique Reach (Beta) Metrics

Old API name	Old column header	New API name	New column header
dfa:uniqueReachClick	Unique Reach: Click	dfa:uniqueReachClickReach	Unique Reach: Click Reach
dfa:uniqueReachImpression	Unique Reach: Impression	dfa:uniqueReachImpressionReach	Unique Reach: Impression Reach
dfa:uniqueReachTotal	Unique Reach: Total	dfa:uniqueReachTotalReach	Unique Reach: Total Reach

Questions about this or anything else DCM API related? Contact us via our support forum.

- Jonathon Imperiosi, DCM API Team

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

Thursday, November 16, 2017

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

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

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

Wednesday, November 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

Upcoming changes to standard placement tags in DCM

Monday, July 31, 2017

Beginning in August 2017, DoubleClick Campaign Manager (DCM) will no longer export standard tags for placements larger than 1x1. This is the next step in a phased rollout of changes aimed at aligning DCM's impression counting methodology with the latest Interactive Advertising Bureau and Media Rating Council guidelines. A full overview of these changes can be found in the DCM partner help center.

How will this affect DCM/DFA Reporting and Trafficking API users?

On August 22, 2017, the API's placements.generatetags endpoint will stop returning standard tags (PLACEMENT_TAG_STANDARD) for non-1x1 placements. Users will still be allowed to include this tag format in all generatetag requests without error, however responses will only contain standard tag data for 1x1 placements. This will be a retroactive change affecting all API versions.

What can API users do to prepare?

Users should begin updating their API workflows to request alternative tag formats, such as PLACEMENT_TAG_JAVASCRIPT or PLACEMENT_TAG_IFRAME_JAVASCRIPT, for all non-1x1 placements. Although standard tags will still be returned for 1x1 placements after August 2017, users leveraging pixels for impression tracking are encouraged to use tracking ads for this purpose, instead.

Existing non-1x1 placements trafficked using standard tags will continue to serve until October 2017. Any such placements which are part of a campaign ending later than this must be re-trafficked using an alternative tag format. Instructions for identifying these placements can be found in the DCM partner help center.

Questions about this or anything else DCM API related? Contact us via our support forum.

- Jonathon Imperiosi, DCM API Team

Announcing v2.8 of the DCM/DFA Reporting and Trafficking API

Monday, May 8, 2017

Today we're releasing v2.8 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:

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.7, which will sunset on November 30th, 2017. After this date, any requests made against v2.7 will begin returning errors.

As a final reminder, API version 2.6 will be sunset on May 31st, 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

Upcoming DCM/DFA Reporting and Trafficking API system maintenance

Tuesday, February 21, 2017

Starting in March, DoubleClick Campaign Manager (DCM) will be undergoing scheduled maintenance to make important updates to our systems. Every DCM account will be assigned a single maintenance window. However, these windows may be on different days for different accounts. More information about how this will affect the DCM product can be found in our help center.

How will this affect API users? Maintenance is expected to last up to 8 hours per account. During that time DCM Trafficking will be read-only. While in read-only mode, all API `delete, insert, patch, and update methods requiring the DCM Trafficking scope will be disabled. See the`Scheduled Maintenance page on our developer site to learn more about the methods that will be impacted and the errors you may encounter. What can API users do to prepare? If your application accesses a single DCM account, we recommend simply planning ahead to avoid running workflows that use affected API methods during your account's maintenance window. Details of when this window will occur will be communicated in advance via in-product notification. If your application accesses multiple DCM accounts, you may be subject to multiple maintenance windows. If it's not possible to plan around these windows, you should prepare your application to catch and handle maintenance related errors. Recommended error handling strategies include: For user initiated requests, return an error to the user along with instructions to wait up to 8 hours before retrying the request. For server initiated requests, retry automatically using an exponential backoff strategy. For example: pause 30 seconds before the first retry, 1 minute before the second, 2 minutes before the third, and so on up to a maximum of 8 hours. This strategy helps ensure you're not calling the API too aggressively and that your request quota is not being wasted. Questions about this or anything else DCM API related? Contact us via our support forum. - Jonathon Imperiosi, DCM API Team













                        Google
                      


Labels:



dfa_api





DCM/DFA Reporting and Trafficking API sunset reminder





Friday, February 3, 2017




















                        Google
                      


Labels:



dfa_api


                                ,
                              

sunset








DCM display ads go 100% HTML5 on January 2, 2017





Tuesday, December 13, 2016




















                        Google
                      


Labels:



dfa_api








                      
                    


                      
                    



                          
                        





















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

Ads Developer Blog

Campaign Manager 360 API v3.5 sunset reminder

Announcing v4 of the Campaign Manager 360 API

Campaign Manager 360 API v3.4 sunset reminder

Announcing v3.5 of the Campaign Manager 360 API

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

Stricter Validation For DCM/DFA Reporting and Trafficking API

DCM/DFA Reporting and Trafficking API v3.2 sunset reminder

Subscribe to our RSS feed to get blog posts via email

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

DCM/DFA Reporting and Trafficking API v3.0 sunset reminder

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

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

Upcoming changes to reach report metrics in DCM

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

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

Upcoming changes to standard placement tags in DCM

Announcing v2.8 of the DCM/DFA Reporting and Trafficking API

Upcoming DCM/DFA Reporting and Trafficking API system maintenance

DCM/DFA Reporting and Trafficking API sunset reminder

DCM display ads go 100% HTML5 on January 2, 2017

Labels

Archive