Display & Video 360 · Status at source date: Announcement
Display & Video 360 Structured Data Files v11 becomes generally available
Google announced general availability of Structured Data Files v11 for Display & Video 360 on 8 October 2026. Teams should review the schema and test their file workflows before migrating.

What changed
General availability announced
Google announced that Structured Data Files v11 is generally available for Display & Video 360 as of 8 October 2026. The release gives teams that rely on structured file workflows a new version to assess for configuration and maintenance work.
General availability supports evaluation of v11, but it does not by itself require every integration to migrate immediately. The announcement supplied here does not establish a common transition deadline for all existing SDF workflows.
Validate both directions
Begin with the v11 schema and identify the fields, definitions and assumptions used by existing processes. Test representative files in a controlled environment before changing production operations.
Validation should cover exports and imports. A structurally valid export may still affect downstream transformations, while an import may reveal dependencies on earlier field behaviour or validation rules. Include operational users as well as technical owners so that workflow effects are not missed.
Build evidence for migration
Retain sample files, validation results and unresolved differences. This provides a traceable basis for deciding when to migrate and makes later problems easier to diagnose. Seek current official documentation for any version-transition or deprecation requirements instead of inferring them from the launch notice.
The available evidence does not specify the v11 schema changes, compatibility guarantees, deprecation dates or deadlines for existing integrations. Those details remain necessary before a production cutover is scheduled.
Why it matters for advertisers
An SDF version change can affect repeatable DV360 operations and downstream processes. Early schema and file validation can reveal dependencies before migration timing becomes urgent.
What to check next
- Compare the v11 schema with the fields and transformations used in current workflows.
- Test representative exports, downstream processing and imports before changing production processes.
- Record validation results and confirm official transition guidance before scheduling migration.
Sources & contributor credit
- Reporting source · Google
Source reporting or observation date, not a universal launch date.
- Newsletter coverage · Paid Media Collective Week 41
Yoann Ferrand’s newsletter curation. Original reporting, account observations and visual credits are listed separately.
Original creator unverified
Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.


