The Performance Max Asset Group Editing Bug: What's Broken and the Workaround
Search Engine Land has reported a Google Ads bug preventing some advertisers from editing existing Performance Max asset groups through the standard web interface, forcing teams to find a way around a platform-side failure rather than their own configuration mistake. If your changes aren’t saving, aren’t applying, or the interface is behaving unreliably on an asset group edit, here’s how to confirm what you’re dealing with and the workaround that has kept advertisers moving while Google resolves it.
- The bug is confirmed by industry reporting to block edits to existing Performance Max asset groups for some advertisers in the standard web interface.
- Google Ads Editor, the desktop bulk-management tool, has continued to work as a reliable workaround for many affected accounts.
- Rule out a local browser issue first before assuming you're hit by the platform-side bug specifically.
- Report confirmed cases to Google Ads support with specific account details to help prioritize a fix and create a documented record.
What's broken
Search Engine Land reported a confirmed Google Ads bug preventing some advertisers from editing existing Performance Max asset groups directly in the web-based Google Ads interface. Attempted edits, updating headlines, swapping images, adjusting an asset group's targeting signal, either fail to save, produce an interface error, or behave unreliably in a way that leaves advertisers unsure whether a change applied to the live campaign. This is a platform-side reliability issue, not a configuration mistake on the advertiser's end, which is why it's worth documenting rather than assuming you've done something wrong.
How to confirm you're affected
- 01
Rule out a local issue first
Clear your browser cache, try a different browser entirely, and attempt the edit again. A genuine platform-side bug persists across these changes; a local rendering or session issue usually doesn't.
- 02
Try the same edit on a different asset group in the same campaign
If one asset group edits normally and another consistently fails, that pattern is useful information to include when reporting the issue.
- 03
Check whether the change silently fails to persist
Some reports describe an edit that appears to save in the interface but reverts or never applies to the live asset group, which is a distinct and harder-to-notice variant of the bug.
The Ads Editor workaround
For many advertisers hit by this issue, Google Ads Editor, the free desktop application built for bulk campaign management, has continued to allow asset group edits that the web interface won't accept. The practical workflow: open Ads Editor, download the current state of the affected account, make the asset group change locally within the application, and post the change back up to the live account. Because Ads Editor operates through a different technical path than the web interface, it has proven to be a reliable fallback for exactly the kind of interface-specific failure this bug represents.
This is not a permanent substitute for the web interface, and some advertisers will still prefer the web UI's visual preview tools for day-to-day work. Treat Ads Editor as the specific tool for the specific job of getting a blocked asset group edit to apply while the underlying platform bug remains unresolved.
Reporting it to Google
Report confirmed instances through Google Ads support with the specific account ID, campaign, and asset group affected, along with a clear description of what edit was attempted and what happened instead. Individual reports contribute to Google's internal prioritization of a fix, and a documented support case gives you a reference point if the issue materially affects campaign performance in the interim, which matters if you later need to explain a performance gap to a client or stakeholder.
Building a temporary workflow around it
Until Google confirms a fix has shipped, route all Performance Max asset group edits for affected accounts through Ads Editor by default rather than attempting the web interface first and troubleshooting after a failure. This avoids wasted time repeatedly hitting the same platform-side block and keeps asset group updates on schedule despite the interface issue. Combine this with the reporting improvements covered in our PMax search terms insights guide so visibility work isn't also blocked by the same underlying platform instability.
We track platform-side bugs like this actively across client accounts as part of our paid media management service, so a known Google issue doesn't get mistaken for an account-specific problem.
Frequently Asked Questions
Search Engine Land has reported a Google Ads bug that blocks some advertisers from editing existing Performance Max asset groups directly in the Google Ads web interface, with edits failing to save or the interface behaving unreliably when changes are attempted.
No. Reports indicate the bug affects some advertisers and accounts rather than every Performance Max campaign universally, which is typical of a platform-side bug tied to specific account states or interface conditions rather than a change to the product itself.
For many affected advertisers, yes. Google Ads Editor, the desktop application for bulk account management, has continued to allow asset group edits for accounts where the web interface editing is blocked, making it the practical workaround while Google resolves the underlying issue.
Yes. Reporting through Google Ads support with specific account and campaign details helps Google prioritize a fix and gives you a documented case if the issue affects campaign performance in the meantime.
Ready to fix what’s costing you conversions?
We’ll review your acquisition funnel, show you what’s underperforming, and hand you a clear, prioritised plan, whether or not you choose to work with us.
Get a clear diagnosis of your acquisition performance.
- 30-minute review
- Free, with no obligation
- Clear findings and priorities
- You keep the findings
30 minutes · Free · No obligation · You keep the findings