Google is pulling the plug on its beloved developer support forums, and it’s a bigger deal than you might think. For years, these forums have been the go-to spot for developers to troubleshoot issues with Google Ads API, Ads Scripts, and Campaign Manager 360 API. But here’s where it gets controversial: starting January 28, 2026, Google will stop responding to new posts, shifting all support to official channels. While the forums will remain as read-only archives until later in 2026, this change is forcing developers to rethink how they solve problems.
Why the shift? Google claims it’s all about streamlining technical support, pushing developers toward official tools with better tracking and response workflows. But this is the part most people miss: by centralizing support, Google risks shrinking the vibrant, community-driven knowledge base that has been a lifeline for many. After January 28, replies to existing threads will create new email tickets, and developers will need to provide more detailed logs and diagnostics to speed up resolutions. This means more structured support but less of the informal, peer-to-peer problem-solving that many have come to rely on.
Where do developers go now? Google’s updated documentation points to these official channels:
- 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 support team via dcmapi-support@google.com.
What’s expected from developers? To expedite resolutions, Google urges developers to include comprehensive diagnostic details when filing tickets, such as request IDs, full logs, script names, execution logs, and error messages. For example, if you’re troubleshooting the Google Ads API, include the request ID and full request/response logs. This level of detail is new for many and could be a learning curve.
Is the community completely left in the dark? Not entirely. Google suggests developers join the “Google Advertising and Measurement Community” Discord server (http://goo.gle/ads-and-measurement-discord) for updates, events, and general discussions. However, this platform is not tied to official support, leaving some to wonder if it’s a true replacement for the forums.
The bottom line: Google’s move to standardized, direct support may streamline issue handling, but it could also diminish the rich, community-shared knowledge that has been a cornerstone for developers. Advertisers and developers alike will need to adapt quickly to avoid downtime and lost performance. But here’s the question: Is this shift a step forward in efficiency, or a step back in community collaboration? Let us know your thoughts in the comments—we’d love to hear how you’re preparing for this change.
Google’s Official Announcement: http://ads-developers.googleblog.com/2025/12/sunsetting-google-ads-api-google-ads.html
About the Author: Anu Adegbola, Paid Media Editor at Search Engine Land since 2024, brings over a decade of experience in digital marketing. From maximizing ROI to automating processes, Anu has been at the forefront of paid search and social media strategies. She’s also the founder of PPC Live and host of the weekly podcast PPC Live The Podcast. When not editing, she’s speaking at international events like SMX, brightonSEO, and HeroConf. Connect with her insights and stay ahead in the ever-evolving world of marketing.
Search Engine Land is owned by Semrush (https://www.semrush.com/). Our content is crafted by experts committed to delivering high-quality marketing insights.
