Tag: Ad Optimization

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.

Control layer	What changed	Main risk	First action
Demand Gen creative	Automatic text overlays can be generated from existing text assets.	Added copy can obscure the composition, repeat burned-in text, or conflict with the approved message.	Inspect the Overlay on videos setting and the text assets available to the campaign.
DV360 audience targeting	SDF v11 supports lookalike audience inclusion and exclusion across eligible ad groups.	A blanket bulk-edit rule can apply the wrong audience logic or mishandle an exception.	Add explicit inclusion, exclusion, and exception checks to the SDF workflow.
DV360 location targeting	Business Chain proximity targeting is available in the line item file format.	A bulk upload can extend location targeting to unintended line items.	Validate the business-chain configuration at line-item level before scaling it.
DV360 file automation	Vendor fields and selected YouTube campaign structures have changed.	Existing templates, parsers, and round-trip assumptions can fail or silently omit information.	Diff a clean v11 file against the production schema and test a limited batch.

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

A reviewer inspects a vertical video preview partly covered by blank translucent interface overlays before 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

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.
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.
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.
Decide whether the video is suitable for an overlay test, requires a redesigned overlay-safe version, or should remain unchanged.
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

Two specialists guide blank spreadsheet-like grids through validation checkpoints during a staged file-schema migration.

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

Inventory every workflow that reads, creates, validates, transforms, or archives an SDF. Include spreadsheets, scripts, data pipelines, naming rules, and reporting jobs.
Record the SDF version each workflow expects. Do not assume the version selected for export is also the version understood by an internal parser.
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.
Update the audience mapping to handle lookalike inclusion and exclusion separately. Add a deliberate branch for YouTube Ad Sequence line items.
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.
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.
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.
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.

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?
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.
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.
Log the exact configuration: overlay state, shorter-video state, resized-video state, SDF version, audience inclusions and exclusions, and proximity targeting.
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.
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

October 9, 2026

Google Ads AI Creative Previews and CTR Benchmarks for 2026

You have a set of polished AI-generated headlines in front of you, but no reliable answer to the question that matters: will enabling them improve the campaign, or simply attract more of the wrong clicks?

Use the AI Max preview and your clickthrough rate benchmark for different jobs. The preview is a pre-launch accuracy and positioning check. CTR is a post-launch response signal. When you keep those roles separate, you can test automation without mistaking plausible copy for proven performance.

Key takeaways

AI Max can preview up to 10 generated headlines and descriptions from a final URL before you enable text customization.
The preview shows possible messaging, not the exact assets that will appear in live auctions.
A 2.1% CTR is a 2026 blended benchmark for the first search-ad position, not a universal Google Ads target.
Placement, ad format, industry and the presence of an AI-generated search answer can materially change the benchmark you should use.
Do not approve AI creative on CTR alone. Accuracy, conversion quality and the business value of those conversions remain the decision criteria.

What the AI Max preview can actually tell you

Google Ads is adding a preview that can produce up to 10 example headlines and descriptions in approximately 30 seconds. You enter the campaign’s final URL, and Google AI uses that landing page to create the samples. You do not have to enable text customization first.

Where the option is available, you can find it under Asset optimization while creating a Search campaign or editing an existing one. It supports the languages already supported by text customization and most business categories, while adult content is excluded.

The useful question is not, “Do these ads sound good?” It is, “What does Google appear to believe this page is offering, to whom, and on what terms?” That shift turns the preview into a diagnostic tool.

A preview can help you notice:

Which benefits and product attributes Google treats as central.
Whether the landing page communicates a clear audience, use case and point of difference.
Whether important qualifications disappear when the offer is compressed into ad copy.
Whether the generated language fits your brand voice or drifts into generic advertising phrases.
Whether ambiguous page copy is being interpreted as a broader or stronger claim than you intended.

It cannot tell you which headline-description combination will serve for a particular query, whether the live system will generate different wording, or what CTR the campaign will achieve. Google describes the assets as examples; the exact previewed text is not guaranteed to serve.

That limitation changes the approval standard. You are not signing off on a fixed set of ads. You are deciding whether the page gives an automated system sufficiently accurate material from which to generate ads. A clean preview is encouraging, but it does not remove the need to inspect generated assets after activation.

Choose a CTR benchmark that matches the auction

CTR is clicks divided by impressions, expressed as a percentage. The arithmetic is simple; the comparison is not. A display campaign, a first-position Search ad and a local result appear in different contexts and reflect different kinds of intent. Comparing all three to one account-wide target will produce confident but misleading conclusions.

The 2026 figures below come from a meta-analysis covering 126 agency client accounts and published CTR datasets from August 4, 2025 through August 28, 2026. The results were weighted by dataset quality and normalized to U.S. query volume. They are useful external reference points, but they are not promises for an individual campaign, another country or a different auction mix.

CTR by ad type and placement

Ad type	Placement	2026 average CTR	How to use it
Search	Position 1	2.1%	Use only for the top search-ad position and remember that it blends search pages with and without AI answers.
Search	Position 2	1.4%	Compare with campaigns occupying a similar position mix.
Search	Position 3	1.1%	Do not treat the gap from position 1 as a creative problem by default.
Search	Position 4	0.8%	Check placement before diagnosing copy from the lower CTR.
Local Search	Local result	4.6%	Keep separate from conventional Search benchmarks.
Local Services	Left	2.6%	Compare within the same Local Services layout.
Local Services	Middle	2.3%	Account for the lower placement when evaluating the result.
Local Services	Right	2.0%	Use as a placement-specific reference, not an account target.
Product Listing Ad	Top eight	1.2%	Compare with other prominent product listings.
Product Listing Ad	Mid-page	0.55%	Do not compare directly with the top-eight figure.
Display	Across placements	0.093%	Judge in the context of a format often used for branding rather than direct click generation.
Video	Skippable	0.69%	Keep separate from Search and non-skippable video.
Video	Non-skippable	0.78%	Compare with the same video format and campaign objective.

The first-position Search benchmark needs one more qualification. The top ad averaged 1.8% on results pages containing an AI-generated answer and 3.4% on pages without one. The published 2.1% figure blends those environments.

That difference is large enough to change your diagnosis. If a campaign’s exposure shifts toward search pages with AI answers, CTR can fall even when the ad copy has not become worse. Conversely, a rise in CTR does not prove that newly generated assets caused the improvement if placement or search-page composition changed at the same time.

CTR for the first Search ad by industry

Industry creates another wide spread. The 2026 first-position Search averages ranged from 1.1% to 5.4% across the 19 reported industries:

Industry	CTR for position 1
Addiction Treatment	5.4%
Automotive	2.0%
Aviation	1.3%
CBD	2.8%
Construction	1.2%
eCommerce	2.9%
Entertainment	4.0%
Financial Services	2.5%
Higher Education & College	3.7%
Home Builders	2.5%
Home Services	3.0%
Hotels & Resorts	3.6%
HVAC Services	3.1%
Legal Services	2.3%
Medical Device	1.1%
Medical Practices	2.1%
Real Estate	2.7%
SaaS	1.8%
Solar Energy	2.4%

There is no defensible universal CTR target for AI Max-generated text in these figures. They benchmark ad formats, positions and industries, not previewed AI copy against human-written copy. If someone tells you that enabling text customization should produce a particular CTR, ask for a comparable test covering the same placement, market, query mix and conversion objective.

Use a three-level benchmark instead:

Start with your own like-for-like campaign history. Match the campaign, market, landing page, intent and approximate placement as closely as practical.
Use the closest industry figure to check whether your internal baseline is broadly plausible.
Use the ad-type and placement table to explain structural differences that creative changes cannot fix.

If your industry is absent, do not force a neighboring category into service because its label sounds similar. Use the placement benchmark as a rough external anchor and let your own campaign history carry more weight.

Audit the preview as a claims and intent test

A marketer uses a magnifying lens to compare abstract ad-preview cards with several possible landing-page destinations.

The preview begins with your final URL, so prepare the page before judging the output. Make the actual offer, intended customer, geographic scope, material conditions and primary distinction easy to identify. Resolve contradictory wording between the headline, body copy, pricing language and calls to action. Otherwise you are asking automation to clarify a page that has not clarified itself.

Save every previewed asset in a simple review sheet. Give each row fields for the generated text, intended angle, supporting landing-page language, risk level and decision. Then make four passes.

Check factual accuracy. Mark any invented feature, incorrect product scope, wrong location, unsupported comparison or material condition that has disappeared. One false claim is a stop signal; do not average it away because the other assets are acceptable.
Check intent. Write down the search need each asset appears to answer. If you cannot identify one, the wording is probably too generic. If it implies a broader offer than the landing page delivers, it may earn curiosity clicks that will not convert.
Check positioning and voice. Look for language that could belong to any competitor, inflated promises you would not publish elsewhere, or terminology your customers do not use. A grammatically clean headline can still weaken the reason to choose you.
Check destination continuity. A visitor should be able to find the advertised promise, product and relevant condition immediately on the destination page. If the ad requires the reader to reinterpret the page after clicking, the message is not aligned.

A red-yellow-green system keeps the decision concrete. Red means false, materially misleading or attached to the wrong offer. Yellow means accurate but broad, generic, ambiguous or inconsistent with your voice. Green means specific, supportable and continuous with the destination page.

Do not enable text customization while a red issue remains. If several samples make the same mistake, inspect the landing page before blaming the model. Repeated errors may indicate that the page leaves an important distinction implicit, although the model can also introduce an error that is not present on the page. Fix the underlying ambiguity where one exists, then run the preview again.

A single yellow asset is a monitoring item, not necessarily a rejection. Record the exact concern so that your live review has a testable condition: for example, “watch for language that presents the service as nationwide” is more useful than “keep an eye on brand fit.”

Run the live pilot without letting CTR make the decision

An analyst monitors two ad-testing streams using several unlabeled performance gauges, with click response shown as one signal among many.

Once text customization is enabled, treat the saved preview as a record of likely themes, not a production manifest. Continue examining generated assets because live messaging may differ from the examples.

Set up the pilot around one business question: can AI-generated text produce more qualified response without creating claim, positioning or destination-match problems? That question gives you a hierarchy for interpreting the data.

Record the starting configuration. Save the preview, final URL, activation date, existing CTR baseline and the conversion outcomes you will use. Without that record, later changes become difficult to attribute.
Limit simultaneous changes where practical. A new landing page, different targeting, altered bidding and AI-generated text introduced together will not tell you which change mattered.
Compare like with like. Review placement and query mix alongside CTR, and remember that AI-answer exposure can alter the click opportunity before the user evaluates your ad.
Read CTR with conversion rate and cost or value per conversion. CTR tells you that the ad attracted a click. It does not tell you that the click came from the right person or produced a worthwhile outcome.
Review the actual message. If a live asset makes an inaccurate or materially misleading claim, intervene immediately. You do not need to wait for a performance threshold before correcting an accuracy problem.

Use this interpretation grid when the numbers arrive:

Observed result	Likely interpretation	Next action
CTR rises and conversion quality holds or improves	The new message may be earning more useful attention.	Continue the pilot and monitor the live assets for message drift.
CTR rises but conversion rate or value declines	The message may be too broad, curiosity-driven or mismatched with the landing page.	Inspect the generated wording, search intent and destination continuity before celebrating the CTR gain.
CTR stays flat but conversion quality improves	The creative may be filtering for better-fit visitors rather than maximizing click volume.	Judge the result against the campaign’s business objective, not the external CTR average.
CTR falls while conversion quality improves	Fewer people are clicking, but those who do may be better qualified.	Compare the additional value per click with the lost volume before deciding.
CTR and conversion outcomes both decline	The change has no evident performance benefit in the observed campaign context.	Inspect placement and query changes, then disable or revise the test if the decline remains attributable to the new setup.
Any material accuracy failure	Performance metrics are no longer the primary issue.	Stop the problematic automation or asset exposure and correct the message.

Avoid importing a universal testing duration or click threshold. A high-volume local campaign and a low-volume B2B campaign do not accumulate useful evidence at the same rate. Make the decision when your campaign has enough comparable traffic to separate a persistent pattern from daily noise, and document what “enough” means before looking at the result.

Your next move is straightforward: preview one representative campaign, save and score every generated asset, write down the correct position-and-industry CTR reference, and define the conversion-quality guardrail before opting in. That gives AI Max a fair test without handing an attractive CTR more authority than it deserves.

References

October 8, 2026

AdMob Black-Screen Outage: What App Publishers Should Do
When people report that your app “freezes” immediately after a video ad, you need to answer two questions quickly: is your own release broken, and can you stop more users from entering the same dead end?

The documented AdMob failure can replace an interstitial video with a solid black screen and leave its close button unresponsive. It affects iOS and Android, and the only reported escape for the user is to force-close the app. Here is how to confirm the pattern, contain it, measure the damage, and restore the placement without making a rushed code change.

Know the boundary of the AdMob failure

The confirmed failure is narrow enough to guide your response but serious enough to justify immediate action. An interstitial video fails to render, the user sees a black screen, and the close control does not work. Reports cover both iOS and Android applications.

AdMob itself may remain accessible while publishers encounter error messages, high latency, or other unexpected behavior. At the reported stage of the incident, Google was investigating, had announced no estimated resolution time, and offered no workaround for the failed interstitial.

That boundary matters. The known issue concerns interstitial video ads; it does not establish that every AdMob format or every placement is failing. Do not disable unrelated inventory merely because it uses the same ad platform. Equally, do not dismiss the incident as an iOS view-controller problem or an Android rendering regression when the same symptom is appearing across both operating systems.

There is also an important distinction between a vendor workaround and publisher containment. Google may have no way for you to repair the ad after it becomes a black screen. You may still be able to prevent your app from requesting or presenting the affected placement through remote configuration, a feature flag, or an emergency release.

Confirm the pattern before changing your SDK or app code

A black screen is a symptom, not a diagnosis. Treat the AdMob incident as a strong lead, then collect enough evidence to distinguish it from your own navigation, lifecycle, or rendering bug.
1. Identify the exact trigger. Record the screen, user action, and interstitial placement immediately preceding the black screen. “The app went black” is not enough to isolate an ad failure.
2. Capture the environment. Preserve the app version, build number, operating system, device model, timestamp with time zone, and network condition. Ask support teams to collect the same fields from new reports.
3. Inspect the session sequence. Determine whether the app process remains active behind a full-screen ad surface, whether the close control appears, and whether tapping it produces any response.
4. Review your ad events. Look for the request, load, presentation, dismissal, and failure events your integration already records. Event names vary by SDK and implementation, so use your own instrumentation rather than assuming a callback was fired.
5. Test the path without the placement. If the next screen works when the interstitial is suppressed in a controlled environment, the evidence points toward the ad boundary rather than the destination screen.
6. Check both mobile platforms. Matching behavior on iOS and Android strengthens the case for a shared service or creative-delivery problem. A report from only one platform does not rule out the AdMob incident, but it does justify checking platform-specific code.
Use your existing test environment and approved ad-testing setup when reproducing the flow. An unsuccessful reproduction does not prove that production is healthy: ad delivery varies, and the affected video may not appear in every request.

Avoid upgrading, downgrading, or replacing the mobile ads SDK solely because the visible symptom resembles an integration bug. Those changes introduce a second variable and may not affect a service-side outage. First establish whether the failure aligns with the known interstitial pattern and whether suppressing that placement restores the user journey.

Contain the user trap at the placement level

Your immediate goal is not to recover every missed impression. It is to stop a full-screen dependency from making the rest of the app unreachable.
- Use a remote kill switch if one exists. Stop invoking the affected interstitial placement without disabling ad formats that are still working.
- Fail open at the gate. If the interstitial sits between a completed action and the next app screen, let the user continue without the ad while the placement is suppressed.
- Do not create an automatic retry loop. Repeatedly requesting another interstitial at the same transition can send the user back into the broken experience.
- Remove the placement from relaunch-sensitive paths. A person who force-closes the app should not immediately encounter the same interstitial after reopening it.
- Consider an emergency release when server-side control is unavailable. Keep the change narrow: bypass the affected placement rather than combining the response with an SDK migration or unrelated feature work.
- Reassess paid acquisition into an unavoidable broken path. If a high-traffic onboarding or conversion flow cannot bypass the interstitial, continuing to drive users into it may waste campaign spend and amplify abandonment.
Suppression has an obvious monetization cost, but leaving the placement active can cost the entire session. The outage can affect ad engagement and publisher revenue while also increasing user frustration and app abandonment. Make that tradeoff explicitly rather than allowing a revenue-protection default to decide it for you.

Give support teams a precise response they can use: “A video ad may display a black screen with a close button that does not respond. Close the app completely and reopen it. We are temporarily limiting the affected ad placement while the provider investigates.”

Do not promise that reopening permanently fixes the issue; force-closing only gives the user a way out of the current screen. Do not publish a resolution time that Google has not supplied. If you cannot suppress the placement, tell users where it occurs so they can make an informed choice about using that path.

Measure the blocked journey, then restore cautiously

Look beyond crash-free sessions

A trapped interstitial may not look like a conventional application crash in your monitoring. The user can leave by force-closing the app, so a healthy crash-free metric is not proof that the experience is healthy.

Build the incident view around the user journey: ad presentation, expected dismissal, arrival at the next screen, session termination, and subsequent reopen. Compare the affected period with your normal baseline, segmented at least by placement, operating system, and app version. Use your established timing baseline rather than inventing a new universal timeout during the incident.
- Count interstitial presentations that are not followed by the expected dismissal or next-screen event.
- Track exits and rapid reopens after an interstitial presentation.
- Review support tickets and app-store feedback for black-screen, frozen-ad, and unresponsive-close descriptions.
- Watch requests, impressions, engagement, and revenue by the affected placement; the outage may alter each metric differently.
- Preserve a timeline of configuration changes, releases, reports, and observed recovery so that later analysis can separate the outage from your mitigation.
Be careful with interpretation. A lower impression count after you suppress a placement is expected. A decline before suppression may reflect failed rendering or disrupted sessions, but the available incident information does not establish exactly how every AdMob reporting metric records the failure.

Require evidence before full restoration

Do not re-enable the placement merely because complaints slow down. Confirm that Google has marked the incident resolved, then validate the affected journey on both iOS and Android. Check that the video renders, the close control responds, the dismissal event arrives, and the user reaches the intended next screen.

If your controls allow it, restore the placement to a limited share of traffic first. Watch the same presentation-to-dismissal and next-screen signals used during triage. Expand only when those signals return to their ordinary baseline. If limited restoration reproduces the black screen, disable the placement again and preserve the new session evidence.

Key takeaways
- The known AdMob failure turns an interstitial video into a black screen with an unresponsive close button on iOS and Android.
- Force-closing the app is the only reported way for a user to escape the affected screen; it is not a permanent fix.
- At the reported stage, Google was investigating and had provided neither a workaround nor an estimated resolution time.
- Confirm the placement-level pattern before changing your SDK, then suppress only the affected interstitial where your controls permit.
- Measure dismissal and journey completion rather than relying on crash metrics alone.
- Restore the placement only after a confirmed resolution and successful validation on both mobile platforms.
Once the incident is behind you, add one durable control: every full-screen third-party placement should have a remotely operated off switch. The next provider failure should require a configuration change, not an emergency app release, before you can give users their app back.

References
- Search Engine Land – Google AdMob outage traps users on black screens with no way to close ads
October 8, 2026

How to Manage Google Ads Video Frequency Across Campaigns

Your video campaigns can each look controlled while your audience still feels overexposed. The blind spot is overlap: a person can qualify for several campaigns, so acceptable frequency inside each campaign can become excessive frequency across the account.

Google Ads is testing Video Campaign Groups for eligible Video and Demand Gen campaigns. The beta introduces group-level choices for increasing deduplicated reach or coordinating delivery around a frequency target. Used well, it can help you answer a practical question: are you reaching more of the intended audience, or repeatedly buying access to people you have already reached?

Campaign-level frequency can hide account-level saturation

Reach and frequency only make sense within a defined boundary. Reach represents the distinct audience exposed within that boundary. Frequency describes how often the reached audience was exposed on average. Change the boundary from an individual campaign to a collection of campaigns, and both measurements can change.

This matters when a brand-awareness campaign, a product campaign, and a Demand Gen campaign pursue overlapping audiences during the same period. Each campaign can report a reasonable result while the combined plan keeps returning to much of the same audience. Adding the individual reach figures will not reveal the true audience size because duplicated people can appear in several campaign totals. Averaging campaign frequency figures can be equally misleading because the campaigns may have different reach and impression volumes.

The problem is organizational as much as technical. Separate teams, agencies, product lines, or budget owners may optimize their campaigns independently. The audience does not experience those internal boundaries. It experiences the combined sequence of ads.

Before creating a campaign group, build a simple overlap map:

List the active Video and Demand Gen campaigns that could belong in the group.
Record each campaign’s business objective, audience, geography, schedule, creative message, and responsible owner.
Mark audience overlap as high, uncertain, or low. Treat uncertain overlap as something to investigate, not as an assumption of independence.
Identify campaigns that serve a different funnel stage or require deliberately different repetition. Keep those outside the group unless a shared group objective still makes sense.
Write the audience experience in plain language. If the plan sounds repetitive when described from the viewer’s perspective, campaign-level optimization is probably not enough.

Choose between broader reach and managed repetition

The beta presents two different strategic directions: increase campaign-group reach or set a campaign-group frequency target. Do not treat this as a routine setup choice. It tells Google what problem you want the group to solve.

Group direction	Use it when	What success should look like	What to watch
Increase campaign-group reach	Your upper-funnel campaigns compete for overlapping audiences and your priority is finding additional eligible people.	Deduplicated group reach expands without unacceptable deterioration in the business outcome or audience quality you use as a guardrail.	Do not confuse a larger reported audience with valuable incremental reach. Check whether the additional exposure still serves the campaign’s purpose.
Set a campaign-group frequency target	Repetition is intentional, but you want it coordinated across campaigns rather than produced independently by each campaign.	Group-level frequency moves toward the intended pattern while reach, delivery mix, and campaign outcomes remain acceptable.	A target is an optimization instruction, not proof that every person receives the same number of impressions. Do not describe it internally as a hard cap unless the interface explicitly defines it that way.

Reach optimization is usually the clearer choice when the central problem is duplication. If several upper-funnel campaigns address substantially the same market, a group-level reach objective gives the system a reason to look beyond people already reached elsewhere in the group.

A frequency target is more appropriate when repetition has a defined role in the plan. That might include maintaining brand presence or supporting a coordinated message over time. The target still needs a business rationale. Do not borrow a universal frequency number from another account. Audience size, campaign purpose, creative variety, buying cycle, and available budget all change what a sensible pattern looks like.

Treat your initial target as a hypothesis. Start from your own historical delivery and the point at which added exposure stopped producing enough additional value. If you do not have evidence for that point, use the group to learn before making a larger budget decision.

Build a campaign group around one coherent job

A campaign group should represent a shared audience-management problem, not merely a convenient folder. Campaigns can use the same channel while doing very different jobs. Combining them under one reach or frequency instruction can create a clean report but a confused strategy.

Confirm that Video Campaign Groups are available in your account and that the campaigns you intend to use are eligible. The capability is in beta, so do not design an account-wide process that assumes universal access.
State the group’s job in one sentence. A useful statement names the audience, the intended exposure pattern, and the business purpose.
Group campaigns by audience relationship and funnel role. Shared format alone is not enough.
Choose either reach expansion or frequency coordination based on the problem you identified. Do not select the setting first and invent the rationale afterward.
Capture a baseline for campaign reach, frequency, spend, delivery mix, and the outcome each campaign is meant to influence. Preserve the date range and reporting definitions so the later comparison is meaningful.
Keep major audience, creative, bid, and budget changes to a minimum during the initial evaluation. If several inputs change together, you will not know what caused the result.
Assign an owner for group-level decisions. Campaign owners should not independently undo the group’s strategy by changing their own settings without recording the change.

Keep campaigns with incompatible goals apart. A prospecting campaign seeking new audience coverage and a narrow remarketing campaign seeking deliberate repetition may need different exposure strategies. Forcing both into the same group can make the aggregate metric look healthy while weakening one campaign’s actual job.

Also separate the setting from assumptions about budget control. A group-level reach or frequency instruction does not automatically prove that budget, bidding, creative sequencing, or delivery priority will be coordinated in the way you expect. Rely on behavior you can observe in your account, not on what the feature name appears to promise.

Measure delivery changes, not just cleaner reporting

The important unresolved question is whether Video Campaign Groups will meaningfully coordinate delivery across campaigns or mainly provide aggregated reporting and deduplicated reach. Those are not equivalent benefits. Better reporting can expose waste, but only delivery changes can reduce that waste.

Evaluate the beta in three layers:

Group outcome: For reach optimization, examine deduplicated group reach alongside group frequency. For frequency optimization, compare observed group frequency with the intended target while watching what happens to reach.
Business guardrail: Keep the outcome that matters for the campaign visible, whether that is qualified site activity, conversions, brand measurement, or another objective already used by your team. A group metric should not improve at the cost of the campaign’s purpose.
Delivery diagnostics: Inspect how spend, impressions, reach, and frequency are distributed across the campaigns. An acceptable group average can conceal a campaign that dominates delivery or another that has effectively stopped contributing.

What you observe	What it may mean	What to do next
Deduplicated reach expands while group frequency becomes less concentrated	The result is directionally consistent with reduced overlap and broader delivery.	Confirm that the additional audience remains relevant and that the business guardrail has not weakened before increasing spend.
Group frequency moves toward the target, but a campaign dominates delivery	The aggregate target may be improving while the campaign mix becomes less useful.	Inspect audience overlap, budgets, bids, eligibility, and campaign roles before accepting the result.
Individual campaign reach totals look large, but deduplicated group reach is substantially smaller	The account has meaningful cross-campaign overlap.	Use the deduplicated view for planning and stop presenting summed campaign reach as the size of the audience reached.
Group reporting becomes clearer, but campaign delivery patterns barely change	The immediate value may be measurement rather than active coordination.	Use the visibility to restructure audiences or campaigns, but do not claim that automated optimization reduced wasted frequency.
The group metric improves while the business guardrail deteriorates	The system may be satisfying the exposure instruction at the expense of audience or outcome quality.	Hold expansion, diagnose the tradeoff, and revise the group membership or objective.

Maintain a change log while testing. Record campaign additions and removals, audience edits, creative launches, bid changes, budget changes, and eligibility interruptions. Without that record, a before-and-after comparison can assign credit to the campaign group for a change caused elsewhere.

Use cautious language when reporting results. A movement that is directionally consistent with better coordination is not the same as proof of incremental reach. If you changed several inputs at once or cannot see how delivery shifted, call the result inconclusive and refine the test.

Key takeaways

Manage frequency at the level where audience overlap occurs. Campaign-level averages can hide repeated exposure across the account.
Use group-level reach optimization when your priority is reducing duplication and reaching additional eligible people.
Use a group frequency target when repetition is intentional and needs to be coordinated across campaigns.
Group campaigns by shared audience, funnel role, and business purpose rather than by video format alone.
Judge the beta by observed delivery changes and business guardrails, not by a cleaner group report.
Treat reported improvement as preliminary when other settings changed at the same time or delivery coordination cannot be verified.

Your next move is to identify one coherent cluster of overlapping upper-funnel campaigns, document its current exposure pattern, and give the group a single measurable job. That limited rollout will tell you more than applying a frequency setting across the account and hoping the aggregate number improves.

References

Search Engine Land – Google Ads tests Video Campaign Groups for cross-campaign reach and frequency

October 6, 2026

How to Make AI-Assisted PPC Optimize for Real Profit

Your PPC dashboard can show a healthy return while the campaign quietly consumes the margin you meant to keep. The usual problem is not that automated bidding failed. It is that the bidding system was given revenue, lead counts, or convenient proxy values and asked to treat them as business value.

You can fix that without abandoning automation. Start by defining the economics outside the ad platform, translate them into usable conversion values and bidding limits, and then let AI control only the decisions it has enough reliable data to make.

Start with the profit floor, not the platform target

Coins pass through trays representing product, shipping, payment, service, and return costs before the remainder reaches a protected profit platform.

Revenue ROAS answers a narrow question: how much reported revenue did you receive for each unit of ad spend? It does not tell you how much money remained after the product, service delivery, transaction, fulfillment, return, and advertising costs attached to that revenue.

For a campaign whose conversion value represents revenue, the basic relationship is:

Break-even ROAS = 1 / pre-ad profit margin expressed as a decimal.

If the relevant margin is 15%, the break-even ROAS is about 6.67, or 667%. At that point, $6.67 of revenue produces about $1 of profit before advertising for every $1 spent on ads. The campaign has covered the advertising cost under that simplified model, but it has not created additional post-ad profit.

That distinction matters: 667% would be the economic floor in this example, not automatically a sensible operating target. A target ROAS is also a bidding instruction, not a guarantee that every order, day, or campaign will achieve that return.

If you want a defined post-ad contribution, build it into the calculation. Let m represent the pre-ad margin as a share of revenue and p represent the share you want to retain after ad spend. Your maximum ad-spend share is m – p, so the required ROAS is 1 / (m – p). This forces the profit requirement into the target instead of adding an arbitrary cushion to the break-even number.

Before applying that formula, settle four inputs with whoever owns the financial numbers:

Confirm what conversion value means. If it is revenue, a revenue-based margin formula can work. If it is already a profit proxy or weighted lead value, applying the same margin again will distort the target.
Define the pre-ad margin consistently. Record which costs are included. Shipping, returns, payment fees, and overhead can materially change true profitability, so a label such as average margin is not enough.
Choose the amount that must remain after advertising. Break-even may be useful for diagnosis, but it is not the same as the return the business needs.
Separate materially different economics. One average can conceal large differences among products, customers, and orders. Do not let high-margin sales make low-margin traffic look sustainable unless that blend is deliberate.

This calculation gives AI a boundary grounded in your business. It does not make the platform profit-aware by itself.

Give the bidding system values that survive a finance review

An automated bidder can optimize only the value and events it receives. If every order is reported as equally valuable, it cannot infer that one product leaves ample margin while another barely covers fulfillment. If every submitted form is called a lead, it cannot know which inquiries can become revenue.

For ecommerce campaigns

Choose one value architecture and keep its logic intact:

Revenue values with margin-based targets: Report actual revenue, group products or campaign portfolios with reasonably similar economics, and calculate the target from the relevant margin. This preserves the familiar meaning of revenue ROAS.
Profit-proxy values: Pass a value that already reflects the economics you want the bidder to favor. Once you do that, stop interpreting the resulting return as revenue ROAS and do not reuse a target calculated on the assumption that conversion value equals revenue.

The dangerous middle ground is to report revenue, use one blended margin across dissimilar products, and call the result profit optimization. That gives the automation a precise target built on an imprecise economic premise.

For lead-generation campaigns

Low-volume lead generation has a different problem: the final sale may arrive too late or too rarely to supply enough bidding signals. Accounts that cannot approach the working benchmark of about 30 conversions in 30 days can use carefully valued micro-conversions to expose progress through the funnel.

A commercial shipping funnel provides a useful illustration of the structure:

Those amounts are an example, not a template to copy. Your values should represent the relative economic worth of each stage. A form start is not $10 of booked revenue; it is a bidding signal. If starts are abundant and their assigned value is too generous, the system can hit its target by finding people who begin forms rather than prospects who become qualified opportunities.

Check three things before using a value ladder:

Whether each stage predicts a more valuable business outcome, rather than merely being easy to track.
Whether one person can trigger several stages and, if so, whether the cumulative value reflects your intended bidding logic.
Whether the final qualified, proposed, and closed outcomes return to the ad platform so earlier assumptions can be compared with reality.

When your sales system can provide lifecycle outcomes, send them back. Google and Microsoft support integrations with systems such as HubSpot for passing later-stage data into advertising workflows. The important part is not the connector itself. It is replacing a platform’s early proxy with the closest available version of actual customer value.

Micro-conversions can help campaigns using conversion-based bidding, Performance Max, or AI Max obtain earlier signals. They can also make performance worse when their values are detached from qualification and revenue. More data is useful only when the data teaches the system the right preference.

Choose how much control AI gets, one decision at a time

A marketing analyst oversees a modular advertising console where some control units are automated and others remain under human control.

You do not need one account-wide answer to whether you trust AI. Treat trust as permission granted for a specific job. A practical operating model separates AI-informed, AI-assisted, and AI-delegated work.

Operating level	What AI does	What you retain	Gate before expanding
AI-informed	Surfaces search-term, variant, forecasting, or creative insights	You choose and apply every campaign change	The insight maps to a measurable business problem
AI-assisted	Runs a selected task such as bidding or asset generation	You define value, budget, scope, exclusions, and review criteria	Tracking is reliable and the task has enough useful signal
AI-delegated	Optimizes a bounded task end to end	You monitor economics, data quality, and exceptions	A controlled test beats the existing method on business outcomes

This model prevents a common mistake: treating automated bidding, generated creative, and automated reporting as one indivisible package. They solve different problems and deserve separate permissions.

Bidding needs signal density and economic constraints

Bidding is often the easiest task to automate because the system can make more auction-time decisions than a person. It still needs enough useful events. Manual bidding can remain reasonable for low-volume campaigns and narrow industries where sparse conversion data gives automation little to learn from.

Budget can become a hidden data constraint. One practical setup check uses a budget of at least 10 times the expected cost per click, based on the need to obtain roughly 10 engagements before depending on a conversion rate better than 10% for nonbranded search. Treat that as a diagnostic, not a universal spending rule. If the economics cannot support that traffic, changing the bid strategy will not repair the underlying volume problem.

Search terms show where automation is buying growth

Use the matched-by view in search-term reporting to inspect how often a keyword enters auctions through close variants. A high share of stable, cost-effective variants can indicate a useful auction entry point. Large swings in variant mix and bid cost can mean that the same keyword is pulling the campaign into materially different auctions.

The action is not necessarily to bid on every variant. Choose the keyword or target that gathers enough relevant demand to produce learning, then exclude or restructure traffic that has a different economic purpose. Consolidation helps only when the combined searches deserve the same value signal and target.

Creative and reporting still need human definitions

AI-generated assets can increase the number of messages and placements available to a campaign. You still own brand fit, factual accuracy, offer terms, and the landing-page promise. A bidding system cannot compensate for creative that attracts the wrong intent.

Reporting has a similar division of labor. Automation can assemble platform metrics, but you must translate them into revenue quality, margin, sales progression, and post-ad contribution. A report that ends at platform ROAS is incomplete when the decision in front of you is whether to invest more money.

Run one test and judge it on post-ad contribution

You do not have to delegate the whole account to learn whether automation can improve it. Compare the automated approach with the current strategy in a bounded campaign or portfolio where you can keep the economics and tracking definitions stable.

Write the baseline before changing anything. Record spend, reported revenue or lead value, realized margin, qualified outcomes, and post-ad contribution. If some figures arrive later, identify that lag.
State the hypothesis. Examples include finding more conversions above the profit floor, improving qualified opportunity volume within budget, or preserving contribution while increasing scale.
Change one layer of control. Test bidding automation without simultaneously redefining every conversion, rebuilding all creative, and widening targeting. Otherwise, you will not know what caused the result.
Freeze the value definitions during the comparison. If a tracking correction is unavoidable, mark the break and avoid treating the periods as directly comparable.
Watch the traffic and outcome mix. Inspect search terms, product mix, funnel stages, and closed outcomes rather than accepting an aggregate return at face value.
Expand only after the business metric improves. A platform target being met is not sufficient if margin mix, lead quality, or total contribution deteriorates.

Read combinations of metrics, not isolated wins:

ROAS rises while post-ad contribution falls: inspect the product or customer mix and confirm that reported value still maps to the margin used in the target.
Conversion volume rises while qualified outcomes fall: reduce the influence of weak micro-conversions and return later sales stages to the platform.
Return per conversion rises while total contribution falls: the target may be restricting volume so severely that efficiency improved but the business result did not.
Volume and post-ad contribution improve together: broaden the test carefully while keeping the same value definitions and monitoring for mix changes.

If it appears in your account, a Google Ads beta can translate an average profit margin into a suggested Target ROAS. It can also show weekly estimates for clicks, revenue, ad spend, and total profit as you change the target. Use those figures for scenario planning before applying a setting, not as evidence that the campaign will deliver the estimate.

The calculator assumes that the reported conversion value is revenue and that the supplied average margin represents the campaign well. It does not directly make Google Ads optimize bids for profit. Your value design, segmentation, cost completeness, and later outcome imports still determine whether the target represents the business you actually have.

Key takeaways

Calculate a break-even ROAS from the pre-ad margin when conversion value represents revenue, then add the post-ad contribution the business needs.
Do not apply a revenue-based Target ROAS formula to conversion values that already represent profit proxies or weighted lead values.
Use micro-conversions only when their relative values reflect progress toward qualified revenue, and replace proxies with offline outcomes when possible.
Grant AI control by task: insight first, selected automation second, and end-to-end delegation only after a bounded test.
Judge automation on post-ad contribution and outcome quality, not platform ROAS or conversion count in isolation.

Your next step is small: take one active campaign, write down what its conversion value actually represents, calculate its economic floor, and compare that floor with the target now in the platform. Any gap you find is the first profitability problem to solve before asking AI to spend more.

References

October 6, 2026

Google Demand Gen View-Through Attribution: What Changed

If view-through conversions in a Demand Gen campaign move while spend, clicks, and downstream sales or leads look ordinary, do not assume the campaign suddenly became more or less effective. The reporting method itself may have changed underneath your benchmark.

Google has lowered the threshold that a Display ad within Demand Gen must meet before a later conversion can receive view-through credit. That distinction matters whenever you evaluate creative, calculate performance, move budget, or report results across the transition.

Key takeaways

The change is limited to Display ads within Demand Gen campaigns. It is not a blanket redefinition of every Demand Gen ad view.
The qualifying event is moving from an Active View-based view to a rendered ad impression.
Under the new definition, an impression can qualify when at least one pixel of the ad appears onscreen, even momentarily.
The conversion event is not being redefined. Google is changing which preceding ad views can receive credit for it.
A rise in view-through conversions may reflect broader attribution eligibility rather than stronger advertising performance.
Keep pre-change and post-change benchmarks separate, and require corroborating evidence before changing budgets or performance targets.

The attribution gate changed, not the conversion event

A view-through conversion, or VTC, connects a conversion to an eligible ad impression rather than to a click on that ad. Two events therefore matter: a person converts, and an earlier impression qualifies to receive view-through credit.

Google is changing the second event for Display ads inside Demand Gen. The old method used Active View and its viewability standards to decide whether an impression was sufficiently viewable. The new method uses a rendered ad impression, which has a lower qualification threshold.

Measurement question	Active View method	Rendered-impression method
What qualifies the preceding ad exposure?	An impression that satisfies Active View viewability criteria	An impression with at least one pixel onscreen for any amount of time
How demanding is the qualification gate?	Higher	Lower
What happens to the conversion event itself?	No change from this update	No change from this update
Which campaign inventory is covered?	Display ads within Demand Gen campaigns

Do not fill in the missing Active View criteria from memory or apply a familiar viewability threshold from another report. You do not need a percentage or duration to interpret this update correctly. The decision-relevant fact is that one onscreen pixel, however briefly displayed, can now make the impression eligible under the rendered-impression definition.

Google’s stated reason is measurement consistency across Demand Gen inventory. That may make reporting conventions more uniform inside the campaign type, but consistency across inventory does not create continuity across time. A VTC reported under the old rule is not methodologically identical to one reported under the new rule.

The announced transition is automatic for eligible campaigns, with no campaign-setting change required from advertisers. Your immediate job is therefore to protect reporting continuity, not to reconfigure campaign delivery.

Why the same campaign can report more view-through conversions

Think of VTC attribution as a gate. Under the earlier method, an impression had to pass Active View’s viewability test before it could participate in view-through attribution. Under the new method, merely rendering one pixel onscreen can open that gate.

Lowering the gate can enlarge the pool of impressions eligible to receive credit. If people in that larger pool later convert, more conversions may be classified as view-through conversions even when the campaign did not generate additional purchases, form submissions, or other underlying conversion events.

This does not mean every affected campaign will report an increase. Delivery, audience mix, spend, conversion lag, and actual customer behavior can all move at the same time. The update supplies a plausible measurement explanation for a change in VTCs; it does not predict the size or direction of every account’s result.

The more important distinction is between attribution and incrementality. A VTC tells you that the platform connected an eligible impression with a later conversion under its rules. It does not, by itself, prove that the impression caused a conversion that would otherwise never have happened. A broader eligibility rule makes that distinction more important, not less.

The definition can also change calculated KPIs. If an internal cost-per-acquisition calculation divides spend by a platform-attributed conversion count, additional VTC credit can make CPA appear lower. If a return calculation includes value assigned to those VTCs, reported return can rise. The arithmetic may be correct while the apparent improvement is methodological rather than commercial.

Use corroborating signals before changing budget

A balanced decision mechanism receives signals from an ad impression, a click, a conversion, and a stack of budget coins.

Do not judge the transition from the VTC column alone. Compare that movement with signals that do not depend on the revised view definition: clicks, conversion paths involving clicks where separately available, qualified leads, completed orders, revenue, and other outcomes recorded in your own business systems.

Pattern you observe	What it can mean	What to do next
VTCs rise while clicks and independently recorded outcomes stay flat	The broader view definition is a strong candidate for at least part of the increase.	Do not increase budget from the VTC movement alone. Annotate the methodology break and inspect the affected Display inventory.
VTCs, click-associated results, and independently recorded outcomes all improve	There may be a real performance gain, although the definition change can still contribute to the VTC increase.	Base the decision on the corroborating outcomes and a post-change benchmark, not on the full VTC difference.
VTCs stay broadly stable	The practical effect may be small for this campaign or masked by other changes.	Keep the reporting annotation. Stability does not make the pre-change and post-change methods identical.
VTCs decline	The lower eligibility threshold does not explain the decline by itself.	Investigate delivery, spend, audience mix, conversion lag, tracking, and business outcomes before assigning a cause.

This check is especially important for automated spreadsheets, dashboards, scorecards, and budget rules that consume an attributed conversion total. A methodology-driven increase can silently trigger a recommendation to scale, make a target appear easier to reach, or make a post-change creative look stronger than a pre-change control.

Pause those conclusions, not necessarily the campaign. The campaign may be performing well; the point is that this particular before-and-after comparison can no longer establish why.

Build a clean reporting bridge across the rollout

Two separate data platforms in muted and bright colors are connected by a two-lane illuminated bridge across a rollout boundary.

You cannot recover comparability by pretending the definition stayed constant. You can preserve decision quality by treating the rollout as a measurement break and documenting it explicitly.

Identify the affected slice. List the Demand Gen campaigns containing Display ads. Do not apply the same warning indiscriminately to unrelated campaign types or to every format inside Demand Gen.
Preserve the old baseline. Save the last available pre-change reports with spend, impressions, clicks, VTCs, attributed conversion value where used, and independently observed leads or sales. Keep the raw export rather than only a chart or percentage change.
Mark the methodology break. Add the change to dashboards, recurring reports, experiment logs, and client or leadership notes. If you do not have a confirmed account-level cutover date, label it as an estimated transition period instead of inventing a precise date.
Separate the reporting eras. Calculate post-change VTC rates, CPA, return, and targets from post-change data. Retain the earlier benchmark for historical context, but do not blend the two periods into one continuous trend line without a visible warning.
Keep the comparison conditions honest. When reviewing periods on either side of the change, account for spend, delivery, audience mix, campaign edits, conversion lag, and changes in the underlying business. The definition shift is one variable, not permission to ignore the others.
Require an independent decision signal. Before increasing budget or declaring a winning creative, look for support from clicks, qualified leads, orders, revenue, or an appropriately designed experiment. The corroborating metric should not rely on the newly broadened view threshold.

Suggested reporting note: View-through attribution eligibility for Display ads in Demand Gen changed from an Active View-based definition to a rendered-impression definition. Post-change VTC results are not directly comparable with the earlier baseline.

Avoid creating a blanket adjustment factor to make old and new VTC totals look comparable. No universal uplift amount is provided, and the effect can vary with each campaign’s delivery and conversion behavior. Multiplying historical results by an assumed correction would replace a known methodology break with an invented one.

The rollout was described as automatic over a period of weeks, so do not assume every account changed on the same day. For agencies or teams combining several accounts, keep the transition status at the account or campaign level until you can justify a shared post-change baseline.

Make the next performance decision on the new baseline

The safest immediate move is simple: add the methodology note to your recurring Demand Gen report, split the VTC trend at the transition, and check every budget recommendation against at least one outcome that does not depend on view-through eligibility.

Once you have enough post-change data for your normal buying and conversion cycle, set fresh benchmarks under the rendered-impression definition. You can still use VTCs as an attribution signal. Just stop asking the old baseline to answer a question measured under a new rule.

References

Search Engine Land – Google changes view-through conversion reporting for Demand Gen Display ads

October 5, 2026

How to Diagnose and Fix Google Ads Destination Disapprovals
Your landing page opens normally, yet Google Ads says the destination isn’t working. That apparent contradiction is the clue: the problem may not be the page you see. It may be the exact URL in the ad, a tracking hop, a deep link, a redirect, an access rule, or the response served specifically to Google AdsBot.

The fastest route back to a working campaign is to trace the complete destination path as a new, unauthenticated visitor and as Google AdsBot would encounter it. That turns a vague disapproval into a specific URL, response, or configuration problem.

Key takeaways
- A page loading in your browser does not prove that Google AdsBot can load it.
- Test the exact final URL, tracking URL, redirect chain, and deep link used by the disapproved ad.
- The terminal landing page should return HTTP 200 without requiring authentication.
- Look for 403, 404, and 500 responses as well as DNS failures, timeouts, malformed responses, redirect loops, private IP addresses, and unfinished pages.
- If Google Ads reports an invalid final URL during campaign setup, verify that a required asset group exists before changing a working landing page.
Start with the request Google actually evaluates

Do not begin by typing your homepage into a browser. Begin with the exact destination attached to the disapproved ad. Copy the complete value, including the protocol, hostname, path, query parameters, and any tracking information. A homepage can work perfectly while a campaign-specific path returns an error.

Think of the destination as a chain rather than one page:
<!– wp:list {
October 1, 2026

ChatGPT Ads Strategy: A Practical Framework for Adoption

You are probably not deciding whether ChatGPT Ads are interesting. You are deciding whether they deserve budget, which campaigns should fund the test, and how you will know whether the channel is producing customers rather than curiosity clicks.

The sensible answer is neither a full commitment nor a wait-and-see posture. ChatGPT advertising has enough reach to justify a controlled test, but not enough established practice to justify treating it like a mature replacement for paid search. Your advantage comes from learning the channel without putting proven acquisition at risk.

Give ChatGPT Ads a specific job in your channel mix

ChatGPT Ads moved beyond novelty quickly. Six months after launch, 43% of ad-eligible ChatGPT users in the United States had seen an ad. The channel had also reached a $1 billion annualized revenue run rate and attracted tens of thousands of advertisers.

Those numbers establish adoption, not effectiveness for your business. The underlying data included more than 98,000 ads and 8,000 landing pages, with a U.S. collection of more than 95,000 ads from over 500 advertisers between April 1 and August 16. That is a substantial early view of advertiser behavior, but it remains observational evidence from a channel whose auction, formats, and user habits are still developing.

Start by assigning the channel one clear role. The best initial role is usually incremental acquisition: reaching a user whose active conversation reveals a relevant need, while leaving your validated search and social programs intact. Google still carries significantly more advertising volume, so moving core search budget before ChatGPT proves comparable business value would exchange known performance for an uncertain learning curve.

You are ready for a pilot when all of the following are true:

You have a product, service, or offer that already converts through a measurable digital path.
You can ring-fence an experimental budget without interrupting campaigns that reliably produce revenue or qualified leads.
You can create copy specifically for conversational use cases instead of importing a complete Google or Meta campaign unchanged.
You have feature, product, or pricing pages that can receive high-intent traffic without a redesign.
You can track the business outcome after the click, not just impressions and click-through rate.

Delay the pilot if you need a new channel to rescue weak unit economics, cannot distinguish qualified conversions from raw form submissions, or have no capacity to produce and evaluate creative variants. A developing platform magnifies those weaknesses; it does not solve them.

Keep paid placement separate from your AEO and GEO reporting as well. ChatGPT ads remain separate from ChatGPT’s answers. Buying an ad is therefore not evidence that your brand is being cited, recommended, or represented accurately in an organic answer. Paid acquisition and AI-search visibility can support the same business goal, but they are different surfaces with different measurement.

Build campaigns around conversational intent, not keyword lists

Three shoppers explore, compare, and select generic products along a pathway connected by blank speech-bubble shapes.

A search ad usually responds to a compact query. A ChatGPT ad can appear beside a conversation containing a problem, constraints, comparisons, objections, and signs of purchase intent. That richer context changes the creative brief.

Ad selection can use the context and intent of the conversation, the landing page, the creative, and context hints supplied by the advertiser. Treat those elements as one system. If the use case implied by your creative conflicts with the destination page, adding more variants will only distribute the mismatch more widely.

Write a campaign brief in this order:

Conversation use case: describe what the person is trying to accomplish, such as comparing plans, checking whether a feature fits a requirement, or understanding the cost of an option.
Decision stage: state whether the person is exploring the problem, validating a shortlist, or preparing to act.
Immediate question: write the question your ad must answer or help resolve at that moment.
Promise: identify the useful next step you can honestly offer, without pretending the ad is part of the assistant’s answer.
Proof: choose the product detail, capability, price information, or other evidence that supports the promise.
Destination: send the click to the page that completes that exact thought.

This process prevents a common failure: targeting a relevant conversation with generic brand copy. Relevance is not simply being in the right category. Your message must connect the user’s current task to a concrete next action.

Native creative is already a distinguishing behavior among active advertisers. Leading advertisers created 98% new copy for ChatGPT instead of recycling copy from other platforms. Advertisers with more creative variations also tended to capture more impression share, although no fixed number of ads emerged as the correct target. Half of the top 10 advertisers were running more ads on ChatGPT than on Meta.

Do not read that as an instruction to maximize asset count. It is a reason to build a controlled variation system. Create a matrix with conversation use case on one axis and message angle on the other. An angle might emphasize a feature, pricing clarity, suitability, or the next action. Every variant should have a named hypothesis, so you know what you learned when performance changes.

For the cleanest initial test, compare ChatGPT-native copy with your best imported baseline while keeping the offer and landing page constant. If the native version wins on meaningful downstream outcomes, test the next variable. Changing the audience logic, message, offer, and destination simultaneously may produce a winner, but it will not tell you why it won.

Keep the landing-page plan deliberately narrow

You do not need a new microsite before you can learn anything. Feature, pricing, and product pages are the most common destinations, and most advertisers use five or fewer landing pages. Existing high-intent pages are the practical place to begin.

Choose the destination by message match, not by internal importance. A pricing promise belongs on a page where the visitor can understand pricing. A feature claim belongs on a page that explains the feature and its relevant constraints. A product comparison message needs a destination that helps the visitor evaluate the choice. The homepage should not be the automatic fallback simply because it represents the whole brand.

Audit each candidate page against the ad before launch:

The opening screen continues the promise made in the ad instead of forcing the visitor to rediscover the topic.
The relevant product, feature, or pricing information is easy to find without navigating through unrelated sections.
The primary action matches the visitor’s likely stage, whether that is viewing plans, starting a purchase, requesting a demonstration, or contacting the business.
The page provides enough evidence to evaluate the claim made in the creative.
Campaign parameters distinguish ChatGPT traffic, creative, use case, and destination in your analytics.
The conversion event passes through to the system where revenue or lead quality can be evaluated.

Five landing pages is an observed pattern, not a recommended quota. Use fewer if one page serves several tightly related messages without becoming vague. Build a dedicated page only when an existing destination cannot continue the ad’s promise cleanly or when isolating a distinct offer is necessary for measurement.

This restraint matters because an oversized page plan creates two problems at once. It consumes production time before you know which conversation use cases deserve investment, and it spreads early conversion data across too many destinations. Start concentrated, identify where the signal is real, and then build around demonstrated gaps.

Measure the pilot as a decision system, not a traffic report

An analyst observes light particles moving through a transparent series of checkpoints toward a final outcome block in a tabletop testing apparatus.

Click-through rates have doubled since the channel launched. That indicates improving interaction as the platform and advertisers learn, but a relative increase is not an account-level forecast. It does not tell you what acquisition cost, conversion rate, lead quality, or revenue your campaign will produce.

Before spending, write down the decision the test is meant to support. Define the primary business outcome, your existing acquisition ceiling for that outcome, the attribution window you will use, and the minimum tracking quality required to trust the result. Use the same conversion definition as the adjacent channel you intend to compare against. Otherwise, a cheap ChatGPT lead and a qualified paid-search lead may look equivalent when they are not.

Read the funnel in sequence

Do not optimize every metric in isolation. Read each signal as evidence about a different part of the system:

Observed pattern	Likely issue to investigate	Next action
Eligible delivery but weak click-through	The use case, opening message, or value proposition may not fit the conversational moment.	Revise the intent-to-message pairing before changing the landing page.
Clicks but weak on-page engagement	The page may not continue the ad’s promise clearly.	Align the opening content and primary action with the creative while holding the audience logic steady.
Conversions but poor lead quality or revenue	The promise may attract the wrong buyer, or the conversion event may be too shallow.	Tighten the claim and context hints, then evaluate a deeper business outcome.
Acceptable economics across distinct creative and use-case combinations	The result may be durable enough for controlled expansion.	Add an adjacent use case or creative angle while preserving the winning combination as a control.

Treat conversational timing as a variable

Ads appearing in the first few turns of a conversation produce the strongest click-through rates and impression share. Conversations can continue well beyond those exchanges, so later placements still represent a longer tail of opportunity.

The important distinction is between an observed performance pattern and a placement control. Do not promise an early-turn strategy until you have confirmed which timing controls and reporting fields are actually available in your account. If conversation-stage reporting is available, segment it. If it is not, avoid attributing a result to timing that you cannot observe.

Early-turn creative should make the value of the next step immediately legible because the user’s requirements may still be broad. A later-stage message can be more specific when the surrounding context indicates comparison or validation. Keep those hypotheses separate in your campaign naming so a blended average does not conceal the difference.

Set promotion and stop rules before the launch

Promote the pilot toward a recurring budget only when conversion quality and acquisition economics meet your existing standard across distinct creative and use-case combinations. Rising CTR alone is not enough. Neither is one unusually valuable conversion that distorts a small sample.

Pause and diagnose when tracking is incomplete, downstream quality cannot be verified, or additional creative produces reach without improving business outcomes. This protects you from scaling activity simply because the platform is growing. The adoption question is not whether other advertisers are arriving. It is whether your account has found a repeatable path from conversational intent to profitable action.

FAQ: what the early adoption numbers do not prove

Does broad ad exposure mean ChatGPT users are ready to buy?

No. Exposure proves that the platform can distribute ads to a meaningful share of eligible users. Purchase intent still depends on the conversation, offer, creative, product, and destination. Use reach to justify testing, not to forecast sales.

Should you move budget out of Google or Meta to fund the test?

Not by default. Fund ChatGPT Ads as an incremental experiment until it meets the same business standard as the channel whose budget it would replace. If you must reduce another campaign, understand that you are giving up measured acquisition to buy learning in a less mature environment.

Does buying ChatGPT Ads improve organic visibility in answers?

Ads and answers are separate. Do not present paid impressions as answer citations, brand recommendations, or proof of GEO performance. Maintain separate dashboards for paid ChatGPT acquisition and organic AI visibility, even when both contribute to the same customer journey.

Your next move is straightforward: choose one measurable business outcome, map the conversations that can lead to it, create native messages, and send them to the smallest useful set of high-intent pages. Keep the campaign experimental until the downstream economics earn a larger role.

References

Search Engine Land – Report: ChatGPT Ads are growing fast, but advertisers are still figuring them out

September 30, 2026

How to Control Paid Search Placement and Ad Presentation

You may have approved the targeting, copy and landing pages, yet still feel that part of your paid search campaign is outside your control. Automation can decide where an ad appears, while the search interface can change how the same assets look to users.

The practical answer is to manage placement safety and ad presentation as separate control systems. One governs the contexts your brand will accept. The other makes your assets resilient when a platform changes their visual treatment.

Treat placement and presentation as separate control planes

Placement control answers: “Which content should never sit beside this campaign?” Presentation control answers: “If the platform rearranges or emphasizes our assets, will the ad still communicate clearly?”

Those questions require different actions:

Placement safety: define prohibited contexts, choose the right exclusion scope, document why each restriction exists and verify that the setting was applied where intended.
Presentation resilience: write assets that work independently, send each link to a matching destination and measure whether interface changes redistribute attention among those links.

Do not use one as a substitute for the other. Strong sitelinks cannot protect a brand from unsuitable content adjacency. A detailed exclusion list cannot prevent a weak or ambiguous sitelink from attracting the wrong click.

This distinction also makes troubleshooting faster. When impressions or eligible reach change after a placement update, inspect exclusions first. When mobile users start choosing different destinations from the same ad, inspect presentation and asset clarity before changing bids or audiences.

Turn content exclusions into an enforceable brand policy

Microsoft Advertising gives advertisers a direct way to define unsuitable content topics. Its Excluded Content Terms control accepts up to 1,000 terms based on page titles. The control can be applied across an account or scoped to an individual campaign.

That scope decision matters more than the length of the list. An account-level exclusion is appropriate when association with a topic would be unacceptable for the brand under any campaign. A campaign-level exclusion is better when suitability depends on the product, audience or message being advertised.

For example, a company-wide reputational restriction belongs at account level because a campaign manager should not be able to bypass it accidentally. A topic that conflicts with one product campaign but remains relevant to another belongs at campaign level. Applying every concern globally may restrict suitable opportunities; keeping every concern local can leave avoidable gaps.

Build the exclusion list in six steps

Start with policy, not keywords. Write down the topics that create a real reputational, contractual or internal-policy conflict. This prevents the list from becoming a collection of vague dislikes.
Assign a scope to each topic. Mark every restriction as account-wide or campaign-specific before anyone enters it into the platform.
Translate the topic into page-title language. The mechanism evaluates terms associated with page titles, so use wording that is likely to identify the unwanted subject clearly. Do not assume that a broad concept and the words appearing in a title are always the same thing.
Review ambiguous terms. A word can appear in both unsuitable and harmless contexts. Check whether the term expresses the prohibited topic precisely enough before applying it across the account.
Record an owner and rationale. Keep the term, scope, reason, approving stakeholder and implementation status in a shared change log. When delivery changes later, you will know whether the restriction was intentional.
Verify the deployed setting. Confirm that account-level terms appear at account level and campaign-specific terms appear only in the intended campaigns. A correct policy in a worksheet provides no protection if it was entered in the wrong place.

The 1,000-term allowance is capacity, not a target. More exclusions do not automatically create better protection. Prioritize terms with a clear connection to a documented concern, then review the list when brand policy, products or campaign scope changes.

Also be precise about what this control can establish. Because the terms are based on page titles, they are a useful boundary for identifiable topics, not a complete interpretation of every page’s meaning. Keep the platform’s built-in safeguards in place and treat your custom list as an additional layer shaped by your own requirements.

Build sitelinks that survive changes in visual treatment

You control the sitelink assets you submit, but not every detail of how Google displays them. Google has tested a mobile layout that places sitelinks on separate lines, adds a vertical treatment on the left and uses darker link text. That could make secondary routes more noticeable even though the advertiser has not edited the assets.

A test is not a promise of broad rollout. It is still an operational warning: an asset that feels secondary in one layout may become visually prominent in another. Write every sitelink as though it could receive focused attention.

Make every sitelink understandable on its own

Name the destination. “Pricing,” “Enterprise plans” or “Book a demo” tells the user what lies behind the click. Generic labels such as “Learn more” depend too heavily on surrounding copy.
Give each route a distinct job. If several sitelinks promise nearly the same thing, a more prominent layout creates apparent choice without meaningful choice.
Match the landing page to the label. A user who selects a specific secondary link should arrive at that destination, not a general page that requires another search.
Avoid sequence-dependent wording. Sitelinks may be scanned individually. Do not make the meaning of one link depend on the user reading the link before it.
Check the set for internal competition. Your most visually attractive sitelink should not divert high-intent users toward a lower-value or poorly matched route.

Reviewing the text in an asset manager is not enough. Inspect the rendered mobile result whenever you can observe it, and compare the visual hierarchy with the campaign’s intended decision path. Ask which element attracts the eye first, which links now resemble primary choices and whether those destinations deserve the additional attention.

This is also why approval should cover the complete asset set. A sitelink is not merely an optional accessory beneath the main ad. It is a possible entrance to your site whose prominence can change without a new copy review.

Diagnose performance shifts before changing the campaign

Placement changes and presentation changes can both alter performance, but they leave different clues. Use the following as first hypotheses, not proof of causation.

Observed change	Question to investigate first	Useful next action
Delivery changes after exclusions are added	Was a restriction applied at account level when it was intended for one campaign?	Compare the deployed account and campaign lists with the approved scope log.
Mobile users begin choosing different sitelink destinations	Has the visual hierarchy changed even though the assets have not?	Inspect live mobile presentation and destination-level analytics before rewriting the ads.
Click-through behavior changes but downstream results do not improve	Is a newly prominent route attracting attention without matching intent?	Compare the promise of each sitelink with its landing page and desired action.
Performance moves across devices and asset routes at once	Is the cause broader than a mobile presentation variation?	Review targeting, bids, budgets, demand and other campaign changes before attributing the shift to layout.

Keep an annotation for each exclusion deployment, asset edit and observed interface change. Without that timeline, a platform presentation test can be mistaken for the effect of your copy revision, or an account-level exclusion can be mistaken for a demand problem.

Do not call a platform-run interface experiment your A/B test unless you have reliable assignment and reporting for the variants. If you cannot identify which users saw which treatment, you can document the correlation and investigate it, but you cannot cleanly credit the layout for the outcome.

A useful review separates three layers: eligibility and distribution, user interaction with the rendered ad, and behavior after the click. That sequence keeps you from “fixing” the landing page when an exclusion changed delivery, or loosening brand-safety rules because a sitelink destination underperformed.

Key takeaways

Manage content adjacency and visual presentation as separate risks with separate owners, controls and diagnostics.
Use account-level exclusions for non-negotiable brand restrictions and campaign-level exclusions for context-specific concerns.
Microsoft’s Excluded Content Terms can use as many as 1,000 page-title terms, but relevance and scope matter more than filling the allowance.
Write each sitelink as a self-contained route because Google can change its prominence without requiring an asset edit.
When performance moves, check distribution, rendered interaction and post-click behavior in that order before changing the campaign.

Your next step is concrete: audit one account’s exclusion scopes and one mobile campaign’s complete sitelink set. Correct the first mismatch you find, log the change and establish the baseline you will use to judge what happens next.

References

September 28, 2026

How to Create Google Veo Video Ads for PMax and Demand Gen
If your PMax or Demand Gen campaign has strong still images but little usable video, you no longer need to make a full production the first step. Inside Google Ads, Veo can turn two image assets into a five- or 10-second video, giving you a faster way to add short-form creative or refresh assets that have started to wear out.

That speed helps only when you give the tool a focused job. Veo can animate your images, assemble two scenes and apply text, but it cannot decide which benefit matters, repair a weak offer or make mismatched images tell a coherent story. Treat it as a rapid production layer: you supply the idea, evidence and brand discipline.

Key takeaways
- Use Veo when you have high-resolution product or service images but need a quick, short-form video asset for PMax or Demand Gen.
- Give the video one job and organize its two scenes as a simple sequence. Ten seconds is not enough for a product tour, company introduction and offer explanation at the same time.
- Produce the same concept in horizontal, vertical and square formats so the campaign has an appropriate asset for more available surfaces.
- Use the two 30-character headlines for the benefit, qualification or next action. Your business name already appears first, so repeating it consumes scarce space.
- Review results at the asset level, but do not let direct conversions become the only verdict. Delivery, engagement, clicks, website engagement and view-through conversions can reveal different parts of the asset’s contribution.
Design one idea that fits inside ten seconds

Veo’s time limit is a useful creative constraint. Before you open Asset Studio, complete this sentence: “After watching, the right customer should understand ______.” If you need more than one clause to fill the blank, the concept is probably too broad.

A short Veo asset can introduce one product benefit, make a static product image more noticeable, connect a problem image to a result image or carry a familiar campaign message into a video format. It is less suitable when the sale depends on a detailed demonstration, several conditions, an extended narrative or a person speaking directly to the viewer.

Build a two-scene bridge

The selected images appear one after the other, so their relationship has to make sense before any animation is added. Choose one of these simple structures:
- Context to product: Establish the setting in scene one, then make the product the clear focal point in scene two.
- Problem to result: Show a recognizable condition first and the completed outcome second. Use this only when the result is accurate and supported by the landing page.
- Wide view to detail: Begin with the complete product or service result, then move to the feature that explains the benefit.
- Product to action: Use the first scene to establish what is being offered and the second to support the next step with the offer or call to action.
The second image should resolve or deepen the first, not merely replace it. Two unrelated hero images may each look polished while producing a video with no narrative movement. Put them side by side before uploading them and ask whether the sequence is understandable as two static frames. If it is not, motion will not fix it.

Know when the format is the wrong fit

The image-to-video route in Google Ads does not accept images containing a face. Product images, packaging, environments, interfaces and service-result images are therefore more practical inputs than portraits or testimonial frames.

Do not contort a people-led idea to fit that restriction. If credibility depends on a customer, creator, employee or demonstrator appearing on screen, use a production method designed for that concept. Veo is valuable because it removes production friction from suitable ideas, not because every idea should be forced through it.

Prepare source images for all three video formats

The quality ceiling is set before generation begins. A high-resolution image with one obvious focal point gives Veo cleaner material to animate and gives you more room to crop. A small or already-soft image may look acceptable in an account preview but become visibly grainy when shown on a larger screen.

Google Ads supports three video shapes, and the practical goal is to create the same concept in each one:

Format Aspect ratio Recommended HD dimensions
Horizontal 16:9 1920 x 1080
Vertical 9:16 1080 x 1920
Square 1:1 1080 x 1080

Do not assume one composition will survive all three crops. A product pushed toward the left edge may work in a horizontal frame and become cramped or disappear in a vertical one. Either start with an image whose subject and important brand details sit comfortably near the center, or prepare crop-specific versions of the same scene.

Use an image-readiness check before generation
- Resolution: Start with the cleanest, largest approved image available. Do not enlarge a visibly soft thumbnail and expect generation to restore authentic detail.
- Focal point: Make the product, environment or service result immediately identifiable. Competing objects make the intended subject harder to read in a brief scene.
- Crop tolerance: Check horizontal, vertical and square crops before committing to the image. Keep essential product features, packaging and brand marks away from vulnerable edges.
- Sequence: Match the two scenes in visual logic. Similar lighting, color and subject scale can help the transition feel intentional.
- Copy space: Leave enough uncluttered area for overlays. Text placed over detailed packaging or a busy background may technically fit while remaining hard to read.
- Brand accuracy: Use images that represent the product or service as it is actually sold. The generated asset should not imply a feature, finish, result or offer that the landing page cannot substantiate.
- Face restriction: Remove any candidate that contains a face before you build around it, because that image cannot be used in this particular creation flow.
Prepare these inputs as a small asset set rather than hunting through the library during generation. For each scene, keep an approved horizontal, vertical and square crop with consistent naming. That makes later iterations faster and reduces the chance that one format quietly uses a different concept.

Build the asset in Google Ads, then inspect every frame

The Google Ads workflow lives in Asset Studio. Once your images and message are ready, the mechanical part is short:
1. Open Asset Studio in your Google Ads account and go to Create videos.
2. Select Create video from images.
3. Choose a five- or 10-second duration. Use the shorter option only when the idea remains understandable without rushing the transition or text.
4. Select the first image from your asset library for scene one and the second image for scene two.
5. Review the two animation options supplied for each scene and choose the combination that keeps the focal subject clear.
6. Select a video template and add the text overlays.
7. Review the completed preview in the intended aspect ratio.
8. Upload the result to a private YouTube channel or your brand’s YouTube channel, then use it as a Short in PMax or Demand Gen.
The two available animation choices may not create radically different concepts. That is another reason to solve the story in the still images first. Choose animation based on clarity: the best option is the one that directs attention to the subject without obscuring the product or making the transition feel disconnected.

Make the text earn its limited space

You receive two headlines of up to 30 characters each, while the business name is the first text shown. Repeating the brand name in either headline usually wastes space that could explain why the viewer should care.

A useful division of labor is:
- Headline one: State the single benefit, differentiator or relevant use case.
- Headline two: Add the most important qualifier, offer or next action.
Write both lines before selecting a template. Count every character, then remove words that merely announce the ad. Phrases such as “introducing,” “learn more about” and a repeated business name consume room without adding a reason to continue. The image should establish the object; the copy should supply meaning the image cannot.

Review the preview as a finished ad

A polished transition can distract you from small errors. Pause through the preview and check the things a customer will actually see:
- Does the product retain the correct shape, label, color and identifying details?
- Is the focal subject visible throughout the animation rather than only in the opening frame?
- Does the transition preserve the intended relationship between scene one and scene two?
- Can both headlines be read comfortably without competing with the busiest part of the image?
- Are the business name and headlines complementary rather than repetitive?
- Does every visual and written claim match the destination page?
- Does the crop remain clean in the specific horizontal, vertical or square version you are reviewing?
Repeat that inspection for all three formats. Approval of the horizontal asset does not prove that the vertical crop is safe. If a version weakens the subject or message, change its source crop instead of accepting it merely to complete the set.

Test the asset by question, not by novelty

Launching an AI-generated video is not itself a test. A test begins with a question that can change your next decision. You might ask whether motion improves engagement over the existing still concept, whether a different first scene produces more clicks, or whether benefit-led copy brings better website engagement than feature-led copy.

Change one creative idea at a time
1. Add the first Veo concept without immediately removing your strongest existing assets. That preserves useful creative while the new asset begins receiving delivery.
2. Create horizontal, vertical and square versions from the same concept so a missing format does not become the hidden reason for limited reach.
3. Keep the offer and destination page stable for the first comparison. Otherwise, you will not know whether the video or the surrounding proposition changed the response.
4. Name the asset so its variables remain visible. A convention such as VEO-10S-916-HOOK-A-COPY-A-V1 records the duration, ratio, hook, copy and version without requiring a separate lookup.
5. For the next iteration, change either the opening image, the second scene or the overlay message. Changing all three produces another ad, but little usable learning.
This will not become a perfect laboratory comparison. PMax and Demand Gen can distribute assets across different contexts, and impressions and performance vary by channel. Keep the comparison as consistent as the campaign allows, then interpret the results as directional evidence rather than pretending every variable was controlled.

Read the full path from delivery to action

Video performance is available at the asset level. Read the signals in sequence instead of jumping directly to the conversion column:
- Impressions: First establish whether the asset received meaningful delivery. Low delivery is not enough evidence to call the creative a failure.
- Engagement: Use this to judge whether the short visual and its opening moment held attention well enough to produce a response.
- Clicks: Look for evidence that the message created enough interest for the viewer to take the next step.
- Website engagement: Check whether the post-click behavior supports the promise made in the video. Clicks followed by weak site interaction should send you back to the message-to-page alignment, not automatically to the animation.
- View-through conversions: Treat these as a sign that exposure may have assisted a later action. They add context, but they should not be treated as proof that the video alone caused the conversion.
- Direct conversions: Keep them in the evaluation, but do not demand that every five- or 10-second asset behave like a direct-response unit before it can contribute value.
The pattern between metrics tells you what to change. Delivery without engagement points toward the opening scene or visual hook. Engagement and clicks followed by weak website behavior point toward a mismatch between the ad’s promise and the landing experience. Too little delivery means you need more observation before making a creative judgment. View-through activity with few direct conversions may indicate an assisting role, but it still needs to be considered alongside the rest of the campaign.

Start with one campaign that has approved, high-quality stills and a genuine video gap. Build one two-scene concept, render it in all three ratios and write down the variable you intend to learn from before launch. Veo’s advantage is not that one generated clip replaces every production need. It is that the next relevant creative iteration becomes easier to make, inspect and improve.

References
- Search Engine Land – How to use Google Veo to create video ads for PMax and Demand Gen
September 24, 2026

Format	Aspect ratio	Recommended HD dimensions
Horizontal	16:9	1920 x 1080
Vertical	9:16	1080 x 1920
Square	1:1	1080 x 1080

Tag: Ad Optimization

Know which control surface changed

Audit Demand Gen overlays before the next launch

Run a campaign-by-campaign creative check

Use the narrowest control that matches your decision

Account for the AI-edit label

Make SDF v11 a controlled migration, not a file swap

Use this v11 migration sequence

Test creative and targeting changes without confounding them

Key takeaways

References

Key takeaways

What the AI Max preview can actually tell you

Choose a CTR benchmark that matches the auction

CTR by ad type and placement

CTR for the first Search ad by industry

Audit the preview as a claims and intent test

Run the live pilot without letting CTR make the decision

References

Know the boundary of the AdMob failure

Confirm the pattern before changing your SDK or app code

Contain the user trap at the placement level

Measure the blocked journey, then restore cautiously

Look beyond crash-free sessions

Require evidence before full restoration

Key takeaways

References

Campaign-level frequency can hide account-level saturation

Choose between broader reach and managed repetition

Build a campaign group around one coherent job

Measure delivery changes, not just cleaner reporting

Key takeaways

References

Start with the profit floor, not the platform target

Give the bidding system values that survive a finance review

For ecommerce campaigns

For lead-generation campaigns

Choose how much control AI gets, one decision at a time

Bidding needs signal density and economic constraints

Search terms show where automation is buying growth

Creative and reporting still need human definitions

Run one test and judge it on post-ad contribution

Key takeaways

References

Key takeaways

The attribution gate changed, not the conversion event

Why the same campaign can report more view-through conversions

Use corroborating signals before changing budget

Build a clean reporting bridge across the rollout

Make the next performance decision on the new baseline

References

Start with the request Google actually evaluates

Give ChatGPT Ads a specific job in your channel mix

Build campaigns around conversational intent, not keyword lists

Keep the landing-page plan deliberately narrow

Measure the pilot as a decision system, not a traffic report

Read the funnel in sequence

Treat conversational timing as a variable

Set promotion and stop rules before the launch

FAQ: what the early adoption numbers do not prove

Does broad ad exposure mean ChatGPT users are ready to buy?

Should you move budget out of Google or Meta to fund the test?

Does buying ChatGPT Ads improve organic visibility in answers?

References

Treat placement and presentation as separate control planes

Turn content exclusions into an enforceable brand policy

Build the exclusion list in six steps

Build sitelinks that survive changes in visual treatment

Make every sitelink understandable on its own

Diagnose performance shifts before changing the campaign

Key takeaways

References

Key takeaways

Design one idea that fits inside ten seconds

Build a two-scene bridge

Know when the format is the wrong fit

Prepare source images for all three video formats

Use an image-readiness check before generation

Build the asset in Google Ads, then inspect every frame

Make the text earn its limited space