Google has made Structured Data Files 10.1 generally available for Display & Video 360. The update may look like a CSV schema change, but every added or redefined column in a programmatic operation can affect campaign setup, quality assurance, reporting joins, and automation code. The new release adds fields for AI transparency on YouTube assets, digital out-of-home structures, creative mapping, and inventory modes.
This is not a change every Google Ads account needs to act on. It matters to teams that download or upload bulk files in DV360, or feed those files into an internal data pipeline. For enterprise advertisers, agency trading desks, and teams running campaigns across markets, the useful question is not simply whether to switch to 10.1 today. It is which version the existing integration assumes and how new columns change parsing and validation.
What changed?
Google's official July 30 developer announcement says SDF 10.1 is available to all DV360 users. The release exposes four areas that previously required more fragmented operational checks. It adds an AI transparency field for YouTube video assets. It expands file support for insertion orders and line items used in digital out-of-home. It makes relationships between creatives, ads, and ad groups easier to map. It also introduces accepted values for inventory mode.
The presence of a field does not mean every account receives the associated product capability at the same time. SDF is the bulk transfer schema for DV360 objects. If a feature is not supported for the account or campaign type, a new column does not create access. On the other hand, an old parser may misread a download when it does not expect a column, and an upload can fail when its template omits a required header.
The AI transparency field also sits within Google's broader advertising disclosure work. Completing a technical field is not a legal approval that automatically satisfies every market. Treat it as a platform signal. The creative production record, target market, and advertising-policy review remain separate responsibilities.
Who is affected?
The first group is media teams that routinely export SDFs, edit them in spreadsheets, and upload changes in bulk. The second is developers who connect the files to agency tools, data warehouses, or automated campaign builders. The third is the advertiser running YouTube, programmatic video, and digital out-of-home in one operating model.
The update is relevant to multinational retail, automotive, finance, tourism, and consumer brands operating in Türkiye. These businesses often combine a central campaign taxonomy with local market files. A version mismatch can cause more than a rejected upload. It can create incorrect creative mapping, missing inventory restrictions, or a misleading QA result.
What is confirmed and what remains uncertain?
SDF 10.1 is generally available, reference formats are published in Google's developer documentation, and versions older than v10 are on a deprecation path. Google's schedule says v9, v9.1, and v9.2 were deprecated on June 29, 2026 and are scheduled to sunset on January 28, 2027.
The uncertainty is account-specific and operational. Immediate access to each new field depends on campaign type and account configuration. The effect on an internal tool depends on whether that tool reads headers by name or relies on column order. Google is not promising a performance lift. Version 10.1 is an operational schema release, not a bidding or optimization model.
It would therefore be misleading to describe this as a “better-performing DV360.” The value is the ability to move newer product objects and disclosure data through a reliable bulk workflow.
What should teams do now? A seven-step migration check
1. Record the default SDF version at both partner and advertiser level. Do not assume interface downloads and API tasks use the same value.
2. Archive the schema of the latest working v9, v9.1, or v9.2 file. Do not move files containing personal data or sensitive campaign details into an uncontrolled test environment.
3. Download the same scope in v10 and, where available, v10.1. Compare added, removed, and changed columns by header name.
4. Make parsers independent of column position. Unknown fields should generate a clear validation record rather than silently shifting data into the wrong field.
5. Build separate cases for YouTube AI transparency, DOOH objects, creative-to-ad mapping, and inventory mode values. Test the empty-value behavior even for features you do not yet use.
6. Complete an export, edit, re-upload, and interface readback on a small reversible campaign before scaling.
7. Assign an owner and an internal deadline. Leave room to fix defects rather than using the January 28, 2027 sunset as the project date.
This process helps digital marketing and performance marketing teams share one version vocabulary with developers. A campaign name can look correct while a creative or inventory relationship fails underneath; that is not a risk for engineers alone.
Where should you act and where should you wait?
Start inventory work now if a custom integration depends on the v9 family. Prioritize 10.1 testing when you use DOOH, manage YouTube assets in bulk, or feed SDF data into a warehouse. Do not begin with a large production upload. Compare schemas and use a contained pilot.
Teams outside DV360 do not need a system change. If a new field is not visible in your account, do not write speculative values; verify access and the reference format. Do not treat the AI transparency column as a substitute for legal review. The platform schema and the market-specific disclosure decision are related but distinct.
Fark Studio perspective
SDF upgrades are often postponed as “an ad-tech task.” In practice, the file schema is the contract of the media operation. When a creative team renames an asset, a developer freezes an enum, and a local team uses an old template, the same campaign can split into three versions of the truth.
The sound migration is not a one-day conversion of every file. It connects the version, owner, test evidence, and rollback plan. That preserves measurement and QA while allowing the team to use new fields.
If your DV360 operation relies on manual or automated SDF workflows, you can plan a programmatic operations audit with Fark Studio. The goal is not to select a new version number; it is to keep campaign data consistent from production through reporting.
Sources
Google Ads Developer Blog, Launching Structured Data Files v10.1, July 30, 2026.
Search Engine Land, Google launches Structured Data Files v10.1 for Display & Video 360, July 30, 2026.
Google for Developers, Migrate to Structured Data Files v10, updated June 2, 2026.
Google for Developers, Structured Data Files deprecation schedule, accessed July 30, 2026.
