Google today added Display & Video 360 API, Structured Data Files, and Bid Manager API support to its existing Google Advertising and Measurement Community Discord server, while simultaneously publishing a significant overhaul of the DV360 API and SDF documentation. The announcement, posted on March 24, 2026, through the Google Ads Developer Blog, was authored by Trevor Mulchay of the Display & Video 360 API Team.

The two changes are separate in nature but clearly connected in intent: making the DV360 developer experience less opaque for teams building programmatic advertising automation at scale.

Discord over Google's own forums - a deliberate choice

The most striking element of today's announcement is not what was added to the documentation. It is the platform Google chose for community engagement. Rather than directing developers to Google's own public forums - or even its established Issue Tracker - the company is funnelling DV360 developer discussions into Discord, a platform originally built for gaming communities that has since evolved into a broad developer communication tool.

According to the blog post, Google's team "will be on this server regularly to interact with the Display & Video 360 community, answering questions and responding to feedback." A dedicated #announce-display-video-360 channel will serve as the notification layer for product updates.

Why Discord and not a Google-owned property? The answer lies partly in precedent and partly in adoption. Google launched the "Google Advertising and Measurement Community" Discord server in July 2025, initially covering Google Ads API, Google Analytics, Google AdMob, and Google Ad Manager. At launch, the server recorded 14,854 total members and 754 users online - numbers that suggest real traction before DV360 was even included. Today's announcement extends that existing infrastructure to cover the DV360 ecosystem rather than building a new channel from scratch.

Google's public forums, by contrast, are indexed by search engines and contribute to organic documentation. Discord conversations are ephemeral and largely unsearchable outside the platform itself. For a developer trying to find a solved problem six months later via a web search, Discord is objectively inferior to a public forum thread. The choice signals that Google is prioritising real-time engagement and friction reduction over long-term knowledge preservation - a trade-off that carries real implications for the broader developer ecosystem.

PPC Land covered the original Discord server launch in July 2025, noting at the time that the move "represents a departure from traditional support models that relied primarily on documentation and email-based assistance." Today's expansion to DV360 deepens that departure.

Does Discord have RSS? Not natively

A practical question for developers and marketing teams monitoring Google's product updates through news aggregators or feed readers: Discord does not offer native RSS feeds. The platform does not expose its channels or announcements as subscribable RSS or Atom feeds. There is no built-in mechanism to follow a Discord channel the way one can subscribe to a blog, a forum thread, or even a YouTube channel.

This is a meaningful limitation. Google's #announce-display-video-360 channel within the Discord server will carry product announcements - equivalent, in function, to the Google Ads Developer Blog. But unlike the blog, which publishes to a standard RSS feed that aggregators, feed readers, and automation tools can consume directly, the Discord channel is walled behind platform login and produces no machine-readable output.

Workarounds exist, but all of them require third-party tooling. Services such as MonitoRSS, Readybot, and RSS.app offer bots that can post RSS feed content into Discord channels - the reverse direction, pushing external feeds into Discord rather than extracting a feed from Discord. For teams that want to route Google's announcements from the Google Ads Developer Blog into the Discord server itself, that workflow is achievable through these third-party bots, which check for new items every 20 minutes on free tiers, with paid plans reducing that interval to as low as 2 minutes.

The inverse - exporting a Discord channel's content as an RSS feed for external consumption - is not natively supported and requires custom development or self-hosted solutions. Open-source projects on GitHub, such as discord-rss-bot, demonstrate that the technical capability exists, but none of these solutions are officially supported by Discord itself.

For developers accustomed to monitoring Google developer announcements through a feed reader - by subscribing to the Google Ads Developer Blog RSS feed, for example - the move of some communications to Discord introduces a friction point. Following the blog remains possible through standard RSS. Following the Discord channel requires being an active Discord member and monitoring the platform directly, or configuring a custom integration to bridge the gap.

This architectural difference matters precisely because the #announce-display-video-360 channel is positioned as a product update mechanism. If developers treat Discord as their primary source for DV360 API announcements, they accept a feed model that is less portable, less archivable, and less compatible with standard information management workflows than the blog format it partially supplements.

Google has not indicated whether it plans to mirror Discord announcements back to the blog, or whether some updates will appear exclusively on the Discord server. The blog post for today's announcement appeared on ads-developers.googleblog.com as normal. Whether that remains the case for all future DV360 product communications - or whether some updates begin to live only in Discord - is an open question that affects how developers should configure their monitoring workflows.

What the documentation overhaul actually changes

The documentation update is the more operationally significant of the two changes for most developers. According to the Ads Developer Blog post, the updated site introduces three structural improvements to how the DV360 API and SDF reference material is organized.

Task guides are the first new addition. These are step-by-step walkthrough documents designed to explain how to perform common operations within the API - creating line items, managing targeting, generating SDF downloads. Previously, developers had to piece together these workflows from reference documentation that described individual endpoints without necessarily explaining how they fit together in sequence. Task guides represent a move toward procedural documentation, which tends to reduce onboarding time for developers new to the platform.

Concept guides form the second new category. Where Task guides are operational, Concept guides explain the underlying logic and data models of the API - why things are structured as they are, how different resources relate to one another, what the architectural decisions mean for implementation. The DV360 API covers a substantial surface area. The API has been available since March 27, 2020, when v1 launched, and has accumulated considerable complexity across six years of updates, version migrations, and feature additions.

The third change is updated navigation that, according to the blog post, "highlights currently-supported versions and features of the API and Structured Data Files." This is a practical fix. The DV360 API has gone through multiple major versions - v1, v3, and v4 - with sunset dates that created real operational pressure for development teams. DV360 API v4 reached general availability in March 2025, and v3 was subsequently sunsetted on October 7, 2025. The July 2025 update removed support for SDF v6, which had itself been deprecated in July 2024. A navigation layer that makes version currency immediately visible should reduce errors caused by developers unknowingly referencing deprecated endpoints.

The Bid Manager API inclusion

Today's announcement also brings the Bid Manager API into the Discord server. This is worth noting separately. The Bid Manager API - historically also referred to as the DBM API - handles reporting and bulk operations within the DV360 ecosystem but is distinct from the Display & Video 360 API itself. Google sunset the DBM API v1.1 Line Item service in February 2021, redirecting those operations toward the DV360 API. The Bid Manager API has since remained focused on reporting. Its inclusion in the Discord channels alongside the DV360 API and SDF products creates a single support surface for developers working across all three interconnected tools.

SDF context: a format under continuous revision

The documentation update lands at a moment when Structured Data Files have been through substantial churn. SDF v7 launched in November 2023. SDF v7.1 followed in mid-2024, bringing TrueView video ad settings and terminology updates. SDF v8 arrived in October 2024 with Demand Gen integration. SDF v9.1 reached general availability in September 2025, with SDF versions 7.1, 8, and 8.1 facing deprecation by March 3, 2026 - a deadline that passed just weeks before today's documentation announcement.

The pace of change across SDF versions means developers who have not kept pace with the release notes may be operating on formats that no longer align with the current documentation. The updated navigation that surfaces currently-supported versions directly addresses this operational risk, even if it does not resolve the underlying challenge of maintaining compatibility across fast-moving format revisions.

Google also enforced EU political advertising declarations through SDF v9 from September 8, 2025, adding a compliance layer to SDF management that increased the cost of running outdated documentation.

Feedback mechanism built into the documentation

The blog post includes a specific instruction for developers: "If you have feedback on these changes or the content of any of the guides, please click the Send Feedback button at the bottom of any page in the documentation." This is a standard component of Google's developer documentation sites, but its explicit mention here suggests the team is actively soliciting input on the new structure rather than treating the update as finalized. PPC Land noted in its coverage of the Google Ads API Developer Assistant v2.0 in February 2026 that Google's recent developer tooling investments have consistently "responded to developer feedback" - a pattern today's changes reinforce.

What this means for marketing technology teams

For agencies and in-house teams running programmatic campaigns at scale through DV360, today's changes are primarily relevant to the engineering and technical operations layers rather than campaign managers. The Discord channels create a route for developers to escalate questions faster than support tickets and to monitor product changes through a dedicated announcement channel. The documentation restructuring reduces the ramp-up time for new developers joining teams that manage DV360 integrations.

The practical significance of having Google engineers "regularly" present in a Discord server should not be overstated. Availability on a chat platform does not equate to guaranteed response times or formal support commitments. The difference between this and official support is meaningful - Discord interactions carry no service-level agreement and may not produce auditable records in the way that formal support tickets do.

The RSS limitation compounds this. A team that previously monitored the Google Ads Developer Blog through a feed reader now faces a split: the blog remains the canonical source for formal announcements, while the Discord server carries real-time discussion and potentially informal product signals that do not appear in the feed. Managing both requires deliberate workflow decisions that were not necessary when all communication flowed through a single, indexable, subscribable source.

That said, the pattern across Google's advertising developer ecosystem is clear. The company is consolidating its developer community engagement onto Discord, and DV360 - its enterprise-grade demand-side platform - is now part of that architecture.

Timeline

Summary

Who: Trevor Mulchay of the Display & Video 360 API Team at Google, on behalf of the Google Ads Developer Relations function, authored the announcement. The changes affect developers and technical operations teams building integrations with the Display & Video 360 API, Structured Data Files, and Bid Manager API.

What: Two simultaneous updates - the addition of DV360 API, SDF, and Bid Manager API support to Google's existing "Google Advertising and Measurement Community" Discord server, and a structural overhaul of the DV360 API and SDF documentation introducing Task guides, Concept guides, and updated navigation highlighting currently-supported versions. Discord does not support native RSS feeds, meaning the new announcement channel is not subscribable through standard feed readers without third-party bots or custom integrations.

When: Announced on March 24, 2026, through the Google Ads Developer Blog by Trevor Mulchay of the Display & Video 360 API Team.

Where: The Discord server is accessible via Google's invite link. The updated documentation is hosted on the official Display & Video 360 API developer documentation site. The announcement was published on the Google Ads Developer Blog at ads-developers.googleblog.com.

Why: Google is extending the developer community infrastructure established with the July 2025 Discord server launch to cover its enterprise programmatic platform. The documentation overhaul addresses complexity accumulated through six years of API versioning, SDF format revisions, and feature additions. The choice of Discord over Google's own indexable forums prioritises real-time engagement at the cost of searchability, archivability, and RSS compatibility - a trade-off with direct workflow implications for development teams monitoring product changes through feed readers.

Share this article
The link has been copied!