Google Ads PMax Asset Group Editing Bug: What Happened and How to Stay Operational

In January 2026, a Google Ads bug made it impossible to edit Performance Max asset groups through the web interface for three full days. Advertisers who relied solely on the browser-based UI were locked out of campaign changes until Google Ads Editor or the API provided a workaround. The lesson: every PPC team needs at least one backup workflow.

The short version

On January 23, 2026, Performance Max advertisers started reporting that saving changes to asset groups in the Google Ads web interface was failing with an error message. The bug affected PMax campaigns specifically — edits to text assets, images, videos, and asset group configurations would not persist. Google acknowledged the issue and recommended Google Ads Editor and the API as workarounds. Three days later, on January 26, Google Ads Liaison Ginny Marvin confirmed the bug was fully resolved. The incident highlights a broader operational truth: the web UI is not a single point of failure you can afford to have.

Key facts

• Bug prevented saving Performance Max asset group edits in the web UI starting January 23, 2026
• Google Ads Editor and the API both worked as functional workarounds during the outage
• The issue was fully resolved by January 26, 2026 — a three-day outage
• Google Ads Liaison Ginny Marvin personally confirmed the fix on LinkedIn
• Advertisers without a backup workflow were unable to modify PMax campaigns for three days

What happened

The bug was first surfaced by Chelsea Harding, a PPC professional who posted about the issue on LinkedIn on January 23, 2026. She wrote: “If you are receiving the below error when you try to edit and save existing asset groups, you aren’t alone! I have been unable to do so for the last few days now” SERoundtable.

Other advertisers quickly confirmed the issue. Tom Cox replied on the same thread, noting: “Not just me then! I also figured out how to get round it by using the ads editor” SERoundtable. The bug was specific to Performance Max campaign asset group editing — standard Search campaigns and other campaign types were not affected.

Google’s support team acknowledged the bug the same day. Harding reported: “I’ve reached out to Google who have said they are looking into it but in the meantime - my current workaround is by editing in Google Ads Editor and uploading that way” SERoundtable. Search Engine Land also covered the story with the headline “Google Ads bug blocks edits to Performance Max asset groups” Search Engine Land.

On January 26, Ginny Marvin, the Google Ads Liaison, confirmed the resolution on LinkedIn: “Hi Chelsea, confirming that this issue has been resolved. Glad to hear you were able to get edits made via Editor in the meantime. We apologize for the inconvenience and appreciate your patience” SERoundtable.

Why does this matter for PMax advertisers?

Performance Max is Google’s most automated campaign type. It relies heavily on asset groups — collections of headlines, descriptions, images, videos, and logos that Google’s AI assembles into ads across Search, Display, YouTube, Discover, Gmail, and Maps. When asset group editing breaks, you lose the ability to:

• Update promotional copy for seasonal offers or sales
• Swap out underperforming creative assets
• Add new audience signals to guide the AI
• Remove assets flagged by policy violations

For ecommerce advertisers running time-sensitive promotions through PMax, a three-day editing blackout could mean running outdated creative during a sale weekend. For lead-generation accounts testing new messaging, it could mean wasting budget on copy that already proved ineffective.

The fact that Google’s response was fast — a three-day turnaround with a confirmed resolution — is reassuring. But the dependency is real. PMax advertisers should treat Google Ads Editor proficiency as a core competency, not a nice-to-have. If your team doesn’t have Editor installed and configured on at least one machine, you’re one outage away from losing campaign control.

How to build a backup workflow for Google Ads

The PMax asset group bug is not an isolated incident. Google Ads platform glitches happen periodically — the interface may break, an API endpoint may return errors, or a browser update may cause rendering issues. Having a backup workflow ensures you can always make changes when you need to.

Here is a practical backup workflow every PPC team should implement:

1. Google Ads Editor — install and keep updated

Google Ads Editor is a free desktop application that supports full offline editing of campaigns, including Performance Max. It supports bulk edits, copy-paste between accounts, and version history. Install it on at least one team member’s machine and set a calendar reminder to update it monthly — Editor releases ship every 4-6 weeks with new features and bug fixes. During the January 2026 outage, Editor was the workaround that kept advertisers operational.

For a complete guide to structuring and optimizing PMax campaigns, see our Performance Max Strategy 2026 guide.

2. Google Ads API access — the programmatic safety net

The Google Ads API provides programmatic access to every function available in the web UI, including asset group management. Setting up API access requires a developer token and OAuth2 credentials — the setup takes about an hour but pays for itself the first time the web UI breaks. Tools like the Google Ads Scripts platform also sit on top of the API and provide a middle ground between full code and the GUI.

3. Monitor official Google Ads channels

Ginny Marvin’s confirmation of the fix came through LinkedIn, which is not exactly a real-time alerting system for outages. Better sources include:

• The Google Ads Status Dashboard (ads.google.com/status)
• The Google Ads Developer Blog for API-specific issues
• The @GoogleAds Twitter/X account

Following these channels means you learn about issues before they cascade into your campaign performance.

4. Cross-team redundancy

If one team member’s browser has a session-specific issue (corrupted cookies, extension conflict, cached JavaScript), having a second person attempt the same edit can confirm whether the problem is local or platform-wide. During the January 2026 bug, the confirmation from multiple users on LinkedIn helped escalate the issue to Google faster than any individual support ticket could.

What this means (our take)

The PMax asset group editing bug was minor in duration — three days. But its implications are not minor. It exposed a single point of failure that every Performance Max advertiser shares: the web UI.

Here’s the uncomfortable reality. Google is pushing advertisers toward fully automated campaign types like PMax while simultaneously deprecating manual controls. In 2025, Google removed the ability to see search term-level performance data for PMax campaigns outside of limited reports. Asset-level performance data remains opaque — you see what wins impressions but not why. When the editing interface breaks on top of that opacity, you’re flying blind and unable to steer.

The fix isn’t to abandon PMax — the performance is too strong for that. As of August 2026, PMax campaigns consistently outperform standard Shopping and Dynamic Search Ads in conversion volume when given sufficient budget and conversion data. The fix is to treat the web UI as one of several interfaces to your campaigns, not the only one.

If your team only uses the browser-based Google Ads interface, install Google Ads Editor today. If you already use Editor, add API access as your next layer of redundancy. Three days without campaign control is survivable. A week-long outage during Q4, when every impression counts, would not be.

For a deeper look at how AI agents are changing campaign management beyond what the UI offers, read our piece on AI Agents for Google Ads Bidding.

What to do now

1. Install Google Ads Editor on your primary work machine. Download from the Google Ads homepage and authenticate with your MCC or individual account credentials.
2. Test an asset group edit in Editor — open a PMax campaign, modify one headline, and upload the change. Confirm it syncs correctly to the live campaign.
3. Bookmark the Google Ads Status Dashboard and follow Ginny Marvin on LinkedIn for real-time outage updates.
4. Document a backup workflow in your team’s operations manual: “If the web UI breaks, switch to Editor. If Editor breaks, use the API or Scripts.”
5. Review your PMax asset groups for freshness — if you haven’t updated creative in 90+ days, now is a good time. Use our Performance Max glossary for definitions and best practices.

FAQ

Sources

• Search Engine Roundtable — Google Ads PMax Asset Group Editing Bug (Jan 23, 2026)
• Search Engine Land — Google Ads bug blocks edits to Performance Max asset groups
• Ginny Marvin, Google Ads Liaison — Confirmation of resolution on LinkedIn (Jan 26, 2026)