Demand Gen video text overlay automation is now explicitly available through Google Ads API v26.2. Released on 11 November 2026, the update adds an OVERLAY_TEXT_ON_VIDEOS setting for Demand Gen video responsive ads. It can place associated text assets, such as headlines, over video assets.
The key governance point is the default. For new Demand Gen video responsive ads created in API v26, the setting defaults to opted in. An integration that does not send an explicit choice can therefore create an ad with automated text overlays. Advertisers should review the saved setting and actual previews rather than assuming their uploaded video will run unchanged.
What Google Ads API v26.2 added
Google’s official API release notes describe the new automation type and its supported ad format. It is configured in the ad-level asset automation settings for a Demand Gen video responsive ad, not as a universal account or campaign control.
The asset automation documentation lists text overlay as enabled by default for this ad type starting in v26. In earlier API versions, the setting defaults to opted out for new ads. Queries made through earlier versions return an unknown automation type, so an old reporting layer may not label the setting correctly.
Version 26.2 is a minor API release. It does not require a new v26.2 endpoint path, but client libraries and typed internal models need definitions that recognise the new enum before an application can use it cleanly.
Who needs to review the change
The update is most relevant to agencies, advertisers and vendors that create Demand Gen video responsive ads through the Google Ads API. That includes custom campaign builders, bulk-upload services and internal tools that reuse templates across accounts. A marketer working only in the Google Ads interface should still review creative previews, but the API-version behaviour described here applies specifically to integrations.
Ask the tool owner which API version creates the ad and which version reads it back. If those paths differ, one service may enable the setting while another reports it as unknown. Also confirm whether the platform exposes the choice to marketers or silently inherits Google’s default.
Audit area
Question to answer
Required evidence
API version
Which version and client library create and read the ad?
Version inventory and tested library build.
Automation status
Is text overlay explicitly opted in or out?
Request payload and retrieved saved object.
Text source
Which associated headlines may appear on video?
Approved asset list and language mapping.
Creative quality
Does overlay text remain readable without covering key visuals?
Previews across supported placements and crops.
Performance
Does the automated treatment improve qualified outcomes?
Controlled test with conversion-quality review.
Why the default deserves attention
A successful API request is not enough. If an integration omits the automation setting, the created ad can still be valid while using a treatment that was never reviewed by the creative team. This is similar to any platform default that turns absence into an active choice.
Text overlays can help communicate the offer when people watch without sound, but they can also repeat baked-in captions, cover a product, introduce awkward line breaks or display a headline in the wrong creative context. Regulated claims, prices, dates and promotional terms require particular care.
Kayaar’s Google Ads AI labels guide explains why asset provenance and disclosure should be documented. Text overlay is an automation setting, not permission to skip brand, legal or factual review.
A practical implementation audit
1. Map creation paths. List every script, agency platform and bulk-creation tool that can create Demand Gen video responsive ads. Record its API version, client library, account scope and responsible owner.
2. Upgrade the schema safely. Add the new automation type to internal enums, storage and logs. Test how older-version readers behave. Do not convert an unknown enum to opted out, because that would hide the actual v26 setting.
3. Send an explicit status. Decide whether each template should opt in or out. Include the decision in the request instead of inheriting a default. Retrieve the created ad and confirm the saved status before it becomes eligible to serve.
4. Audit text assets. Review every associated headline for accuracy, length, language, offer dates and required qualifications. A headline that works beside a video may not work when placed inside it. Remove duplicate text that is already embedded in the footage.
5. Preview placements. Inspect vertical, square and landscape treatments where available. Check safe zones, contrast, subtitles, product visibility and calls to action. Kayaar’s YouTube creative repurposing workflow provides a useful process for adapting one message without forcing the same composition into every format.
6. Create an approval record. Save the source video, approved headlines, automation status, preview date and reviewer. If a headline or video changes later, trigger a new review rather than assuming the old approval still applies.
7. Monitor outcomes. Compare reach, views, engagement and qualified conversions against a suitable control. Do not credit or blame the overlay based on a before-and-after comparison that also changed audience, budget or bidding.
Creative checks before opting in
Start with a video that has enough negative space for text. Keep critical products, faces and demonstrations away from likely overlay areas and interface controls. Use concise headlines that still make sense when separated from the full description.
Check localisation deliberately. The text asset language should match the audience and landing page. Right-to-left scripts, long translations and mixed-language campaigns need real previews, not assumptions based on English layouts.
Client libraries recognise the new automation enum.
Every creation template sends an explicit status.
The saved ad is retrieved and compared with the request.
Headlines are approved for in-video presentation.
Previews cover relevant formats, languages and placements.
Performance tests isolate the overlay treatment.
For help reviewing a Demand Gen creative or API workflow, contact Kayaar with the ad format, tooling and business objective. Do not send API credentials or customer data through an unsecured form.
FAQs
What is Demand Gen video text overlay automation?
It is an ad-level setting that can place associated text assets, such as headlines, over Demand Gen video responsive ad videos.
Is video text overlay enabled by default in API v26?
Yes. Google documents it as opted in by default for new Demand Gen video responsive ads created in v26.
Does the setting apply to every Demand Gen ad?
No. Google documents this automation for Demand Gen video responsive ads, not every campaign or Demand Gen ad format.
What happens when an older API version reads the setting?
Google says versions earlier than v26 return an unknown automation type, so older reporting layers may need an upgrade.
Should advertisers automatically opt out?
No. Choose explicitly after checking brand rules, headlines, previews and test design; the right choice depends on the creative and objective.
