Google Ads Developer Blog: adwords

Increase in Batch Job Service Request Size

reede, 27. märts 2026

Increased Request Limits for BatchJobService Enhance Large Asset Uploads We're pleased to announce significant increases to the request size limits for the BatchJobService.AddBatchJobOperations method in the Google Ads API. These changes are designed to streamline workflows, particularly for developers uploading multiple large assets like images, by reducing the need to split uploads into numerous smaller requests. The following limits have been increased: Request Size Cap on AddBatchJobOperations: Increased from 10,484,488 bytes (approximately 10.48 MB) to 41,937,920 bytes (approximately 41.94 MB). Single Mutate Operation Size: While the overall request can be larger, the size of a single mutate operation within the batch is capped at 10,484,488 bytes (approximately 10.48 MB). What This Means for Developers: This update allows you to include more operations, especially those containing sizable data like image assets, within a single AddBatchJobOperations request. This can simplify your client-side logic and potentially improve throughput by reducing the number of round trips required to add all operations to a batch job. For example, when uploading multiple images, each of which can be up to 5,242,880 bytes (approximately 5.24 MB), you can now batch more of these into a single request, up to the new 41,937,920 bytes (approximately 41.94 MB) total request limit. Important Notes:

While the request size limit has increased, other limitations such as the maximum number of operations per request (10,000) and per job (1 million) still apply. Please refer to the Best Practices and Limitations guide for full details.

We believe this enhancement to the BatchJobService will offer greater flexibility and efficiency for managing bulk operations in the Google Ads API. As always, please reach out to us via the forum or our other support channels if you have any questions or feedback. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server. Bob Hancock, Google Ads API Team

Upgrade to AdWords Universal App campaigns from mobile app install campaigns before October 16th

teisipäev, 19. september 2017

What’s changing?
On August 14th, we announced that AdWords users should start migrating their mobile app install campaigns to Universal App campaigns (UACs). Starting on October 16, 2017, all requests to create new mobile app install campaigns will fail, and all requests to add ads and ad groups to these existing campaigns will fail with an ADD_OP_NOT_PERMITTED error. Edits to these existing campaigns will still be allowed. Starting on November 14, 2017, these mobile app install campaigns will be deleted and will stop serving. Reporting stats for these campaigns will still be available. Mobile app engagement campaigns will not be affected.

Why is this happening?
If you want to learn more about these changes, check out our Propel your mobile app growth with Universal App campaigns announcement.

What should I do?
To avoid errors when managing your mobile app campaigns, here’s what you need to do by October 16th:

Modify your code to enable the creation of Universal App campaigns. Check out our guide on creating Universal App campaigns, which includes code samples in all client library languages.
Disable the creation of mobile app install campaigns and adding ad groups or ads in these campaigns. Edits will still be allowed.

To keep your ads serving beyond November 14th:

Search for all campaigns in your accounts that have campaign status ENABLED or PAUSED with advertisingChannelSubType DISPLAY_MOBILE_APP or SEARCH_MOBILE_APP. After November 14th, these campaigns will have a status of REMOVED because they will be deleted automatically by the AdWords system.
Create a new Universal App campaign to replace each campaign you find.
Once that Universal App campaign is online and serving, remove the mobile app install campaign.

Where can I learn more?
Here are a few resources to get you started:

Mobile app campaigns guide
Universal App campaigns
Client Libraries: Code examples are available in Java, PHP, Python, Ruby, Perl, C#, and VB.NET.

If you have questions while you’re upgrading, please reach out to us on the AdWords API forum.

Nadine Sundquist, AdWords API Team

Changes Required for Creating New Campaigns in the AdWords API v201402

reede, 28. märts 2014

With v201402 of the AdWords API, it is now necessary to set the advertisingChannelType when you create a new Campaign. As part of this change, the networkSetting attribute is now used to define in more detail where you want your ads to appear.

All newly created campaigns, or campaigns that are switched into targeting both Search and Display using v201402, will automatically be SNDS campaigns. This behavior is the same as you will see in the AdWords User Interface, bringing that and the API into closer alignment. Existing applications are unaffected. As we continue to invest in Search Network with Display Select (SNDS) and see strong adoption from advertisers, we will over time be upgrading Search & Display Network campaigns to Search Network with Display Select.

With the introduction of both SNDS and Shopping campaigns, the new advertisingChannelType field allows you to state which kind of Campaign you're building. The field is an enumeration, which can be set to:

SEARCH, for the Search Network, including (for campaigns created with older API releases) Search and Display hybrids, and now SNDS campaigns;
DISPLAY, for the Google Display Network only;
SHOPPING, for Shopping campaigns serving Product Listing Ads on Google and Google Shopping.

Note that an UNKNOWN value can be returned if the value set isn't supported by the called version of the API. This covers situations where new options are added in newer releases.

This table specifies the only valid combinations of parameters for newly created campaigns on the networks that you intend to target.

Networks Targeted by the settings on the right	advertisingChannelType	displaySelect	Enabled networkSettings
Search Network	SEARCH	false	Search Networks only
Search Network with Display Select	SEARCH	true or unspecified	Search & Content networks
Display only	DISPLAY	false or unspecified	Content Network only
Shopping only	SHOPPING	false or unspecified	Search Network only

Any parameter combination other than the above when creating a new campaign or making targeting changes to existing campaigns will be rejected with an OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE error.

While you can no longer create Search & Display Network campaigns, existing campaigns of this type will remain unchanged. You can identify them by their displaySelect attribute being false, while both the Search and Content Networks are enabled. These campaigns should be migrated to SNDS by setting displaySelect to true.

The advertiserChannelType and isDisplaySelect fields are also present in reporting, so you can see how your Campaigns are configured.

If you have any questions about this change or the AdWords API in general, you can post them on our developer forum. You can also follow our Google+ page for updates about the AdWords API.

- Mark R. Bowyer, AdWords API Team

UPDATED: AdWords Display-only campaign NetworkSetting will become immutable in early October

esmaspäev, 19. august 2013

Update: any change to NetworkSetting.targetGoogleSearch will throw a TargetError.TARGET_ERROR after this update takes place.

We'll soon be updating the AdWords API to prevent a subset of CampaignOperation modifications to theNetworkSetting for existing campaigns. Display-only campaigns have been evolving over time, and have developed unique features which make switching these campaigns between Search-only and Search-and-Display unreliable. Today, these modifications can unintentionally change campaign behavior (for instance, disabling certain display-specific targeting), potentially causing confusion and negatively impacting the advertiser experience. So starting in early October, we'll begin returning errors for these NetworkSetting changes.

What this means for you: If you do not make use of the NetworkSetting to change the network for existing campaigns, this change will not affect you.

In a few weeks, any change to NetworkSetting.targetGoogleSearch will throw errors for all versions of the API.

All other NetworkSetting modifications will continue to behave as before.

Posted by
Adwords API team

Changes to advanced location targeting

esmaspäev, 9. aprill 2012

Last year we exposed advanced location targeting settings in the AdWords API, using the GeoTargetTypeSetting object. Based on customer feedback we are now rolling out a series of changes to improve the power and clarity of this feature. The full details of these changes can be found on the Inside AdWords blog, but some highlights are:

The advanced location targeting settings now apply to Display Network traffic in addition to Google Search and the Search Network traffic.

The default value of the exclusion setting will be more restrictive for new campaigns, taking into account both the physical location and the area of interest. In API terms, GeoTargetTypeSetting.negativeGeoTargetType will default to DONT_CARE for new campaigns. The value will not be updated for existing campaigns.

The AdWords web interface has reworded the language used to describe these settings. If you provide a user interface you may want to update your language as well.

If you have any questions about these changes please reach out to us in the forum or during one of our office hours hangouts.

- Eric Koleda, AdWords API Team

Ads Developer Blog

Increase in Batch Job Service Request Size

Upgrade to AdWords Universal App campaigns from mobile app install campaigns before October 16th

Changes Required for Creating New Campaigns in the AdWords API v201402

UPDATED: AdWords Display-only campaign NetworkSetting will become immutable in early October

Changes to advanced location targeting

Sildid

Archive