Google Ad Creative and Targeting Updates: An Action Plan

If your Demand Gen video was approved down to the last line break, you now have a new reason to inspect the campaign settings: Google may place additional text over that finished creative. If your team manages Display & Video 360 through bulk files, you also have a new schema to accommodate before older workflows reach a hard support deadline.

These changes affect different products, but they create the same operational problem. The ad that gets served or the audience that gets targeted may no longer be defined only by the asset and configuration your team originally approved. You need an audit trail that covers Google’s transformations as well as your own inputs.

Know which control surface changed

There are two separate updates to manage. In Google Ads, Demand Gen campaigns can use existing text assets to generate messages that appear over video. In Display & Video 360, Structured Data Files v11 expand bulk targeting controls and change parts of the file structure used by automated workflows.

Keep ownership clear. Creative teams should decide whether a video can tolerate generated copy. Media teams should control the campaign setting. Marketing operations or engineering should own the SDF schema migration. One person should reconcile those decisions before launch; otherwise each team can complete its own task correctly while the final campaign is still wrong.

Audit Demand Gen overlays before the next launch

The Overlay on videos control sits under Asset optimization with Shorter videos and Resized videos. It has been observed as enabled by default, so silence is a decision: if nobody checks the setting, Google may add text to a video that your team considered complete.

Run a campaign-by-campaign creative check

1. Open each Demand Gen campaign and record the current state of Overlay on videos, Shorter videos, and Resized videos. Do not treat the account-level expectation as proof of the campaign-level state.
2. Review the beginning, middle, and end of every video. Mark areas occupied by burned-in copy, product details, logos, calls to action, prices, and required disclosures.
3. Review the existing text assets Google can use as overlay inputs. Remove or revise stale promotions, weak generic claims, mismatched calls to action, and language that does not belong in the campaign’s market.
4. Decide whether the video is suitable for an overlay test, requires a redesigned overlay-safe version, or should remain unchanged.
5. Record the decision with the campaign identifier, approver, setting state, date, and reason. This turns an invisible optimization toggle into an accountable creative choice.

A video with open visual space, little burned-in copy, and tightly governed text assets may be a reasonable candidate for a controlled overlay test. A dense product demonstration, carefully typeset brand film, localized creative, or video with disclosures is a poor candidate for unattended text placement. The relevant question is not whether overlays are useful in general. It is whether this particular composition and message can accept another layer without changing their meaning.

Do not confuse a generated overlay with closed captioning. The overlay draws from advertising text assets and can reinforce a benefit, promotion, or call to action; it does not necessarily reproduce the spoken content. If the video must be understandable without sound, assess captions and visual storytelling separately.

Use the narrowest control that matches your decision

You can turn off Overlay on videos by itself or use Disable all for the available video optimization features. Use the individual switch when your video can tolerate shortening or resizing but not added copy. Use Disable all only when the approved composition must not be altered by any of the listed optimizations.

Review the three settings independently. Turning off the overlay does not express a decision about shorter or resized versions. Equally, accepting alternate dimensions does not mean text can safely cover any part of the frame. Your approval record should state which transformations are allowed rather than reducing the decision to a vague yes or no on automation.

Account for the AI-edit label

When these optimization features modify an image or video, the served ad is labeled as created or edited with AI in the European Union, India, and New York state. That does not determine whether the creative is acceptable for your brand, but it does belong in the approval process. Tell brand, legal, and market owners which assets can be transformed and where the label may appear before they sign off.

Make SDF v11 a controlled migration, not a file swap

Display & Video 360 users can now download and upload SDF v11 directly in the platform. For a team that edits files manually, this is a template change. For a team that generates, validates, or ingests SDFs with code, it is a schema migration with targeting consequences.

The audience change needs an explicit exception. V11 supports lookalike inclusion and exclusion across ad groups except those under YouTube Ad Sequence line items. A bulk updater should identify those sequence line items before it writes audience fields. Do not treat a rejected or missing value as an unexplained upload anomaly when the campaign type itself is excluded.

Location logic also moves further into bulk management. Business Chain proximity targeting is now available in the line item format. That makes repeated setup easier, but it also increases the reach of a bad mapping. Confirm the intended business chain and destination line items in the generated output, then begin with the smallest reversible batch that can prove the rule works.

Use this v11 migration sequence

1. Inventory every workflow that reads, creates, validates, transforms, or archives an SDF. Include spreadsheets, scripts, data pipelines, naming rules, and reporting jobs.
2. Record the SDF version each workflow expects. Do not assume the version selected for export is also the version understood by an internal parser.
3. Download a clean v11 file and compare its headers, accepted values, and restrictions with your production template. Treat column names and structures as a contract; do not reconstruct unfamiliar fields from memory.
4. Update the audience mapping to handle lookalike inclusion and exclusion separately. Add a deliberate branch for YouTube Ad Sequence line items.
5. Update line-item logic for Business Chain proximity targeting only if the organization intends to use it. A new available field does not need to become a new default.
6. Inspect the four updated third-party YouTube vendor columns. They now incorporate reporting IDs and allow multiple vendor assignments, while separate reporting ID columns have been removed. Any script that expects those separate columns needs revision.
7. Test a limited upload and reconcile the accepted campaign structure against the intended file. Check line-item and ad-group counts, audience inclusions, audience exclusions, location settings, and vendor assignments.
8. Retain the last accepted file and a change log so the team can reconstruct the previous configuration if the upload produces an unintended change.

YouTube Instant Deals need a separate path. V11 includes columns and restrictions for their line items, ad groups, and ads, but Instant Deals remain in beta for allowlisted partners. They do not appear in downloaded SDFs and can only be uploaded through the dedicated creation workflow. A system that treats an export as a complete round-trip representation of the account will therefore have a known gap. Document that exception instead of letting the next export overwrite the team’s understanding of what exists.

There is also a firm planning horizon. SDF versions earlier than v10 are deprecated and will stop being supported in January 2027. At minimum, remove every pre-v10 dependency before that point. Moving directly to v11 gives you time to test the current fields and restrictions without turning a support cutoff into an emergency migration.

Test creative and targeting changes without confounding them

An overlay changes what a person sees. A lookalike inclusion, exclusion, or proximity rule changes who can see it. If you change both at once and results move, you will not know whether the message or the audience caused the difference.

1. Choose one question. For example: does an overlay-safe video with generated messaging improve the campaign’s business outcome, or does a particular lookalike configuration improve audience quality?
2. Define the primary metric before launch. Click-through rate can describe response to an ad, but it should not replace conversion rate, cost per qualified lead, acquisition cost, or another outcome that reflects the campaign’s actual purpose.
3. Keep the other major inputs as stable as the account allows. Budget, bid strategy, offer, landing page, audience definition, and creative can all obscure the effect you are trying to measure.
4. Log the exact configuration: overlay state, shorter-video state, resized-video state, SDF version, audience inclusions and exclusions, and proximity targeting.
5. Inspect the output as well as the metric. A performance lift does not make obscured product details, duplicated copy, an outdated promotion, or an unintended audience exclusion acceptable.
6. Set rollback conditions from your own baseline before the change. There is no universal performance threshold that fits every account, but brand obstruction, incorrect claims, lost exclusions, or spend directed to unintended locations should trigger immediate correction.

For overlays, your evidence should include a visual QA record and the downstream business metric. For SDF targeting, reconcile the uploaded configuration first, then evaluate reach, spend, and conversion quality for the affected audience or location. A clean measurement window cannot rescue an incorrectly configured campaign.

Keep the change log readable by someone outside the activation team. A useful entry includes the campaign, line item, or ad group identifier; the old and new value; who approved it; the hypothesis; the measurement period; and the rollback condition. This is especially important when a platform-generated creative treatment and a bulk-generated targeting rule can both influence the same result.

Key takeaways

• Demand Gen can generate video overlays from existing text assets, and the setting has appeared enabled by default. Audit it rather than assuming the approved master is the served creative.
• Overlay on videos, Shorter videos, and Resized videos are separate asset-optimization decisions. Disable only the transformations your creative cannot safely accept.
• Modified image or video assets receive an AI creation or editing label when served in the European Union, India, and New York state, so include that behavior in market and brand approvals.
• SDF v11 adds lookalike inclusion and exclusion for eligible ad groups plus Business Chain proximity targeting at line-item level. YouTube Ad Sequence line items are the stated lookalike exception.
• The v11 vendor-column changes and Instant Deal workflow can break assumptions in automated imports and exports. Test the schema and document incomplete round-trip cases.
• Support for SDF versions earlier than v10 ends in January 2027. Migrate while you still have room to validate small batches and correct the workflow safely.

Start with two inventories: every Demand Gen campaign whose video can be altered, and every workflow that touches an SDF. Assign an owner to each, record the current state, and make one controlled change at a time. That is how you gain the reach of automation without surrendering control of the message, audience, or spend.

References

• Search Engine Land — Google Ads adds automatic text overlays to Demand Gen video ads
• Search Engine Land — Google launches Display & Video 360 Structured Data Files v11 with expanded targeting