Google Ads Developer Blog: google_ads

Managing your integrations at scale: Ads DevCast E4

2026 m. gegužės 7 d., ketvirtadienis

Scaling an advertising integration is more than just writing code—it requires a deep understanding of efficiency, resilience, and auditability. In Episode 4 of Ads DevCast, "Managing your integrations at scale," we break down universal architectural best practices and product-specific solutions to help you optimize your advertising integrations. Watch the full episode Hear the full episode Whether you are working with the Google Ads API, Google Ads scripts, Data Manager API, DV360, or Google Analytics, here is a summary of the key takeaways to build high-performance, scalable systems. Universal Principles of Robust Integrations

Respect Rate Limits: Rate limits are a reality of using APIs at scale. Understand your limits beforehand to prevent lockouts and maintain a healthy integration. Read the error messages — they may contain instructions on what to do next. For transient or retry-able errors, don't hammer the server with rapid retries. Instead, implement exponential back-off with jitter to give the system time to recover.

Prioritize Logging and Monitoring: Always consider logging in production where appropriate. Capture crucial metadata, like the Google Ads API request_id, in your structured logs to trace failures instantly. If a call is erroring, write that error payload to logs. Set up proactive alerts to catch errors before they impact operations.

Use Official Client Libraries: While direct REST/gRPC calls are supported in many of our products, using official libraries saves development time and handles heavy lifting (e.g., serialization and authentication) out of the box.

Cache Smartly: Reduce redundant queries. If you are querying historical data that will no longer change, cache it locally to save bandwidth and rate limits.

Product-Specific Best Practices

Google Ads API: Optimize efficiency by Batching Operations. Group operations logically to reduce round-trips. Order your operations correctly to improve execution efficiency.

Data Manager API: Batch ingestion requests to process events efficiently. Understand the difference between synchronous errors (structural issues returned instantly that reject the whole batch) and asynchronous validation (monitored via the Diagnostics endpoint).

Google Ads scripts: Avoid sequential iterations when dealing with many accounts at once. Use Bulk Uploads with CSV tables to apply scaled operations, and leverage the executeInParallel method for MCC scripts to run up to 50 concurrent execution threads.

Display & Video 360 API: Utilize Structured Data Files (SDFs) to manage YouTube line items and ad group bulk operations that aren't natively supported by the API.

Google Analytics: Enable daily BigQuery Exports for event-level data, and utilize Long-running Asynchronous Report Tasks in the Analytics Data API v1alpha to build scalable, customized reports without HTTP timeouts.

Next Steps: Watch the full episode on our YouTube channel (or listen on YT Music) Check out our Advertising and Measurement Developer Hub. Join our community on Discord and share your scaling stories or questions with Googlers and other developers. Learn more in our guides below:

Google Ads API Best Practices and Batch Processing

Google Ads scripts Bulk Upload and Best Practices

Analytics BigQuery Solution and Report Tasks Fundamentals

Data Manager API Best Practices, Limits, and Diagnostics

Display & Video 360 Structured Data Files (SDFs)

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

New Data Retention Policy for Google Ads starting June 1, 2026

2026 m. gegužės 1 d., penktadienis

table#dataretensionmay2026{ border-collapse: collapse; } table#dataretensionmay2026 td { border: 1px solid grey; padding:5px; } Starting June 1, 2026, Google Ads and related measurement APIs will transition to a 37-month data retention policy for granular performance statistics (daily, hourly, and weekly). High-level data (monthly, quarterly, and yearly) will continue to be available for 11 years.

API

Impact

Next Steps

Google Ads API and Google Ads scripts

Starting June 1, 2026, queries that request granular segments (such as segments.date, segments.week) for ranges older than 37 months from the current date will return a DateRangeError.INVALID_DATE error. Future API versions will return DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED error. To retrieve data older than 37 months, you must update your queries to use segments.month, segments.quarter, or segments.year. Unsegmented queries for historical data must align perfectly with calendar month boundaries (1st to last day of month) to succeed.

Please review your applications and make updates. If you require granular historical data beyond 37 months, we recommend exporting it prior to the June 1, 2026 deadline.

If you have any questions, you can contact us on our Google Ads API support channel or Google Ads scripts support channel.

Google Analytics Data API

The Google Analytics Data API will truncate affected metrics to the latest 36-month window if the dimension "date" is also used in the report. Affected metrics include Advertiser Ad Cost, Clicks, and Impressions. Only reports with all of affected metrics, 37-months or older, and including the dimension "date" are impacted. Date-equivalent dimensions like "Day of week" and "day" are also impacted.

Review your data stitching logic to account for this truncation.

DV360 API and CM360 API

These APIs currently maintain a 24-month retention period, which remains unchanged.

No impact.

BigQuery Data Transfer Service

Starting June 1, 2026, the BigQuery Data Transfer Service for Google Ads and BigQuery Data Transfer Service for Search Ads 360 connectors will stop populating data for backfill runs with dates older than 37 months from the current date. Data transferred and stored in BigQuery will remain in the tables with no impact.

Starting June 1, 2026, BigQuery Data Transfer Service for Google Analytics 4 connector will stop populating data for backfill runs with dates older than 37 months from the current date. Data transferred and stored in BigQuery will remain in the tables, but if a transfer is manually triggered for a report date 37-months or older, the data of the date in BigQuery table will be overwritten by empty value.

If you want to keep historical data beyond 37 months in BigQuery, we recommend starting backfilling runs early so that they can complete before June 1, 2026.

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.

Nadine Wang, Advertising and Measurement APIs Team

Merchant API is coming to Google Ads scripts starting April 22, 2026

2026 m. balandžio 9 d., ketvirtadienis

The Content API for Shopping will sunset on August 18, 2026, to be replaced by the Merchant API. This migration provides a shift toward more robust, scalable, and feature-rich integrations. For Google Ads scripts users, the Google Ads scripts editor will begin rolling out Merchant API support on April 22, 2026. While the Content API for Shopping will remain available until its sunset, here’s what to expect from the Merchant API. Understanding the Merchant API The Merchant API offers important changes and improvements over the Content API for Shopping:

Modular Design: The Merchant API is broken down into sub-APIs. This allows for:

Faster access to new features and updates.
Easier versioning and maintenance.
Reduced disruption, as changes in one sub-API are less likely to impact others.

New Features & Capabilities:

Omnichannel Support: Designed with Omnichannel in mind, though it provides backward compatibility for legacy separate online/local offer structures using the legacy_local flag.

Take a look at the Merchant API migration guide for more detail on the changes between APIs. How to get started The Merchant API will be available as an Advanced API in the Google Ads scripts editor, just as the Content API is. 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.

- Dora Sun - Google Ads API Team

Introducing the Google Advertising and Measurement Developers Hub!

2026 m. balandžio 6 d., pirmadienis

We're excited to announce the launch of the new Google Advertising and Measurement Developers Hub! Come see the new site! Whether you're looking to automate campaigns, analyze performance, manage tags, or monetize your apps, the new hub is designed to make it easier to find the right tools and information. We've launched a new technical-user focused site to make it easier than ever for you to find the tools, resources, and support you need to build and innovate with Google's advertising and measurement products. What's New? We have created a one-stop shop where you can easily find the resources you need, connect with our team and the community, and get support. Here are some key features:

At-a-glance homepage: A clear starting point highlighting how we can help, with quick links to our blog, Discord, and information about our team.

Meet the team: Learn more about the Developer Relations team dedicated to supporting your success.

Products: A comprehensive directory of the developer products we cover, from the Google Ads API and Google Analytics APIs to Publisher Tools like AdMob and Ad Manager, linking directly to their official documentation. You can browse by categories like Advertising Platforms, Tagging, Measurement & Analytics, and Publisher Tools.

Connect with us: A streamlined page to help you find the best way to engage:

Join our vibrant Discord community.
Find links to product or technical support.
Download open source projects on GitHub.

Media and podcast: A new home for our multimedia content, including the Ads DevCast playlist embedded directly on the page.

We're excited to make this the place for you to learn, build, and connect. Please explore the new site and use the Send Feedback button located at the bottom of each page to share your thoughts! If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our "Google Advertising and Measurement Community" Discord server. Happy Building!

- Aalap Shastri, Google Ads API Team

Additional changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

2026 m. vasario 26 d., ketvirtadienis

What’s changing? In 2025, Google rolled out changes to support the EU Political Ads Regulation in the Google Ads API and Google Ads scripts. On April 1, 2026, we will change account-level API restrictions. If you use either of these products to create or manage campaigns, you may need to update your application before April 1, 2026 to handle these enforcements. API validation and enforcement changes On April 1, 2026, Google Ads API and Google Ads scripts will implement the following changes in versions v20, v21, v22 and v23 of the API.

If a Google Ads account has one or more undeclared campaigns, all mutate calls related to campaign management will fail with a MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error.

You can determine if a campaign is undeclared by examining the Campaign’s missing_eu_political_advertising_declaration field.

All other calls – such as reporting, account management or keyword planner – will continue to work unaffected. See the full list of methods.

To declare currently undeclared campaigns, retrieve the list of eligible campaigns, and set their contains_eu_political_advertising declaration using the CampaignService.MutateCampaigns method, GoogleAdsService.Mutate method, or using the BatchJobService. These methods won’t fail with a MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error as long as you only update the campaign's contains_eu_political_advertising field. You can retrieve the list of undeclared campaigns by running the following GAQL query using either the Search or SearchStream methods of the GoogleAdsService.

select campaign.id from campaign where campaign.missing_eu_political_advertising_declaration = true How will this affect my campaign serving? Any campaign that has declared EU political ads by setting contains_eu_political_advertising to true will stop serving ads in the EU. Refer to the Help Center to learn more. What do I need to do? If your application uses either the Google Ads API or Google Ads scripts to create or manage campaigns, make sure to update your application to handle these enforcements before April 1, 2026. How do I get help? Reach out to the Google Ads API support or Google Ads scripts support channels if you have more questions about this change.

- Anash P. Oommen, Google Ads API Team

Sunsetting Google Ads API, Google Ads Scripts, and Campaign Manager 360 API Developer Support Forums on Google Groups

2025 m. gruodžio 1 d., pirmadienis

To streamline our technical support channels, we will be sunsetting the following developer support forums on Google Groups:

Google Ads API

Google Ads Scripts

Campaign Manager 360 API

Effective January 28, 2026,

Support agents will no longer respond to new forum posts. Send your questions using the recommended support channels mentioned below.

If you reply to any existing forum threads with the support teams on or after this date, they will initiate a new email thread to continue your discussion.

We plan to disable the ability to create new forum posts at a later date in 2026, but the existing forum content will remain visible as a read-only archive for the time being, so you can still access past discussions and solutions. Where can I get technical support for these products? Our developer site and other documentation has been updated to the new preferred technical support channels. Moving forward, the best way to reach us for technical support for these products will be through our official support channels below:

Google Ads API: https://developers.google.com/google-ads/api/support/contact

Google Ads Scripts: https://developers.google.com/google-ads/scripts/docs/support/contact

Campaign Manager 360 API: Contact the Campaign Manager 360 support team for assistance.

As always, when submitting a support request, please provide all relevant details to help us expedite the resolution of your issues. This typically includes:

For Google Ads API: Always include the request-id found in the response logs, along with the complete request and response logs.

For Google Ads Scripts: Include the script name, Customer ID, and any relevant execution logs or error messages from the Google Ads UI.

For Campaign Manager 360 API: Provide relevant IDs (e.g., Profile ID, Account ID), the API method, and the full request and response logs if possible.

All Products:

A clear description of the issue
What you expected to happen
Steps to reproduce the issue
Relevant code snippets
Any error messages received

Providing comprehensive information upfront will help our team diagnose and assist you more effectively. The support page will guide you on the necessary information. If you’re looking for updates, events, or non-support focused conversation with Googlers or fellow members of the developer community on the products listed above, please join us on our “Google Advertising and Measurement Community” Discord server. We appreciate your understanding as we make this transition to better focus our support resources.

- Aalap Shastri, Google Ads API Team

Google Ads scripts documentation upgrade

2025 m. rugsėjo 22 d., pirmadienis

We’re excited to announce a refresh of the Google Ads scripts documentation! Like the Google Ads API documentation changes announced in a previous blog post, we have focused on making the Google Ads scripts documentation more intuitive and useful. Here’s a sneak peek at what’s new: 1. Logically grouped guides We’ve reorganized our guides into clear categories. Whether you're a beginner starting out with core concepts or an expert exploring all the different campaign types supported by scripts, you'll find what you need faster. These changes will help you write scripts more efficiently by smoothly navigating between related topics, building on previous guides and highlighting unique scripts features. 2. Dedicated reference tab You now have a dedicated reference tab to quickly explore all the scripts objects available to you. This creates a direct path to the resources you need and aligns our documentation more closely with the Google Ads API documentation, providing a more seamless experience across our products. 3. Combined solutions and examples We've merged the solutions and examples tabs into a single, comprehensive resource. Now you can find all our sample code in one place. This is a great launchpad for discovering what’s possible with scripts and for modifying examples to create your own powerful solutions. We have more exciting updates on the way, and we'll be incorporating more of the fantastic feedback from our Google Ads scripts community. If you have any questions, suggestions, or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server, where we have a dedicated #ads-scripts channel.

- Dora Sun - Google Ads API Team

Changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

2025 m. rugpjūčio 7 d., ketvirtadienis

What’s changing? As announced last year, Google will stop serving political advertising in the European Union ahead of a new regulation taking effect in October 2025. On September 3, 2025, the Google Ads API and Google Ads scripts will roll out enforcements related to this change. If you use either of these products to create or manage campaigns, you may need to update your application to handle these enforcements before September 3, 2025. API support for self-declaration of EU political ads Google Ads API and Google Ads scripts have added support for self-declaration as to whether a campaign has EU political ads. Learn how an EU political ad is defined here. Versions v19.2, v20.1, and v21 of the API contain a new field named contains_eu_political_advertising in the Campaign object. The possible values and their meaning are shown in the table below.

Value

Meaning

CONTAINS_EU_POLITICAL_ADVERTISING

The campaign has EU political ads.

DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING

The campaign does not have EU political ads.

UNSPECIFIED

The campaign is missing self-declaration about EU political ads.

You can retrieve the self-declaration status of a campaign in Google Ads API by running the following query using either the Search or SearchStream methods of the GoogleAdsService. For Google Ads Scripts, use the AdsApp.search or AdsApp.report methods. select campaign.id, campaign.contains_eu_political_advertising from campaign If you use the Google Ads API client libraries, you may need to download the latest library version to use this functionality in versions v19 and v20 of the API. API validation & enforcement changes On September 3, 2025, Google Ads API and Google Ads scripts will start enforcing the following checks in versions v19 and v20 of the API.

All new campaigns created either through Google Ads API or Google Ads scripts should set the contains_eu_political_advertising field. The API call to create a new campaign using CampaignService.MutateCampaigns will fail with a FieldError.REQUIRED error if this field is not set. Google Ads Scripts will enforce these checks when creating campaigns using AdsApp.mutate or AdsApp.mutateAll methods.

All the existing campaigns should set the contains_eu_political_advertising field before attempting to change proximity, location, or location_group targeting either at the campaign or ad group levels. The API call to create or update these campaign criteria using CampaignCriterionService.MutateCampaignCriteria method for existing campaigns will fail with a CriterionError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION error if the campaign hasn’t completed the self-declaration. The API call to create or update these ad group criteria using AdGroupCriterionService.MutateAdGroupCriteria will also fail in a similar manner if the campaign hasn’t completed the self-declaration. Google Ads scripts will enforce these checks when attempting to change targeting using AdsApp.mutate, AdsApp.mutateAll, AdsApp.Campaign.addProximity, and AdsApp.Campaign.addLocation methods.

These enforcements also apply to other mechanisms that you can use to make campaigns, such as running Batch Jobs and using GoogleAdsService.Mutate method to create and update entities.

Attempting to schedule a new experiment using ExperimentService.ScheduleExperiment method will throw an ExperimentError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION error if the contains_eu_political_advertising declaration is missing on the treatment draft campaigns.

If you use the bulk upload feature in Google Ads scripts, check the product documentation to learn more about the spreadsheet template changes required as part of this change.

These checks are already enforced in version v21 of the Google Ads API. How will this affect my campaign serving? Any campaign that has declared EU political ads by setting contains_eu_political_advertising to true will stop serving ads in the EU on September 22, 2025. Refer to our Help Center to learn more. Existing campaigns without a declaration will remain unaffected for now. We recommend updating the existing campaigns in your accounts with an appropriate declaration as soon as possible. You can retrieve campaigns without a declaration using the following GAQL query using either the Search or SearchStream methods of the GoogleAdsService. select campaign.id, campaign.contains_eu_political_advertising from campaign where campaign.contains_eu_political_advertising NOT IN ( 'CONTAINS_EU_POLITICAL_ADVERTISING', 'DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING' ) What do I need to do? If your application uses either Google Ads API or Google Ads scripts to create or manage campaigns, make sure to update your application to handle these enforcements before September 3, 2025. How do I get help? Reach out to the Google Ads API support or Google Ads scripts support channels if you have more questions about this change.

- Anash P. Oommen, Google Ads API Team

Join our “Google Advertising and Measurement Community” Discord Server

2025 m. liepos 8 d., antradienis

We’re launching our new “Google Advertising and Measurement Community” Discord server! To join, just click this invite link and follow the onboarding guide. The current products available on this server are Analytics, Google Ads, Google AdMob, and Google Ad Manager. The Ads Developer Relations team will be on this server regularly to discuss your feedback or questions using Google’s Advertising and Analytics APIs/SDKs, as well as to let you know what’s new with our products. We’ll be hosting a “Meet the Team” in August, where we’ll go over who we are, and how you can expect to engage with us in Discord. Stay tuned as we add other events, and more channels. Looking forward to chatting with you on Discord!

- Cory Liseno, on behalf of the Ads Developer Relations Team

Google Ads Scripts Sunsetting Ad Customizers for Expanded Text Ads and Legacy Ad Extension Entities Starting July 14, 2025

2025 m. birželio 25 d., trečiadienis

Starting July 14, 2025, Google Ads scripts will begin to throw errors for requests related to ad customizers for expanded text ads and feed-based legacy ad extensions. Ad customizer changes Any requests related to Ad Customizer entities, such as AdsApp.AdCustomizerSource or AdsApp.newAdCustomizerSourceBuilder, will begin to return sunset errors. These entities have been read-only since deprecation in 2022 and haven’t been served on any ads since May 2024. They were also fully removed from the Google Ads API in the v19 release. Ad extension changes Feed-based Ad Extensions were sunset in 2022 in favor of asset-based extensions. Users were asked to migrate, or were migrated automatically, but were able to access legacy functionality through the withOnlyLegacy() methods on various selectors. The withOnlyUpgraded() method was added to allow users to only use upgraded asset-based extensions. Starting July 14, 2025, the legacy functionality will be removed, and withOnlyLegacy() methods will begin to throw a sunset error. The withOnlyUpgraded() methods will log a warning, since it will no longer be necessary to specify the use of asset-based extensions when they are the only option. If you have any questions, ask them in the Google Ads scripts forum. We're here to help!

- Dora Sun - Google Ads API Team

Upcoming change to LowerTargetRoas recommendations in the Google Ads API and Google Ads scripts

2025 m. kovo 26 d., trečiadienis

As of v17 of the Google Ads API, recommendations of type LOWER_TARGET_ROAS have included a current_average_target_micros as a whole currency value instead of a micros value (where one million is equivalent to one currency unit) as indicated by the field name. On April 23, 2025, we are rolling out a fix to populate current_average_target_micros with the micros value. Note that as a result of the incorrect unit, the currently returned current_average_target_micros value is truncated and is therefore less precise than the micros equivalent. If you were converting the existing value to micros by multiplying by 1,000,000, the resulting value wouldn't necessarily be correct because any digits past the first position are dropped. For example, a current_average_target_micros value of 5 might have been converted to 5,000,000 in micros before the change, but could be returned as 5,750,000 (more precise) after the change. What do I need to do? If you use the Google Ads API or Google Ads scripts to query the recommendation resource for recommendations of type LOWER_TARGET_ROAS, and your application logic uses the current_average_target_micros field, you must update your application to treat the value as micros instead of a whole budget value for when the change takes effect on April 23, 2025. If you have any questions or need help, check out the Google Ads API support page for options.

- Laura Chevalier, Google Ads API Team

Google Ads API and Google Ads scripts search term insight report update starting March 3, 2025

2025 m. sausio 28 d., antradienis

Starting on March 3, 2025, the Google Ads API and Google Ads scripts search term insight reports will return all search subcategories as empty. The Google Ads UI already removed this field, and the API is also rolling out this change to be consistent across Google Ads. What do I need to do? Starting March 3, 2025, it is expected that all values for segments.search_subcategory will be empty. If you query segments.search_subcategory in the campaign_search_term_insight or customer_search_term_insight reports, then:

Check that your code can handle an empty value in segments.search_subcategory. An empty string already is a catch-all, so your code should be already handling this.

We recommend removing segments.search_subcategory from your query.

If you have any questions or concerns, you can reach out to us through our support form.

Nadine Wang, Google Ads API Team

Consent unbundling in Google Ads scripts

2024 m. lapkričio 12 d., antradienis

forum - Mike Cloonan, Google Ads Scripts Team

Subscribe to the blog

2024 m. rugsėjo 19 d., ketvirtadienis

RSS feedcommunity resource on GitHub

Structured Data Files

IMA SDK

Mobile Ads SDK

- Mike Cloonan, Ads DevRel Team

Create Performance Max campaigns in Google Ads scripts

2024 m. gegužės 23 d., ketvirtadienis

developers sitemutateGoogle Ads APImutate strategyforum - Mike Cloonan, Google Ads Scripts Team

Upcoming Google Ads change – switching user accounts and account settings to a business email

2024 m. gegužės 16 d., ketvirtadienis

Google Ads is rolling out a new feature that allows the account administrator to request its users to switch from a regular personal email address (for example john.doe@gmail.com) to a business email address (for example john.doe@example.com). We are making this change to improve account security and reduce potential surface for abuse. This is an informational post to highlight how this feature could affect the Google Ads API and Google Ads scripts developers. How does this feature work? To use this feature, the account administrator sends a request to an account user from the Google Ads UI to switch their personal email to a business email. If the user accepts, then the following steps are bundled behind the scenes:

A business email address is added to the Google Ads account.

A grace period of one month starts, where both the personal email address and business email address are active users in the Google Ads account.

The personal email address is removed from the Google Ads account at the end of the grace period.

Refer to our help center guide to learn more about this feature. How does this affect API developers? As a developer, you may need to do the following additional steps:

If the user has authorized your application to make API calls to the Google Ads account using their personal email address, then the OAuth 2.0 refresh token will stop working once the personal email address is removed from the Google Ads account. You need to authorize the user with the new business email address.

This change only works with Google Ads accounts. If the user manages other accounts, such as Google Analytics or Google Merchant Center, then the email address needs to be switched manually in those accounts. See the help center page for a more comprehensive list of locations where you might have to make a change.

If you have authorized and scheduled Google Ads Scripts with the personal email address, you need to authorize the scripts with the business email address after this change.

How to get help If you have any questions or need help, check out the Google Ads API support page or Google Ads scripts support page for options.

- Anash P. Oommen, Google Ads API Team

Google Ads scripts updates for v15

2024 m. vasario 22 d., ketvirtadienis

Google Ads scriptsGoogle Ads API v15searchmutateGoogle Ads API v15

AdsApp.adMedia() will throw a sunset error. Media is no longer supported. Assets are used instead.

ResponsiveDisplayAd would previously return a Media when fetching its marketing image or logo image. Instead, this will now return null.

ImageAd.getImage() previously returned a Media. It will now return an Asset instead. This will be a breaking change if you depend on this method.

forum - Mike Cloonan, Google Ads Scripts Team

Announcing New Reporting Script for Performance Max

2023 m. liepos 17 d., pirmadienis

How can I get started?Find the script hereforumDavid Stevens, Google Ads Scripts Product Manager

Generic mutate support in Google Ads scripts

2023 m. liepos 13 d., ketvirtadienis

generic mutate functionalityconst budgetResult = AdsApp.mutate({ campaignBudgetOperation: { create: { amountMicros: 10000000, explicitlyShared: false } } }); MutateOperation reference documentationnew guideforum - Mike Cloonan, Google Ads API Team

Experiment changes in Google Ads scripts

2023 m. kovo 21 d., antradienis

Drafts and Experiments guideconst draft = campaign.newDraftBuilder() .withName(newDraftName) .build() .getResult(); // Modify the draft campaign before beginning the experiment. const draftCampaign = draft.getDraftCampaign(); const experiment = draft.newExperimentBuilder() .withName(newExperimentName) .withTrafficSplitPercent(50) .startBuilding();const experiment = AdsApp.newExperimentBuilder() .withCampaign(campaign) .withTrafficSplitPercent(50) // Some new fields are required. .withStartDate("20230501") .withEndDate("20230601") .withType("SEARCH_CUSTOM") // The suffix will automatically be added to the end of the name for // each experiment campaign. .withSuffix("experiment") // Goals have no effect on the serving of the experiment, but instead // just help you keep track of your intentions. .withGoals([{metric: 'CLICKS', direction: 'INCREASE'}]) .build(); // The experiment campaign is the new equivalent of the draft campaign // in the example above. const experimentCampaign = experiment.getExperimentCampaign();forumgoogleadsscripts-support@google.com - Mike Cloonan, Google Ads Scripts Team

Ads Developer Blog

Managing your integrations at scale: Ads DevCast E4

New Data Retention Policy for Google Ads starting June 1, 2026

Merchant API is coming to Google Ads scripts starting April 22, 2026

Introducing the Google Advertising and Measurement Developers Hub!

Additional changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

Sunsetting Google Ads API, Google Ads Scripts, and Campaign Manager 360 API Developer Support Forums on Google Groups

Google Ads scripts documentation upgrade

Changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

Join our “Google Advertising and Measurement Community” Discord Server

Google Ads Scripts Sunsetting Ad Customizers for Expanded Text Ads and Legacy Ad Extension Entities Starting July 14, 2025

Upcoming change to LowerTargetRoas recommendations in the Google Ads API and Google Ads scripts

Google Ads API and Google Ads scripts search term insight report update starting March 3, 2025

Consent unbundling in Google Ads scripts

Subscribe to the blog

Create Performance Max campaigns in Google Ads scripts

Upcoming Google Ads change – switching user accounts and account settings to a business email

Google Ads scripts updates for v15

Announcing New Reporting Script for Performance Max

Generic mutate support in Google Ads scripts

Experiment changes in Google Ads scripts

Etiketės

Archive