We are announcing support for new generic mutate functionality in Google Ads scripts, available today. Most mutate operations that are supported by the Google Ads API can now be performed directly in scripts.


For example, to create a simple budget:

const budgetResult = AdsApp.mutate({
    campaignBudgetOperation: {
        create: {
            amountMicros: 10000000,
            explicitlyShared: false
        }
    }
});

The new functionality enables you to create full campaign hierarchies, new conversion actions, and more that previously was not possible in scripts. For a full list of available operations, check out the MutateOperation reference documentation for the Google Ads API. Note that a few operation types are still restricted in scripts.

Check out the new guide for a complete overview of how to use the feature, including update and remove operations and performing multiple operations in a single call.

Please contact us on our forum or at [email protected] if you have any questions.
- Mike Cloonan, Google Ads API Team

Starting in April, we will be rolling out a change to the way you create experiments in Google Ads scripts to bring the process more in line with the Google Ads API. Previously, you would create a draft, modify the draft, and then create an experiment from the modified draft. Now, you will create the experiment directly, which will automatically create the underlying drafts and allow you to modify them before scheduling the experiment.

You can read more about this feature in our Drafts and Experiments guide.

To summarize the new changes in a simple example, if you had code such as:

const 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();

The new equivalent code would be:

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();

This change will allow us to bring further improvements to this feature as they are added in the Google Ads API.

If you have any questions or feedback, please leave a post on our forum or send a message to our support alias [email protected].
- Mike Cloonan, Google Ads Scripts Team

Today we're launching support for Performance Max campaigns in Google Ads scripts. This is treated as a brand new campaign type in scripts, similar to how video or shopping campaigns already work.

To get started, check out the performance max campaigns selector on the AdsApp. Once you've selected a PerformanceMaxCampaign, you can perform common operations like pausing or enabling the campaign, as well as selecting and modifying most asset types in asset groups. You cannot modify text assets this way, and you cannot create new campaigns or asset groups through scripts.

Performance Max retail campaigns are supported in only a limited fashion as listing groups cannot be managed via Scripts.

For more information about Performance Max campaigns in general, check out the complete help center article.

If you have any questions or feedback, please leave a post on our forum or send a message to our support alias [email protected] so that we can help.
- Mike Cloonan, Google Ads Scripts Team

Today we’re launching the full version of the new Google Ads scripts experience. The beta has been running since June of last year, and now the final batch of features to match the functionality of legacy scripts has been released.

Starting soon, all new scripts will default to the new scripts experience, although you can still disable it on a script by script basis if necessary. Existing scripts won't be affected until September of 2022. After that, we will migrate all scripts to the new experience. You should manually move your scripts over to the new experience before then to ensure continued functionality. We've tried to implement backwards compatibility, but we can't guarantee every script will work without changes, so definitely take some time to confirm yourself.

Here are some highlight features in the new experience:

• Support for ES6, including let, classes, for..of loops, and more.
• Improved throughput, meaning you can process more entities in the same amount of time. We've also removed the entity limits on processing, although time limits remain in place.
• Support for new asset-based extensions.
• Enhanced bidding strategy support.

The following features are added in this release:

• Manager account scripts
• Bulk upload
• Video campaigns

See the updated Google Ads scripts site for full information on the new experience, including migration information, performance improvements, and updated best practices. This replaces the documentation for the legacy scripts experience, but if you must reference that we will preserve it at a new location until the legacy scripts sunset: https://developers.google.com/google-ads/scripts-legacy

If you have any questions or feedback regarding the new experience, please leave a post on our forum so that we can help.
- Mike Cloonan, Google Ads Scripts Team