Tag: Campaign Management

YouTube Ad Creative and DV360 Changes to Make by October

Your YouTube campaign can have a sound bid strategy and still underperform because the ad was built for another surface. At the same time, a promising creative refresh can stall before delivery if the Display & Video 360 integration behind it is not ready for October’s unversioned platform changes.

Treat this as one operating problem with two workstreams. Improve the message people see and hear, then verify that your API and Structured Data File workflows can still create, update and protect the campaign. Here is the sequence we would use.

Key takeaways

For Demand Gen in-stream skippable ads in the United States, July 2026 data associated human voice with 12% higher conversions on average, text overlays with 3% higher conversions and visible branding in the first five seconds with 4% higher conversions. These are test priorities, not guaranteed lifts.
Build image ads for the YouTube feed: use high-resolution, full-bleed imagery, include people when appropriate and remove black bars, excessive empty space and oversized logos.
Do not bake fake buttons or arrows into an image. They compete with YouTube’s functional call to action and can leave the viewer unsure about what is actually clickable.
On Oct. 1, DV360 API and Line Item Structured Data File workflows lose specified digital-content-label exclusions and most sensitive-category exclusion options.
On Oct. 12, YouTube responsive ad creation and updates require a business name and logo when those defaults are not already assigned to the parent advertiser.

Start with voice, early branding and useful on-screen text

Creative is not the decorative layer that you address after bidding and targeting. Nielsen attributed 49% of campaign ROI to creative, while Ekimetrics found that improving creative could more than double YouTube ROI. Those aggregate findings do not forecast what your account will gain, but they do justify giving creative testing the same operational attention as media settings.

The most actionable benchmarks are narrower. They apply to Demand Gen in-stream skippable ads, use U.S. data from July 2026 and describe associations rather than proof that an isolated element caused the result. That scope matters when you decide what to test and how confidently to interpret it.

Creative element	Observed conversion association	First controlled test
Human voice	12% higher on average	Compare a voiced cut with a closely matched cut that has no human voice.
Supers or text overlay	3% higher on average	Add concise on-screen wording to the same core edit and keep the offer and call to action unchanged.
Brand visible in the first five seconds	4% higher on average	Compare immediate visual brand identification with a later brand reveal.

Do not add those percentages together and turn the result into a forecast. The elements can interact, and campaigns that use them may differ in other important ways. Use the figures to determine test order: if you have enough traffic for only one new comparison, human voice is the most defensible place to start because it had the largest reported association.

Give the voice a real job. It can state the viewer’s problem, establish the offer or make the next action clear. A voice that merely reads every word on screen adds sound without improving the message. Keep supers equally disciplined: reinforce the key point rather than turning the frame into a transcript.

Early branding also needs restraint. The goal is to make the advertiser identifiable within five seconds, not to cover the opening with a logo that delays the reason to keep watching. Put the brand into the story while the viewer is still deciding whether to skip.

For a useful test, hold the audience, offer, bid strategy, call to action and landing page as steady as your campaign setup permits. Change one creative factor at a time. If your conversion volume cannot support several cells at once, run the comparisons sequentially instead of launching a test that never produces a clear decision.

Judge the result against the conversion action that matters to the campaign. A click-through improvement is not automatically a conversion improvement. Also, do not assume that benchmarks from U.S. Demand Gen in-stream skippable inventory transfer unchanged to Shorts, other formats or other markets. Those are separate questions for your account to answer.

Make image assets belong in the YouTube feed

An image can be polished in a design file and still look broken when placed in a YouTube feed. The common failure is not low production value. It is a layout that carries the visual habits of a banner, presentation slide or another ad platform into a surface where people expect immersive imagery.

For YouTube image ads, visible people and people interacting with products tend to outperform assets without human presence in Google’s platform observations. Human presence should still make sense for the product and message; inserting an unrelated face is not a substitute for a coherent concept.

Fill the available frame. Start with high-resolution, full-bleed photography or lifestyle imagery rather than an image floating inside a large solid canvas.
Show use, not just inventory. When appropriate, let a person hold, wear, operate or otherwise interact with the product so the viewer can understand its role quickly.
Keep the logo proportional. The brand should be identifiable without making an oversized logo the main visual event.
Remove structural clutter. Black bars and large empty solid areas can make the asset feel fragmented or incorrectly formatted.
Delete fake interface elements. A button, play control or arrow drawn into the image is not functional. Let YouTube’s actual call-to-action control handle the interaction.

Fake controls create two competing instruction systems. The platform presents a real action, while the picture implies another one that does nothing. That forces the viewer to determine which visual element is interactive instead of understanding the offer. If an arrow is necessary to make the call to action discoverable, the composition or message probably needs another pass.

Review the rendered asset in its intended placement, not only at full size on a designer’s canvas. Ask whether it reads as one complete image, whether the important person or product survives the crop, whether the brand remains recognizable and whether there is exactly one obvious functional path forward. This preview is also where black bars, oversized marks and deceptive button shapes become easiest to catch.

Native fit does not mean disguising an advertisement. It means using the visual language of the surface while keeping the advertiser and offer clear. A feed-compatible image earns attention through relevance and composition, not through an imitation of YouTube’s controls.

Prepare DV360 automation for the October deadlines

A better asset cannot improve results if the integration that manages it stops working. The October rollout contains three unversioned changes across the Display & Video 360 API and Structured Data Files. Do not assume an older client or a delayed API-version migration will preserve the previous behavior.

Oct. 1: specified exclusion controls are removed

Starting Oct. 1, advertisers will no longer be able to use API targeting to exclude specific digital content labels. The change affects available TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION options and valid values in the Digital Content Labels - Exclude column of Line Item Structured Data Files.

Most sensitive-category exclusions are also being removed from targeting on that date. Audit any workflow that uses TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION, as well as the Brand Safety Sensitivity Setting and Brand Safety Custom Settings columns in Line Item Structured Data Files.

This is a change to available controls, not a reason to quietly weaken your brand-safety policy. Do not simply delete fields until an error disappears. First identify which business rule each field was implementing, who owns that rule and what the approved workflow should be once that targeting option is unavailable.

Do not guess how every existing line item will display or behave after the change. Inventory the affected line items and validate the actual transition in a controlled workflow. The important distinction is between authoring a new setting, updating an existing line item and observing a previously configured value; each path deserves an explicit check.

Oct. 12: responsive ads need business identity assets

Starting Oct. 12, developers creating or updating YouTube responsive ads must provide a business name and logo when default values are not already assigned to the parent advertiser. The requirement also applies to ads uploaded through Ad Structured Data Files.

That parent-advertiser condition gives you a clean preflight decision. If approved defaults exist, verify that every relevant workflow can use them. If they do not, make the business name and logo required inputs before an ad reaches the create, update or upload step. Do not wait for a production job to discover that the identity assets are missing.

Your technical audit should cover these exact paths:

Search code, configuration files and Line Item Structured Data File templates for TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION, TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION and the affected column names.
List every scheduled job, internal tool and third-party workflow that creates or updates YouTube responsive ads through the API.
List every process that uploads Line Item or Ad Structured Data Files. Treat the two file types separately because the exclusion and identity changes affect different operations.
Inspect each parent advertiser used by those workflows and record whether an approved default business name and logo are already assigned.
Add a preflight check that blocks responsive-ad submission when neither advertiser defaults nor required identity inputs are available.
Have the brand-safety owner approve any operational change caused by the lost exclusion options, then test create, update and file-upload paths before their respective deadlines.

Record which test covers which deadline. A successful responsive-ad creation test does not prove that an exclusion workflow is ready, and a clean Line Item Structured Data File does not prove that an Ad Structured Data File contains the required identity. Separating those assertions will make a failure much easier to locate.

Run one joined creative-and-delivery sprint

Creative production and delivery engineering often sit in different queues, but the campaign depends on both. A new ad trapped behind a failed update request creates no learning. A perfectly updated integration serving weak recycled assets only automates the wrong input.

Use this order to turn the work into a test you can trust:

Clear the deadline risk. Open technical tickets for the Oct. 1 exclusion changes and the Oct. 12 identity requirement. Assign owners before asking the creative team to produce a large new batch.
Freeze a useful control. Preserve the current offer, landing page, audience and conversion action so the next result can be interpreted as a creative comparison.
Create focused video variants. Build a human-voice version, an early-brand version and a concise-text-overlay version. Keep the underlying proposition as consistent as possible.
Rebuild image assets for the feed. Use full-bleed imagery, meaningful human presence and one clear composition. Remove fake buttons, arrows, black bars and excess empty space.
Validate delivery before launch. Exercise the API create and update paths, the relevant Structured Data File uploads and the business-identity fallback. Do not mix a delivery defect into a creative performance test.
Label the change in reporting. Use variant names that identify the factor being tested. When conversions move, you should be able to connect the result to voice, branding, text or image treatment without reopening the design files.

If capacity is tight, prioritize the integration work first because its dates are fixed. Then test human voice, which had the largest reported conversion association, followed by early branding and text overlays. Feed-image cleanup can run alongside those video edits because it addresses a different asset type.

Open your highest-spend YouTube ad and its parent advertiser record side by side. Check whether the ad uses a human voice, identifies the brand within five seconds and gives on-screen text a clear purpose. Then confirm the advertiser’s default business name and logo and search your automation for the affected exclusion identifiers. You will leave that session with one defined creative experiment and one concrete technical readiness list, both in time for October.

References

August 28, 2026

Google Display to Demand Gen Migration: A Practical Runbook

If your standalone Google Display campaigns depend on Manual CPC, portfolio bidding, HTML5 ads or tightly constrained audience targeting, the move to Demand Gen is not a simple campaign rename. Some of those controls will not survive the migration, and pretending they will can leave you diagnosing a strategy change as if it were a temporary performance dip.

Your safest approach is to separate migration from expansion. First reproduce the campaign as closely as Demand Gen allows. Confirm that bidding, creative, audiences, conversion signals and spending behave as expected. Only then test Discover, Maps, additional formats or other Demand Gen capabilities.

The deadline matters, but the unspecified date matters more

The ability to create new standalone Display campaigns will be disabled permanently in January 2027. Google expects automatic migrations later in 2027, but it has not specified when those migrations will begin.

That gap is a planning risk. Waiting for automatic migration means you may lose control over whether the change lands near a product launch, seasonal promotion, reporting deadline or peak sales period. Migrating deliberately gives you a chance to resolve incompatibilities and choose a period when your team can watch the account closely.

The migration tool began appearing through a phased rollout in June after the May announcement, so availability can differ between accounts. When the tool is available, it can update a live campaign while preserving the previous 42 days of performance history. That continuity is intended to reduce the new campaign’s learning period, not eliminate performance volatility.

You also do not have to adopt every Demand Gen network during the move. Demand Gen supports individual network selection, and the migration tool initially creates a Google Display Network-only Demand Gen campaign. Other networks can be added afterward. Use that separation: migration should answer whether the replacement works; expansion should answer whether new inventory adds value.

Audit the features that will not transfer cleanly

Campaign components are sorted on a workbench, with compatible modules passing through an inspection gate and incompatible controls set aside in amber trays.

Build a compatibility sheet before touching the migration control. For every Display campaign, record its current bid strategy, targeting logic, creative formats, data dependencies, measurement studies and business objective. Then mark every feature that requires a replacement.

Display campaign dependency	Demand Gen status	Decision to make before migration
Target CPA, Target ROAS or Maximize Clicks	Supported	Confirm the selected strategy still matches the campaign objective and that its conversion inputs remain appropriate.
Manual CPC, Viewable Impressions or Pay for Conversions	Not supported	Select a replacement strategy and document how success will now be judged.
Bid adjustments, seasonality adjustments or portfolio bidding	Not supported	Identify what business rule each control handled and decide how you will manage that requirement without it.
Business Data feeds	Not currently supported	Do not migrate a feed-dependent execution until you have a supported alternative. Availability has been described as coming, but without a specific date.
Uploaded HTML5 ads or third-party ads	Not currently supported	Rebuild the creative in a supported format or wait. Support is planned for late 2026, but a roadmap date should not be treated as a delivery guarantee.
Brand Lift or Search Lift studies for GDN	Not supported	Decide whether the campaign can move without those studies or requires a different measurement plan.

The supported bidding options are Target CPA, Target ROAS and Maximize Clicks. That does not make them interchangeable. Maximize Clicks is aligned with traffic acquisition. Target CPA requires a meaningful conversion action and a cost-per-acquisition objective. Target ROAS makes sense only when the conversion values being supplied reflect the value you actually want the system to pursue.

Do not choose the nearest-looking setting just to clear the migration screen. Write down what the old strategy controlled and what the replacement will optimize. A campaign moving from Manual CPC to automated conversion bidding, for example, is undergoing a buying-strategy change as well as a platform change. Its before-and-after results need to be interpreted accordingly.

Creative needs the same discipline. Business Data feeds, uploaded HTML5 ads and third-party ads are not currently supported. HTML5 and third-party ad support is planned for late 2026, while no precise availability date is stated for Business Data feeds. If one of those formats is essential to the campaign, the missing replacement is a migration blocker, not a minor setup detail.

Use a controlled six-step migration runbook

Six connected workstations show campaign inventory, duplication, configuration, verification, launch, and monitoring while the original setup remains on a parallel rail.

A controlled migration gives you a clean baseline and limits the number of explanations for any change in performance. Use the same runbook for each campaign so that results are comparable across the account.

Capture the baseline. Export at least the same 42-day performance window the migration tool can retain. Record the campaign budget, bidding method and target, conversion actions, audiences, creative formats and any account-level process that depends on the campaign. Save the date and time of the export.
Map every unsupported dependency. Use the compatibility table above. Assign a replacement, owner and decision date to each unsupported bid strategy, adjustment, feed, creative format or lift study. Do not begin while an essential dependency remains unresolved.
Choose the cutover window. Performance may fluctuate after migration, so avoid placing the first move immediately before a peak trading period. Pick a time when someone can inspect delivery and spending during the rest of that day and over the following reporting periods.
Account for same-day spending. The newly migrated campaign will not respect the amount the old campaign already spent earlier that day. That creates a risk of more combined same-day spend than you expected. Watch total account spend at the cutover rather than assuming the new campaign knows how much daily budget has already been consumed.
Verify the migrated campaign before expanding it. Confirm that the new Demand Gen campaign is restricted to Google Display Network inventory, as the migration tool is designed to configure it. Check the budget, bid strategy, conversion inputs, audience setup and live creative against your migration sheet.
Hold expansion until the replacement is interpretable. Let the Display-only campaign establish a usable post-migration pattern before adding Discover, Maps or materially different creative. When you do expand, change one major dimension at a time and record the date.

The fourth step deserves special attention. If a Display campaign has spent a large portion of its daily budget before migration, the new campaign can still begin without credit for that earlier spending. You do not need to predict the exact effect. You do need an operator watching the combined spend and authorized to respond if delivery departs from the day’s plan.

During the first post-migration review, compare more than totals. Look at spend, delivery, conversion volume, conversion value and the metric tied to the chosen bid strategy. Annotate the migration so nobody later mistakes the cutover for an unexplained market movement. If you change the bid target, network mix and creative simultaneously, you will have no reliable way to tell which change produced the result.

Rebuild audience and measurement assumptions for Demand Gen

The deepest change is not in the interface. Demand Gen uses audiences and conversion signals as inputs to a more automated buying system, so controls that once acted as boundaries may now act as guidance.

Treat Lookalike Audiences as signals, not fences

As of March 2026, Lookalike Audiences changed from restrictive targeting to audience suggestions. Your first-party seed still informs the model, but Google can reach high-intent users outside the similarity thresholds associated with the seed.

If you previously relied on a Lookalike segment to define who could receive an ad, revise that assumption before migration. The segment now supplies direction rather than a hard perimeter. Judge it by the outcomes it helps generate, and use the campaign’s available network controls to govern where ads can run.

Create required Lookalike segments well before the campaign needs them. A new segment can take up to 96 hours to populate. Building it on the day of migration can leave you troubleshooting a campaign whose intended audience signal is not yet ready.

Decide whether view-through conversions belong in optimization

Demand Gen can optimize bids toward users who view a YouTube or Discover ad, do not click it, and convert later. This view-through-conversion optimization can provide an additional signal when click-led conversion volume is too limited for conversion-focused bidding.

That capability is not automatically an improvement for every account. Decide whether a later conversion following an ad view represents an outcome you want the bidding system to pursue. Make the decision explicitly, document it and avoid comparing a view-through-optimized campaign with a click-focused predecessor as though their optimization inputs were identical.

Billing also changes in a specific configuration. Google has announced that Demand Gen campaigns running on Discover with view-through-conversion optimization will move from CPC to CPM billing. In other words, cost is tied to impressions rather than clicks. This does not affect a Demand Gen campaign serving only on the Display network, but it becomes relevant as soon as you add Discover under that optimization setup.

Before enabling that combination, update the reporting brief. Stakeholders should know that a change in click volume or CPC no longer describes the entire buying model. Mark the billing transition date and evaluate delivery, cost and conversions within the new setup rather than forcing a direct CPC-era comparison.

Add new reach as a test, not a migration default

Demand Gen can extend reach into Discover and Maps, offers formats unavailable in standalone Display, and includes additional generative image tools. It also provides more ways to use YouTube creative. An Affiliate Partnership boost for organic YouTube affiliate videos is in pilot, so it should be treated as an emerging option rather than a dependency in your migration plan.

Test those capabilities after the Display replacement is stable. State one hypothesis for each expansion: the audience you expect to reach, the conversion signal the campaign will optimize and the result that would justify continued spend. Add one network or major creative approach at a time. Otherwise, Demand Gen’s wider inventory can obscure whether the migration itself succeeded.

Key takeaways

New standalone Display campaign creation ends in January 2027; automatic migration is expected later in 2027, but its start date remains unspecified.
The migration tool can retain 42 days of history and initially creates a Display Network-only Demand Gen campaign.
Manual CPC, Viewable Impressions, Pay for Conversions, bid adjustments, seasonality adjustments and portfolio bidding require alternatives.
Business Data feeds, uploaded HTML5 ads, third-party ads, Brand Lift studies and Search Lift studies have support gaps that may block some migrations.
Same-day spend from the old campaign is not credited against the newly migrated campaign’s budget, so the cutover needs active spending oversight.
Lookalike Audiences are suggestions rather than restrictive targeting, and a new segment can take up to 96 hours to populate.
Discover inventory using view-through-conversion optimization is moving from CPC to CPM billing; Display-only delivery is not affected by that billing change.

Start by opening your highest-spend standalone Display campaign and marking every compatibility-table row as supported, replaceable or blocked. If a blocked item has no approved alternative, solve that first. If the campaign is clear, choose a monitored migration window, preserve the Display-only network setup and put any Discover, Maps or creative expansion into a separate test plan.

References

Search Engine Land — Moving from Google Display to Demand Gen: What you’ll lose and gain

August 27, 2026

Google LSA Category Expansion: Your Migration Action Plan
If your Local Services Ads account still describes a specialist business with a broad label, this is the time to inspect it. Google is introducing more precise categories while preparing to move LSA campaign management into Google Ads, so the choices you make before migration can affect both lead relevance and your ability to diagnose performance afterward.

You do not need to rebuild a working campaign. You do need a clean record of what it targets, an honest category-to-service map, and a plan for separating migration effects from ordinary business changes.

Separate the category expansion from the platform migration

Two changes are arriving together, but they solve different problems. The category expansion gives Google a more precise description of your business. The migration changes where you manage the campaign.

Restaurants that once sat inside broad restaurant or dessert-and-coffee groupings can now use classifications such as American, Chinese, Italian, pizza, steak house, sushi or vegan restaurant. Automotive advertisers have options including Auto Air Conditioning Service, Auto Glass Repair Service, Brake Shop, Car Battery Store, Car Inspection Service, Oil Change Service, Tire Shop and Transmission Shop. Beauty categories have also become more detailed. This added category specificity is intended to help businesses represent their actual services and potentially connect with customers seeking those services.

The platform move does not turn LSAs into a conventional keyword campaign. Google says advertisers will continue to pay for valid leads rather than clicks. Campaigns will remain keywordless, and their existing local placements will remain on Google Search and Google Maps.

Key takeaways
- Review newly available categories before your account moves, especially if a broad label currently hides a specialist service.
- Select only categories that describe services you genuinely provide; the category menu is not a keyword list.
- Expect campaign management to move into Google Ads, but do not rebuild an existing setup solely because of that change.
- Prepare to receive real leads if Google allows your business to advertise before completing full badge onboarding.
- Do not treat an LSA category as proof of an organic, local-pack or AI-search ranking factor.
Choose the narrowest truthful description of the business

A more precise category is useful only when it matches the job a customer can actually buy. A transmission specialist should not have to look identical to a general maintenance shop. A sushi restaurant should not have to rely on a generic restaurant label. That distinction can reduce ambiguity at the moment a searcher is deciding whom to contact.

It does not follow that selecting every available category will produce better leads. LSAs are still keywordless, so categories should describe the business rather than function as a collection of search terms. An unsupported category can attract inquiries your team cannot serve, waste response time and make lead-quality reporting harder to interpret.

Use this category audit:
1. List the services customers can purchase now. Use operational language, not aspirational offerings. Include the specialist jobs, cuisines or treatments that materially define why someone contacts you.
2. Match each offering to the most precise available LSA category. If an exact category now exists, compare it with the broad classification you previously used.
3. Check the edge of every category. Ask what a reasonable customer would expect after seeing that label. Remove a category if the business cannot consistently meet that expectation.
4. Confirm the handoff. Make sure the employee, location or call-routing process receiving the lead knows which service generated it and can qualify it correctly.
5. Record the decision. Save the selected category, the services supporting it, the date and the reason for the change. That record becomes your baseline during migration.
Then compare the promise across your customer-facing properties. Your LSA profile, website, Google Business Profile and phone response do not need to use identical taxonomies, because each product may offer different labels. They should describe the same underlying business. If your ad says Transmission Shop while your site mentions only general maintenance and the receptionist routes every call to a general-service queue, the problem is not wording alone. The customer is encountering three different versions of the company.

Prioritize category changes that resolve a real mismatch. A specialist hidden in a broad category has a stronger reason to update than a business whose current classification already describes what customers buy. Precision is the goal; novelty is not.

Treat pre-badge leads as paid demand, not test traffic

Eligible businesses that pass preliminary checks may be allowed to receive leads while completing the remaining onboarding requirements for the Google Verified badge. These pre-badge ads appear below fully onboarded providers, so earlier activation comes with a placement limitation.

The operational consequence matters more than the label. Those inquiries enter a pay-per-valid-lead system. If you activate before your intake process is ready, you can spend money learning that no one owns the phone, the service-area rules are unclear or employees do not know which new category produced the inquiry.

Before accepting pre-badge leads, put four controls in place:
- Assign an owner. One person should be responsible for lead receipt, response and disposition rather than assuming a shared inbox will manage itself.
- Write a category-specific qualification prompt. For an automotive category, confirm the requested system or repair. For a restaurant category, confirm the relevant dining, menu or order need. Keep the prompt short enough to use on every inquiry.
- Define your internal outcomes. At minimum, distinguish a valid inquiry, a qualified opportunity, a booking or order, and a request for something the business does not provide.
- Log the reason for poor fit. Separate taxonomy mismatch from service-area, availability, pricing and response problems. Otherwise every failure gets mislabeled as low-quality traffic.
Do not use the badge itself as a universal readiness check. The Verified badge is unavailable for auto, beauty and dining categories. If you operate in one of those verticals, the badge’s absence is not evidence that the account failed to complete the same path as a badge-eligible provider. Train staff and stakeholders on that distinction so they do not promise a badge customers will never see.

Build a migration baseline instead of rebuilding the campaign

The first migration phase begins with select U.S. home and storefront service advertisers in August 2026. Additional advertisers follow later in 2026, while non-U.S. accounts and remaining categories move in 2027. Your country and category therefore matter more than the broad announcement date when planning internal work.

Existing setups are expected to migrate automatically into Google Ads. Do not create a duplicate campaign just to prepare for the new interface. A duplicate can fragment your measurement and introduce overlapping changes precisely when you need a stable comparison.

Create a compact migration record before your account receives its cutover:
- Account name, business location, country and responsible owner.
- Current LSA categories and the real services supporting each one.
- Service area, operating hours, budget and lead-routing destination as configured in the account.
- Onboarding state, including whether the business is fully onboarded, operating through a pre-badge path or in a category where the badge is unavailable.
- Spend, total leads, valid leads, cost per valid lead and the share of leads that become qualified opportunities or bookings.
- Any category, budget, service-area, staffing or hours change made near the migration date.
Use comparable periods when you review performance. A week with a holiday, temporary closure or staffing problem is not a clean baseline for an ordinary week. Platform metrics also cannot tell you whether a lead became revenue unless your own intake process records the outcome.

When your migration notice arrives, verify who can access the destination Google Ads account and who is authorized to change the campaign. Then avoid stacking unrelated edits into the same observation window. If you change categories, budget, hours and call routing at the same time as migration, a later performance shift will have too many plausible causes.

Diagnose post-migration changes in a fixed order:
1. Confirm that categories, services, service area, hours, budget and lead routing match the saved baseline.
2. Check whether verification or pre-badge status changed.
3. Review valid-lead volume and cost before examining downstream booking performance.
4. Check staffing, response handling, availability and other operational changes.
5. Only then treat an unexplained difference as a migration-related issue requiring escalation.
Do not respond to the new Google Ads location by building keyword lists or optimizing toward clicks. The underlying campaign remains keywordless and lead-based. The interface is moving; the commercial unit you are buying is not.

Use the new taxonomy as a content map, not an SEO shortcut

The expanded category list can reveal where your website describes a real service too vaguely. It does not establish LSA category selection as an organic ranking factor, a local-pack signal or a direct path into AI-generated answers. Keep paid eligibility and organic visibility separate in your measurement.

A category deserves supporting content when it represents a distinct customer intent and a service you genuinely deliver. A transmission shop can explain transmission diagnosis, repair scope, customer eligibility and location coverage. A sushi restaurant can make its cuisine, service format, hours and location explicit. A generic page that merely repeats every new label adds no comparable clarity.

For each important category, check whether the corresponding page clearly answers:
- What exactly does the business provide?
- Which customer need or request does the offering address?
- Where is it available?
- What is included, excluded or subject to confirmation?
- How can a customer take the next step?
Apply the same discipline to structured data. An LSA category label is not automatically a valid Schema.org type. Use an established LocalBusiness subtype that accurately describes the entity, and support it with visible page content. Do not invent a schema type by copying a newly available advertising label into the type field. For restaurants, cuisine details should be accurate and visible to users as well as represented in supported structured-data properties. For automotive businesses, specific services can be described in page content even when Schema.org offers a broader business subtype.

For AEO and GEO work, aim for consistent, machine-readable facts rather than assuming Google’s advertising taxonomy is fed directly into frontier models. The business category, visible service description, location facts, structured data and conversion path should reinforce one another. That alignment makes the entity easier to understand without turning an ad configuration into an unsupported ranking claim.

Start with one account. Save its current configuration, identify the narrowest category the business can honestly support, and document a before-migration performance baseline. When the management change reaches you, you will be comparing evidence instead of reconstructing the past from memory.

References
- Search Engine Land — Google expands Local Services Ads categories ahead of migration
August 24, 2026

Generative AI Video Resizing in Performance Max: A Control Guide

You gave Performance Max a strong horizontal video. Now Google can extend it into vertical and square versions so the campaign can reach inventory that the original shape could not cover. That can save production work, but it also gives automation a hand in what your customer sees.

Your decision is not simply whether to switch an AI feature on or off. You need to decide which assets can tolerate generative adaptation, what must remain visually exact, and who has authority to reject a version that fits the placement but fails the brand.

What generative AI resizing changes in Performance Max

Google Ads can now extend existing Performance Max videos into missing aspect ratios. The capability builds on video enhancements that can already convert horizontal assets into vertical and square formats. Google’s stated aim is to improve the viewing experience and make the video eligible for more inventory.

The important word is extend. Ordinary resizing changes dimensions. Cropping removes or repositions material already in the frame. Generative extension can create material needed to complete a differently shaped frame. That moves Performance Max beyond deciding where an ad runs and into adapting the visible creative.

More eligible inventory is a coverage benefit, not proof that every generated version communicates equally well. A vertical asset may fit a vertical placement while weakening the composition, moving attention away from the product, or placing too much visual weight around a logo or call to action. Evaluate format coverage and creative fidelity as separate questions.

This distinction also changes ownership. Media teams can judge whether broader inventory is useful. Brand and creative owners must judge whether the adapted frame remains accurate. If only the first group reviews the feature, the campaign can pass a performance check without passing a creative one.

Choose your control level from the asset, not the campaign

A campaign should not receive one blanket risk rating just because it is a Performance Max campaign. One asset may be easy to extend, while another in the same campaign depends on exact geometry. Classify the videos themselves before deciding how much automation to allow.

A practical three-level policy looks like this:

Allow with routine review: The main subject is centered, the surrounding background is visually simple, essential text is not pressed against an edge, and adding space around the scene would not change what the product appears to be.
Require explicit approval: The subject moves across the frame, a demonstration depends on spatial relationships, text appears in several positions, or the original composition uses the edges deliberately.
Use manually produced formats: The video contains exact package details, interface demonstrations, prices, disclosures, comparison imagery, before-and-after claims, trademark-sensitive shapes, or another element that must not be visually reinterpreted.

The third level does not mean generative tools are inherently unsuitable for the brand. It means the cost of a small visual error is higher than the production time saved on that particular asset. A generated background anomaly in an atmospheric scene may be correctable. An altered product label or misleading interface state is a different class of problem.

Do not use campaign budget as a shortcut for this assessment. A low-spend campaign can still publish an inaccurate representation, while a high-spend campaign may contain a visually flexible asset. Product truth, brand constraints, and message structure are better control signals than spend alone.

If you operate several accounts, write the policy once and attach examples from your own approved creative library. Name which asset types are eligible, which require approval, and which must be supplied in every needed ratio. That keeps the decision from changing whenever a different campaign manager encounters the setting.

Review every generated ratio as a new piece of creative

The safest review process treats a generated version as a new execution derived from an approved master. Calling it a resize can encourage a quick edge check. A full creative review catches errors that appear during motion, after a scene change, or around the final call to action.

Record the master asset. Keep the approved original, its campaign and asset-group location, the available ratios, and the person responsible for creative approval in one register.
Mark the non-negotiable elements. Identify the product silhouette, package text, logo, typography, interface state, offer language, disclosures, and visual claims that must remain unchanged.
Inspect the entire timeline. Review the opening frame, every scene transition, moments when the subject approaches an edge, and the closing frame. Do not approve a moving asset from a single thumbnail.
Review each ratio independently. Horizontal, vertical, and square versions can fail in different places. An approval for one shape should not automatically cover the others.
Check small-screen legibility. View the adapted asset at a realistic small display size. Confirm that the focal action, essential wording, and call to action still make sense without relying on the original composition.
Log defects by timestamp and type. Record where the problem occurs and whether it affects product accuracy, brand presentation, legibility, narrative clarity, or commercial information. A precise rejection is easier to act on than a note saying the version looks wrong.
Assign a clear outcome. Approve the ratio for campaign use, replace it with a manually produced version, or change the relevant video setting. Do not leave a failed version in an informal state where nobody knows whether it can run.

Your review should answer concrete questions. Did the number, color, label, and proportions of products remain accurate? Is the logo intact? Does generated visual material look like part of the same scene? Does the composition still direct attention to the intended action? Are prices, conditions, and disclosures as legible and unambiguous as they were in the master?

Keep campaign approval separate from library approval. A variant that is acceptable for one controlled use should not automatically become an evergreen brand asset or a template for other channels. Record the scope of the approval alongside the decision.

A September 4 opt-out window was provided through account teams or Google’s form, but advertisers can also change video settings from within Google Ads at any time. If that opt-out date has passed for your account, do not assume the decision is permanent. Inspect the current setting and make the appropriate account-level or campaign-level governance decision based on the controls actually available to you.

Measure coverage and creative quality on separate scorecards

Generative resizing is intended to make a video available across more inventory. That objective can be met even when a particular output is not good enough for your brand. Your scorecard therefore needs one track for delivery and another for creative acceptability.

Decision question	Evidence to inspect	Action
Did the new ratio create useful coverage?	Changes in eligible formats, delivery, or placement information available in the account	Keep the format only when its additional coverage serves the campaign goal
Is the output factually accurate?	Frame-by-frame comparison with the approved master and product references	Reject any material error, regardless of campaign performance
Does the message survive the new composition?	Focal action, text legibility, sequence clarity, and call-to-action visibility	Produce the ratio manually when the shape weakens the intended message
Does it remain within brand rules?	Logo treatment, typography, colors, spacing, product presentation, and restricted elements	Approve, restrict, or replace the version according to the documented policy
Can a performance change be attributed to resizing?	A change log plus the campaign reporting available during the review period	Treat a simple before-and-after change as directional, not as isolated proof

Record the setting, approved assets, and review date before making a change. Where practical, avoid introducing another major creative change during the same evaluation period. Performance Max also automates media buying, so campaign results can move for reasons other than the new video ratio. A campaign-level lift or decline by itself does not isolate the effect of generative extension.

Set the rejection rules before looking at performance. A visually inaccurate product should not earn approval because the campaign converted. If a generated ratio delivers useful coverage but repeatedly fails creative review, that is a signal to produce the format manually, not to lower the accuracy standard.

Also log how often your team can inspect generated variants before they run. If the practical workflow gives nobody a reliable chance to review the output, your real choice is not automation with oversight. It is unreviewed creative automation. Change the setting or supply complete format coverage yourself until the approval path exists.

Key takeaways

Performance Max can use generative AI to extend existing videos into missing aspect ratios, including formats suited to vertical and square inventory.
Additional format coverage does not guarantee that the composition, product representation, or message remains acceptable.
Classify risk at the asset level. Exact product visuals, interfaces, disclosures, and layout-dependent demonstrations deserve tighter control.
Review the full timeline of every generated ratio, not just a thumbnail or the approved master.
Measure delivery coverage separately from creative fidelity, and reject material visual errors regardless of performance.
If you cannot establish a dependable owner and approval path, change the video setting or provide manually produced formats.

Start with the highest-risk video currently attached to a live Performance Max campaign. Record its video-enhancement setting, identify its non-negotiable visual elements, and review every available ratio from beginning to end. If nobody can clearly approve or reject the generated versions, pause that layer of automation until ownership is explicit.

References

Search Engine Land — Google Ads will use generative AI to resize Performance Max video ads

August 18, 2026

Google Ads Automated Language Matching: What to Change Now

If you run multilingual Google Ads campaigns, the language setting you once treated as a boundary is about to stop doing that job on Search. Leaving your campaigns untouched may not break delivery, but it can make language allocation harder to predict and language-related waste harder to diagnose.

Your immediate task is not to find a replacement checkbox. It is to make every eligible ad and destination unmistakably suitable for the language journey you intend, preserve the controls that still matter in Performance Max, and give your reporting enough structure to expose mismatches.

Know exactly where the language setting stops applying

Beginning in late September, campaign-level language targeting will disappear from Search and AI Max for Search campaigns. Google will instead match Search ads largely from the language of the ads and signals indicating which languages a user understands.

Campaign or placement	What happens to selected languages	What you should control
Standard Search	The campaign-level setting no longer controls matching	Ad language, ad-group clarity and destination language
AI Max for Search	The campaign-level setting no longer controls matching	Ad language, eligible ad groups and destination language
Performance Max on Google Search	The selected campaign languages no longer apply to Search delivery	Search-facing creative and destination language
Performance Max on YouTube, Display, Discover and Gmail	Selected languages continue to guide delivery	Campaign language settings as well as multilingual assets
Shopping ads within Performance Max	Language settings do not affect these ads	The product and destination experience rather than the campaign language selector

The Performance Max distinction is the easiest place to make an expensive mistake. Do not remove its language settings merely because they no longer govern Search inventory. Those settings continue to guide YouTube, Display, Discover and Gmail delivery.

The opposite warning applies to standard Search. An existing language criterion may remain visible, but visibility does not mean enforcement. Do not use it as proof that a campaign can reach only people associated with the selected language.

Rebuild multilingual control around the ad-to-page journey

Three color-coded customer pathways connect abstract speech waveforms to matching search ads and landing pages while a marketer adjusts one route.

Google can use the language of the search term, a user’s language settings and other preferences to estimate what that person understands. A user whose interface is set to one language may still receive an ad in another language if their behavior supports that match. Your campaign setting will no longer override that judgment on Search.

That makes the ad itself a routing signal. It also makes language consistency a practical control surface: the promise in the ad, the page it opens and the next action should all work for the same reader. Audit that path in this order:

Inventory every active Search ad by its actual language. Do not classify an ad from its campaign name. Read the headline, description, extensions or assets, and call to action.
Record the destination language. Check the page headline, primary offer, form fields, validation messages and conversion action. A translated ad does not create a supported journey when the page or form switches languages.
Identify mixed-language ad groups. If clean diagnosis matters, separate ads by intended language at the ad-group level. This gives you a clearer record of which language candidate received traffic and what happened afterward.
Keep campaign separation only when it serves another business control. Separate budgets, markets, offers or conversion goals can still justify separate campaigns. Duplicating campaigns solely to select different Search languages no longer creates a reliable language boundary.
Document the Performance Max exception. Mark which selected languages must remain because the campaign also serves YouTube, Display, Discover or Gmail.
Add language to launch QA. Treat an ad, its destination and its conversion path as one test case. Approving only the translation of the ad leaves the costly part of the journey unchecked.

Clear structure matters when more than one campaign or ad group is eligible. Google says AI-based ad-group prioritization will choose the candidate with the most relevant language. You cannot force that decision with the former Search language control, but you can avoid giving the system ambiguous or poorly supported candidates.

Make landing-page language an operating requirement

A language change in the campaign interface used to feel like a targeting task. The new model makes it a content-operations task as well. Ad creative and destination pages now carry more of the burden for Search language matching, so page ownership can no longer sit outside the campaign migration.

For each language you actively advertise, define what a complete supported experience means. At minimum, the user should be able to understand the offer, evaluate the main terms and complete the primary action without an unexplained language switch. If the business cannot support that journey, pause or remove the corresponding ad rather than hoping the old campaign criterion will suppress it.

Use language-specific destination paths where they already fit your site structure. They make QA and reporting easier because a landing URL can be reconciled with the language label on an ad group. The URL does not need to become a targeting theory; it needs to help your team answer a concrete question: did the intended ad open the intended experience?

Translation alone is not enough when the offer changes by market. Check prices, availability, legal terms, fulfilment language and contact options wherever they appear in the conversion path. Those checks are not new Google Ads controls. They are safeguards against paying for a click whose promise the destination cannot fulfil.

Monitor language matching without waiting for a perfect report

Two analysts inspect color-coded routes between generic ad tiles and landing pages, with one mismatched connection highlighted in red.

Automated matching can change which eligible language candidate receives traffic. Build a baseline before the rollout so a later shift is visible. The baseline does not need a new platform metric; it needs stable labels and a repeatable review.

Label ads and ad groups by intended language. Use one naming convention across the account so reports can be grouped without rereading every ad.
Record performance by that label. Compare impressions, spend, clicks, conversions and conversion value where those measures apply to your objective.
Review search terms against the served ad language. Read the whole query before classifying it. Brand names and borrowed words can appear inside queries written in another language.
Reconcile destination paths. Flag cases in which a language-labelled ad opens a page intended for a different language.
Use downstream evidence. Unsupported-language form submissions, calls or support requests can reveal a mismatch that click metrics alone will not explain.
Separate Performance Max observations by placement where your reporting allows it. A Search-delivery change should not automatically be blamed on the language settings that still guide the campaign’s other channels.

Set alerts from your own baseline rather than borrowing a universal percentage. The available information does not establish a normal amount of language reallocation or a safe variance threshold. Your alert should identify a material change in your account, not pretend that every advertiser will experience the same shift.

When you find a problem, change one controllable layer at a time: the eligible ad, the ad-group structure or the destination. That preserves enough evidence to tell whether the correction worked. Rebuilding campaigns, rewriting ads and changing pages simultaneously may stop the immediate symptom, but it will leave you unable to identify the cause.

Update Google Ads API workflows by campaign type

API users have a concrete migration requirement. Stop sending language criteria when creating or updating Search campaigns. Attempts to add or update CampaignCriterion.language for Search will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT.

Existing Search language criteria may remain but will no longer affect targeting. You may remove them, but cleanup is optional. If another internal system reads those objects, decide whether retaining inert criteria would mislead operators before choosing to leave them in place.

Do not apply the same rule indiscriminately to Performance Max. Its language setting still influences non-Search channels, so Performance Max will not return the same context error. Branch the workflow by campaign type instead:

Exclude language criteria from new Search campaign requests.
Remove language mutations from Search update jobs and templates.
Allow existing Search criteria to remain only if your interface clearly marks them as non-operative.
Preserve supported Performance Max language operations for the channels where they still matter.
Test both create and update paths so error handling does not hide unrelated failures behind the expected context error.
Update internal documentation, validation rules and campaign builders that still describe Search language selection as an enforceable control.

This is more than an API compatibility fix. If an internal campaign tool continues showing a required Search language selector, users may believe they established a boundary that Google no longer observes. Removing that false assurance is part of the migration.

Key takeaways

For Search and AI Max for Search, stop treating campaign-level language selection as a targeting restriction.
For Performance Max, preserve selected languages because they still guide YouTube, Display, Discover and Gmail, even though they no longer govern Search placements.
Use deliberately separated ad languages, clearly matched destinations and consistent labels to make automated decisions easier to diagnose.
Keep separate multilingual campaigns when budgets, markets, offers or goals require them, not merely to recreate a language switch that no longer controls Search delivery.
Remove Search language mutations from API workflows, while retaining campaign-type logic for Performance Max.

Start with the account inventory and the API branch before late September. Then run the ad-to-page language audit while the old structure is still familiar. You cannot restore the removed Search control, but you can make every language candidate intentional, measurable and supportable before automated matching decides where it belongs.

References

Search Engine Land — Google Ads is removing language targeting from Search campaigns

August 13, 2026

Campaign Manager 360 Real-Time Reporting API Guide

You need Campaign Manager 360 performance data inside a dashboard while someone is still looking at the screen. The traditional create-run-poll-download workflow can do the reporting, but it makes an interactive product carry the machinery of a batch job.

The reportData.query endpoint gives you a shorter path: describe the data you need in the request and receive structured JSON synchronously. That can simplify dashboards and ad-hoc analysis considerably. It does not mean every reporting workload should move, nor does the word “real-time” guarantee that every underlying metric is updated instantly.

The reporting flow is now a direct request-response path

The traditional Campaign Manager 360 reporting flow is built around generated reports. Your application creates a Report resource, runs it, polls until processing finishes, and downloads the resulting file. That sequence remains useful when the file is part of the deliverable, but it introduces several states that an interactive application must manage.

Create or identify the report configuration.
Start the report run.
Poll for completion.
Download and parse the generated CSV or Excel file.
Transform the result into the shape required by your interface or analysis.

With reportData.query, developers can instead specify dimensions, metrics, and filters in the request body and receive structured JSON in the response. You do not have to create a Report resource before asking for the data.

Define the dimensions that determine the result’s grain.
Select the metrics needed by the dashboard or analysis.
Apply filters that keep the request focused.
Submit the synchronous query.
Map the returned JSON into your application’s data model.

The practical gain is not simply fewer API calls. Your application no longer has to model a report job, persist its status, poll it, retrieve an artifact, and parse that artifact before it can show a result. For a user-driven dashboard, removing that orchestration can make both the code and the experience easier to reason about.

Keep the distinction precise, though: reportData.query simplifies the retrieval path. It does not make the Reports service obsolete, remove the need for a reporting data model, or turn an unfocused query into a fast one.

Choose the endpoint by workload, not by which API is newer

Two data-reporting routes show a short interactive query path beside a larger multistage batch-processing path.

The clearest implementation decision is based on how the result will be consumed. Use reportData.query when a person or application needs a structured answer immediately. Keep the Reports service when the workload is large, scheduled, or expected to produce a downloadable file.

Decision factor	reportData.query	Reports service
Interaction model	Synchronous request and response	Create, run, poll, and download
Response format	Structured JSON in the API response	Generated CSV or Excel file
Best fit	Interactive dashboards, real-time reporting experiences, and ad-hoc analysis	Large datasets, scheduled reporting, and file-based workflows
Configuration	Dimensions, metrics, and filters are supplied directly with the query	A Report resource defines the report before retrieval
Execution consideration	A query can run for up to 60 seconds	Completion is handled as an asynchronous report job

Four questions usually settle the choice:

Is a person waiting for the answer? A dashboard refresh, filtered table, or investigative view is a strong candidate for reportData.query.
Is the output itself a CSV or Excel deliverable? Keep the Reports service rather than retrieving JSON only to recreate the same file workflow.
Is this a large or scheduled extraction? The existing Reports service remains the preferred route.
Does the same system have both interactive and batch needs? Use both paths. A hybrid architecture is a deliberate workload split, not an incomplete migration.

This prevents a common architectural mistake: replacing a sound batch process merely because a more convenient interactive endpoint exists. The new endpoint solves a different access pattern. It should take over the requests that benefit from synchronous JSON while the Reports service continues handling work that benefits from generated files and asynchronous execution.

Design interactive queries that remain useful under pressure

A direct endpoint removes report-job ceremony, but your dashboard still needs a disciplined query layer. The following design choices determine whether reportData.query feels responsive and trustworthy in production.

Start with the user’s question, not every available field

Define one question for each dashboard component. A campaign summary, a filtered placement table, and a diagnostic drill-down do not need to share one universal request. Give each component the smallest dimension grain, metric set, and filter scope that answers its question.

Write down a compact query contract before implementation:

The decision or question the result supports.
The dimensions that determine what one result row represents.
The metrics the interface will actually display or calculate with.
The filters controlled by the application and the filters controlled by the user.
The behavior the user sees while the request is running.
The fallback shown when the request cannot return a usable result.

This contract helps you notice accidental scope growth. If a new chart needs a different grain, give it a separate query rather than quietly expanding an existing request and making every dashboard refresh carry the extra work.

Treat 60 seconds as a ceiling, not a target

The endpoint allows queries to run for up to 60 seconds. That accommodates meaningful interactive analysis, but a dashboard can still feel broken long before the request reaches its limit.

Design the interface for a genuinely synchronous operation. Show a clear loading state, keep unrelated controls usable, and decide what happens if the request takes longer than the user’s workflow can tolerate. Where appropriate, retain the last successful result and label it as such rather than replacing useful data with an indefinite spinner.

Do not hide a consistently slow query behind a longer loading message. Narrow its dimensions, metrics, or filters. If the workload is inherently large rather than accidentally broad, route it to the Reports service.

Do not equate synchronous retrieval with instant measurement

“Real-time” describes the reporting access pattern here: your application submits a query and receives data directly instead of waiting for a generated report file. That alone does not establish how quickly every underlying campaign event becomes available as a reportable metric.

If freshness affects an operational decision, verify it for the dimensions and metrics you use. Give the dashboard an “as of” indicator based on information your implementation can substantiate, and avoid labels such as “live” or “instant” unless you have validated what those words mean for that view. This keeps a faster retrieval method from creating a stronger freshness promise than the data supports.

Put a stable adapter between CM360 and the interface

Structured JSON is easier to consume than a downloaded file, but your UI should not become a direct reflection of a vendor response. Map the response into an internal model with names and types that make sense to your application.

Keep the API request definition in one reporting layer rather than duplicating it across dashboard components.
Validate that the returned structure contains what the component needs before rendering it.
Centralize metric labels and formatting so the same measure is not presented differently across views.
Record the query definition alongside operational logs so a bad result can be traced to its dimensions, metrics, and filters.
Version your internal contract when a dashboard changes its grain or meaning.

This adapter also preserves your options. The UI can consume one internal shape even if some views use reportData.query and other data arrives through the Reports service.

Separate no data, zero, slow, and failed

These states can look similar in an empty chart, but they mean different things:

No matching data: the selected dimensions and filters produced no rows.
Measured zero: the query returned a legitimate result whose displayed metric is zero.
Still running: the application has not received the synchronous response yet.
Failed request: the application cannot present the requested result.
Last successful result: a previous result remains visible while its replacement is unavailable.

Model and label these states explicitly. Otherwise, an API problem can be mistaken for campaign performance, or an empty filter result can be presented as a technical failure.

Also control how often the interface sends requests. Trigger queries on deliberate actions, avoid submitting a new request for every unfinished input change, and reuse identical results for an appropriate period when your freshness requirements permit it. The right reuse period is a product decision; the existence of a synchronous endpoint does not require every screen interaction to generate a new API call.

A low-risk rollout keeps the batch path intact

Parallel reporting pipelines pass through a controlled traffic junction and comparison stage, with a return route to the established batch system.

You do not need to redesign the entire reporting stack to benefit from reportData.query. Start with one view where report creation, polling, or file parsing is clearly getting in the way of an interactive experience.

Inventory the current flow. Identify where the application creates the Report resource, starts the run, polls, downloads the file, parses it, and transforms it for display.
Classify the use case. Confirm that a person or interactive application needs the result directly. Leave scheduled, large, and file-based jobs in the Reports service.
Write the query contract. Specify the exact dimensions, metrics, filters, expected result grain, loading behavior, and failure behavior for the selected view.
Build the response adapter. Convert the returned JSON into the internal shape already expected by the interface, or introduce a stable model that both reporting paths can use.
Verify meaning, not just transport. Compare the new view with the existing reporting output for the same requested scope. Investigate differences before assuming that receiving JSON means the migration is complete.
Exercise the slow and empty paths. Confirm that the interface remains understandable if a query runs for a substantial part of the allowed window, returns no matching data, or fails.
Switch only the interactive read path. Keep existing scheduled reports and downloadable exports running until there is an independent reason to change them.

Measure the rollout by what it removes from the interactive path: report-resource management, polling, file retrieval, and parsing. Do not judge it by how much legacy reporting code you can delete. If that code still supports a valid batch workload, retaining it is the correct design.

Campaign Manager 360 reporting API FAQ

Is reportData.query a streaming API?

No. Its documented interaction is a synchronous query that returns structured JSON. Your application requests a defined result; it is not described as subscribing to a continuous stream of campaign events.

Does “real-time reporting” mean every metric is instantly current?

Not on the evidence available for this endpoint. The direct synchronous response removes the generated-report workflow, but that does not by itself define the freshness of every underlying metric. Validate freshness for your use case before making a user-facing promise.

Should an existing Reports service integration be migrated completely?

No. Keep the Reports service for large datasets, scheduled jobs, and workflows that require CSV or Excel downloads. Move only the interactive and ad-hoc requests that benefit from direct JSON.

What is the best first use case?

Choose one narrowly scoped dashboard view whose user currently waits for a report job or whose implementation exists mainly to download and parse a file. Define its dimensions, metrics, and filters; build the JSON adapter; then compare its output with the established reporting path before expanding the rollout.

Your next step is small and concrete: identify one interactive report, write down the exact question it answers, and determine whether a synchronous query can answer it within the endpoint’s 60-second window. If it can, migrate that read path. If it is fundamentally a large export or scheduled artifact, leave it where it belongs.

References

Search Engine Land – Google adds real-time reporting endpoint to Campaign Manager 360 API

August 12, 2026

Google Ads Automation Changes: What to Audit Before Rollout

If your Google Ads account depends on Target CPA, Target ROAS, or existing Travel campaigns, your immediate job is not to predict what the automation will do. It is to preserve enough evidence to tell a platform change from a tracking problem, a copied setting, or one of your own account edits.

Two changes need attention. Google’s Smart Bidding rollout is scheduled to begin on August 17, 2026. Starting in Q3 2026, Google will also move existing Travel campaigns into Search campaigns for Travel. The right response is a controlled audit: document the current state, define business guardrails, and validate every migration instead of assuming automation preserved what matters.

Separate the confirmed changes from account-level guesses

These updates affect different parts of campaign management. The Smart Bidding change concerns how automated bidding behaves. The Travel change replaces one campaign structure with another. Combining them into a single theory about performance will make diagnosis harder.

For Smart Bidding, the important confirmed point is the August 17 rollout date. Advertisers have raised questions about whether long-standing Target CPA and Target ROAS practices will continue to behave as expected, but that uncertainty does not establish a universal performance outcome. It does not tell you that costs will rise, return will fall, or every account will need a new target.

The Travel migration is more concrete. Google plans to create new Search campaigns for Travel that mirror the closest equivalent settings from existing campaigns, preserving current settings where possible. The phrase “where possible” is the reason to audit. It describes an attempted mapping, not a guarantee that every control, report, or downstream workflow will remain identical.

The new Travel workflow brings travel feeds and formats together with AI Max capabilities, advanced bidding, search-term reporting, and campaign management. That consolidation may simplify future operations, but it also creates more places where an unnoticed mapping difference can be mistaken for a bidding problem.

Keep a simple assumption log with three labels: confirmed platform change, observed account behavior, and hypothesis. A rollout date belongs in the first category. A change in your campaign’s conversion volume belongs in the second. “The new bidding system caused it” remains a hypothesis until tracking, configuration, traffic mix, and normal business variation have been checked.

Build a control record before automation moves anything

A blank control console is protected under glass beside archived configuration layers, a clock, and a documentation device.

A screenshot of the campaign overview is not a sufficient baseline. It shows results, but it rarely captures the settings and measurement dependencies that produced them. Build a record that lets another account manager reconstruct the campaign’s starting state without relying on memory.

Identify every campaign using Target CPA or Target ROAS, including shared or portfolio-level bidding arrangements that affect more than one campaign. Separately inventory every campaign that will fall within the Travel migration.
Record each campaign’s budget, bidding strategy, current target, conversion goals, location settings, schedules, audiences, exclusions, and feed or asset connections. For Travel campaigns, also preserve the formats and feed relationships you expect the replacement campaign to use.
Export a representative performance baseline. Include spend, conversion volume, conversion value, CPA, ROAS, clicks, impressions, and the search-term information available to you. Choose a comparison period that reflects normal day-of-week patterns, conversion delay, and business conditions rather than selecting an unusually strong week.
Document the measurement layer. Record which conversion actions are primary, which actions bidding uses, how values are assigned, and which dashboards or external systems consume the campaign data.
Create a dated change register. Log the rollout or migration date, target changes, budget edits, conversion-setting changes, feed changes, and the person responsible for each decision.

Use Google Ads change history as evidence of what happened, but maintain an independent register for why it happened. A target edit made during a migration may be visible in change history; the commercial reason, expected effect, approval, and stop condition usually live elsewhere.

Do not use the bid target itself as your historical benchmark. A Target CPA is an instruction to pursue an average cost per selected conversion. Target ROAS expresses the conversion value sought relative to ad spend. Neither is proof that the account historically achieved that result, and neither tells you whether the underlying conversions were economically useful.

Audit the business signals before changing bid targets

Automated bidding can only optimize the goals and values it receives. Before deciding that a post-rollout movement requires a new Target CPA or Target ROAS, confirm that the account is still describing the business outcome you intend to buy.

Does the primary conversion represent a result the business can fund, or is bidding optimizing an earlier proxy action?
Are conversion values applied consistently across campaigns, products, destinations, or booking types?
Did a conversion action, value rule, attribution setting, tag, or import change near the rollout?
Does your evaluation window allow the account’s normal conversion delay to mature?
Has the underlying commercial limit changed even if the advertising metric has not? A target inherited from an earlier margin, price, or customer-value assumption may no longer be defensible.
Are budget limits preventing the strategy from operating under the same conditions as the baseline?

Write guardrails in business terms

Do not wait for performance to move before deciding what counts as material. Establish an expected range from comparable historical periods, then define the maximum spend or efficiency deterioration the business is willing to absorb while investigating. The guardrail should reflect actual economics, not a generic percentage copied from another account.

Pair that loss limit with a measurement gate. If conversion tracking or value reporting cannot be verified, do not treat the displayed CPA or ROAS as a reliable bidding diagnosis. Broad target and budget edits made against broken measurement can compound wasted spend. The safer response is to limit exposure with a budget the business can tolerate while the measurement problem is isolated.

Also define a maturity gate. Compare results only after the relevant conversions have had their usual time to arrive. An incomplete reporting window can make a normal delay look like a sudden loss of efficiency.

Diagnose movement in a fixed order

When results diverge from the baseline, check the measurement layer first. Then compare campaign settings, migration mappings, budgets, and eligibility. Next inspect search terms and traffic mix. Only after those checks should you treat changed bidding behavior as the leading explanation.

When commercially safe, change one major control at a time. Editing the bid target, budget, conversion goals, and campaign structure together may produce a new result, but it removes your ability to identify which edit mattered. If the account breaches its loss limit, protect the budget first; preserving a clean experiment is less important than containing an unacceptable business cost.

Choose a Travel migration path based on control, not convenience

An analyst evaluates two travel campaign pathways at a controlled junction in a generic airport operations setting.

Travel advertisers can migrate manually before their assigned transition or allow Google to perform the automatic replacement. Google will communicate account-specific timing through account notifications and email, so the first operational requirement is making sure those notices reach an accountable person.

Migration path	What you gain	Main risk	Required control
Manual migration	You choose the change window and can validate the new campaign before the scheduled automatic transition.	Your team must manage the mapping and may introduce its own setup differences.	Use a written preflight checklist, record the migration time, and compare the new campaign with the saved baseline.
Automatic migration	Google creates the closest-equivalent replacement and reduces the setup work required from your team.	Preserved where possible does not mean every setting, report, or dependency is guaranteed to match.	Review the replacement immediately and have an owner ready to contain spend if a material discrepancy appears.

Manual migration is usually the more controllable option when campaign settings are unusual, spend exposure is material, or internal reporting depends heavily on the current structure. Automatic migration may be reasonable for a simpler account with limited operational capacity, but it is not a hands-off option. Both paths require the same validation discipline.

Run this preflight before the Travel switch

Save the account notification and assigned migration timing.
Export the existing campaign configuration and its representative performance baseline.
List every feed, travel format, conversion goal, bid target, budget, location control, schedule, audience, and exclusion that should carry forward.
Identify dashboards, scripts, exports, or business reports that depend on the existing campaign name, identifier, or type. Because Google is creating a new campaign, test those dependencies rather than assuming they will follow automatically.
Assign an owner for the migration window and define the measurement, maturity, and loss-limit checks that will govern intervention.

Validate the replacement line by line

Start with configuration, not performance. Confirm the bidding strategy and target, budget, conversion goals, locations, schedules, audiences, exclusions, feeds, and travel formats. Check that the expected AI Max capabilities and search-term reporting are available within the new workflow without assuming they are configured exactly as your team intends.

Then test reporting continuity. Update any mapping that depended on the former campaign structure and make sure conversion value, cost, and search-term data still reach the reports used for decisions. Preserve the old exports and migration log even if the new campaign looks correct; they are your evidence if a discrepancy emerges after conversions mature.

Key takeaways

The Smart Bidding rollout begins August 17, 2026, but its schedule does not prove a particular account-level performance outcome.
Do not diagnose a bidding change until you have checked measurement, copied settings, budgets, eligibility, and traffic mix.
Set business loss limits and conversion-maturity rules before the rollout so that intervention is based on evidence rather than alarm.
Travel campaigns begin moving to Search campaigns for Travel in Q3 2026, either manually or through Google’s automatic migration.
Closest-equivalent settings still require line-by-line validation, especially where feeds, conversion goals, bid targets, and downstream reporting are involved.

Before August 17, preserve your bidding baseline and write the guardrails that will govern any response. For Travel campaigns, monitor the account-specific notice and choose the migration path that matches your capacity to validate it. Automation is manageable when you can prove what changed, when it changed, and which business limit determines your next move.

References

August 12, 2026

Google Campaign Data Import Validation: A Practical Workflow

You have a cross-channel dashboard ready for review, but some campaign numbers arrived through an import rather than Google’s native collection. The dangerous failure may not look like an error. A campaign can appear in the report while its cost, clicks, or impressions are absent, leaving a dashboard that looks complete enough to trust.

Google’s Campaign Data Import Validation Report gives you a quality-control checkpoint. It reviews non-Google campaign data and previously imported data, then highlights campaigns that may be missing cost, clicks, or impressions. The practical move is to treat this validation as a release gate for reporting, not merely as a troubleshooting screen.

Read each result as a completeness warning

The validation report is designed to help answer a narrow but important question: are essential reporting fields missing from imported campaign data? It does not remove the need to determine why a field is absent or whether a populated value is correct.

Keep three data states separate:

Present and correct: the imported value agrees with the originating platform for the same campaign and reporting window.
Present but incorrect: the field contains a value, but a mapping, transformation, unit, scope, or duplication problem changed its meaning.
Missing: the import contains no usable observation for a field that should have been supplied.

The validation report is especially useful for finding the third state. Do not automatically convert it into the first by replacing a missing field with zero. Zero means the platform recorded none of the activity being measured. Missing means you do not yet have a usable value. Treating those states as interchangeable can understate totals and make derived performance metrics look valid when they are not.

Missing field	What becomes unreliable	First question to ask
Cost	Spend totals and cost-based efficiency metrics	Did the source export contain spend in the expected unit and column?
Clicks	Click totals, cost per click, and click-through calculations	Was the source click field mapped to the imported click field?
Impressions	Exposure totals, click-through rate, and impression-based cost metrics	Was the impression field included for the same campaign and date range?

Run validation before the dashboard is released

A report that is checked after executives or clients have acted on it is an incident review, not a control. Put validation between the import and the reporting handoff.

Define the expected scope. Record the non-Google platforms, accounts, campaigns, and reporting window that the import is supposed to cover. Without an expected set, an omitted campaign can remain invisible because there is nothing to compare against.
Complete the import. Keep the import run, date range, and source files identifiable so that a flagged result can be traced back to the data that produced it.
Review the validation report. Identify campaigns with missing cost, clicks, or impressions. Include previously imported data in the review when it remains part of the reporting period.
Create an exception record. For every unresolved campaign, capture the platform, campaign, missing field, reporting window, owner, cause, and planned reporting treatment.
Repair the earliest broken layer. Correct the source extract, field mapping, transformation, or import scope instead of typing a replacement value into the final dashboard.
Import the corrected data and validate again. A change is not complete merely because the pipeline ran without an operational error. Confirm that the original warning has been resolved.
Reconcile against the originating platform. Compare campaign coverage and totals for the same reporting window before approving the dashboard.

Your pass condition should be explicit. Every expected campaign should either contain the applicable metrics or have a documented exception explaining why a metric is unavailable and how the campaign will be handled. If a platform genuinely does not provide a particular field, record that limitation rather than manufacturing a value.

Trace a missing metric to the layer that failed

A cutaway data pipeline shows one amber signal disappearing at a broken connection before the remaining signals reach a dashboard.

A validation flag identifies the symptom. Diagnose it in pipeline order so you do not waste time fixing a later layer that never received the data.

Check the source extract. Find the affected campaign and reporting window in the exported data. If the metric is absent there, the importer could not have populated it. Correct the export selection or document the source limitation.
Check field mapping. Confirm that the source column for cost, clicks, or impressions maps to the intended destination field. Pay attention to renamed columns and platform-specific labels.
Check transformations. Look for parsing rules, data-type conversions, filters, and blank-value handling that could remove a valid value before loading it.
Check scope. Compare the account, campaign, and date filters used in the extract with those used in the import. A valid metric from the wrong period does not repair the affected reporting window.
Check the load result. Verify that the corrected campaign row reached the imported dataset and that a repeated import did not create an unintended duplicate.

If several metrics are absent for the same campaign, check row coverage and scope before debugging each field independently. If only one metric is absent while the others are populated, inspect that field’s source column, mapping, and transformation path first. These are diagnostic priorities, not assumptions about the cause.

Fix the problem where it first appears. A manual patch in a dashboard may repair one visible number while leaving the import pipeline broken for the next refresh.

A clean validation result still needs reconciliation

Two sets of campaign data tokens are compared on an analyst desk, with one mismatched pair highlighted beside a complete dashboard.

Completeness and accuracy are different controls. A populated cost field can still contain the wrong currency, the wrong reporting period, a duplicate value, or data from the wrong campaign. Presence validation cannot establish that the number carries the intended meaning.

After resolving missing-field warnings, run these checks:

Campaign coverage: compare the imported campaign roster with the expected roster from each non-Google platform. Use a stable campaign identifier where one is available; names alone may be ambiguous.
Reporting window: confirm that both systems use the same start date, end date, and time-zone treatment.
Units and currency: verify that cost values have not been mixed across currencies or transformed into an unexpected unit.
Metric definitions: make sure the source field represents the same type of click or impression that your cross-channel report labels. Similar names do not guarantee identical platform definitions.
Aggregate totals: compare imported totals with totals from the originating platform for the same scope. Define how documented processing differences or rounding will be handled instead of accepting any unexplained mismatch.
Reimport behavior: determine whether a correction replaces, updates, or appends to previous data. Then check for duplication after the corrected load.

This second control catches an important failure mode: the wrong value in the right field. A fully populated import can pass a completeness check while still producing a misleading channel comparison.

Key takeaways

Use the Campaign Data Import Validation Report to identify non-Google and previously imported campaigns that may be missing cost, clicks, or impressions.
Treat a missing metric as unknown until you investigate it. Do not silently convert it to zero.
Validate after the import but before the data reaches a decision-making dashboard or recurring report.
Repair problems in the source extract, mapping, transformation, scope, or load rather than patching the presentation layer.
Reconcile campaign coverage and totals after clearing validation warnings because complete data can still be incorrect.

For your next reporting cycle, make the handoff require three items: validation status, a list of unresolved exceptions, and confirmation that source totals were reconciled. That turns imported-data quality from an assumption into a control someone must complete.

References

Search Engine Land — Google adds Campaign Data Import Validation Report

August 11, 2026

Google Merchant Center Outage: A Retailer’s Response Plan
If Google Merchant Center stops accepting updates or showing reliable account data, your first instinct may be to repair the feed, reset an integration, or pause campaigns. During a platform incident, those reactions can create a second problem inside an account that was otherwise healthy.

Your immediate job is to establish what failed, preserve evidence, protect essential commerce operations, and avoid changes that will be difficult to untangle later. Here is a practical response plan for doing that while Google’s investigation remains incomplete.

Start with what Google has and has not confirmed

The known incident window began on August 6 at 13:06 UTC. Google published its first public update at 17:46 UTC, four hours and 40 minutes later, and said it was investigating reports of a Merchant Center problem. At that point, Google had not disclosed the root cause, the affected features, the size of the impact, or an estimated restoration time.

That distinction matters. Acknowledgment of a Merchant Center incident supports the conclusion that at least some failures may be platform-side. It does not prove that every account, feed, product, country, interface, or connected campaign is affected. It also does not prove that an account-level error appearing during the same period was caused by the incident.

The potential exposure is meaningful because merchants use Merchant Center to manage product information for Google Shopping, Performance Max, and free product listings. But potential exposure is not confirmed impact. Until the affected functions are identified, describe what you can observe rather than declaring that listings or campaigns are universally down.

Key takeaways
- Use August 6 at 13:06 UTC as the start of the known incident window when comparing errors, sync logs, and account changes.
- Treat Google’s acknowledgment as evidence of a platform incident, not proof that every Merchant Center anomaly has the same cause.
- Preserve failed requests, error messages, timestamps, and intended catalog changes before retrying anything.
- Avoid deleting feeds, replacing the full catalog, rebuilding integrations, or broadly pausing campaigns without evidence that the action is necessary.
- Validate the source catalog, storefront, Merchant Center state, and campaign outcomes separately; one healthy or unhealthy layer does not establish the state of the others.
- After service appears to return, test a small reversible operation before releasing a backlog of product updates.
Separate a platform outage from an account problem

A status notice gives you context, but your own operational evidence tells you what happened to your business. Build a short incident record before anyone starts changing settings.
1. Record the first observed failure in UTC. Include the Merchant Center account, the user or integration involved, the attempted action, the affected products or feed, and the exact error text.
2. Preserve evidence. Save screenshots, export available logs, and retain copies of any files or requests that failed. Do not rely on someone remembering the message after the interface changes.
3. Find the last known successful operation. Compare its timestamp with the 13:06 UTC incident start. A cluster of failures after that time supports a platform explanation, although it does not prove one.
4. Check for changes that began outside the incident window. Recent access changes, expired credentials, malformed source data, integration deployments, or catalog edits can still produce independent failures during a wider outage.
5. Compare more than one signal. If a scheduled feed job failed, determine whether the source file was created correctly, whether the request reached Google, and whether the storefront still contains the intended price and availability.
6. Use read-only checks first. If a write test becomes necessary, make one already-intended, reversible change to a low-risk item and document it. Do not use the entire catalog as a test payload.
This process prevents a common diagnostic mistake: seeing two events at the same time and assuming one caused the other. The incident may explain an error, but timing, logs, and repeatable behavior should carry more weight than coincidence alone.

Protect sales without making the account harder to recover

Merchant Center sits between several operational layers. Your source catalog can be correct while an update fails to reach Google. Merchant Center can accept product data while a campaign has a separate delivery problem. Your website can remain accurate while an external commerce surface displays older information. Check each layer on its own terms.
- Keep the storefront accurate. Continue correcting prices, availability, and product details in the system that normally owns those values. If delivery to Merchant Center fails, queue the intended changes with timestamps so they can be reconciled later.
- Preserve the normal source of truth. Do not create an improvised second catalog merely to work around an unconfirmed failure. Competing sources can leave your team unsure which values should survive after recovery.
- Do not rewrite Product structured data just because Merchant Center is having trouble. Change website markup only when an independent validation shows that the markup or visible page content is wrong. A platform outage is not evidence of a schema defect.
- Inspect actual campaign outcomes before changing budgets or pausing Performance Max. A Merchant Center error may affect campaign operations, but the scope was not confirmed. Broadly pausing healthy activity can suppress valid demand; leaving uncontrolled spend running can also create exposure. Follow your normal spend guardrails and escalate if campaign controls are unavailable or the potential exposure exceeds your authority.
- Record manual interventions. Note who changed what, when it changed, why it was necessary, and how to reverse it. That log becomes the recovery checklist when Google restores affected functions.
Be especially careful with full-feed uploads and repeated retries. An automated integration may already be configured to retry failed work. Adding manual submissions without checking that behavior can create duplicate effort, obscure the original failure, or send older catalog data after a newer update.

Your internal update should also preserve uncertainty. A useful note has four fields: what is confirmed, what users are observing, what remains unknown, and when the next review will happen. For example, say that Google acknowledged a Merchant Center incident and that your team observed failed product updates after a recorded time. Do not say that all listings disappeared unless you have verified that outcome.

Verify recovery in stages before clearing the backlog

An interface loading successfully is not enough to declare recovery. The failing operation may still be unavailable, delayed, or returning inconsistent results. Use a staged check that limits the consequences of a false recovery signal.
1. Review the latest public incident update and record the time. Keep Google’s status timeline separate from the time your own account begins behaving normally.
2. Repeat the same read-only checks used during diagnosis. Confirm that account data, product records, and recent processing information are available where expected.
3. Retry one failed, reversible operation. Use the original intended data rather than inventing a new test change.
4. Confirm the result at the destination. A successful submission message does not by itself prove that the intended product state is visible or usable.
5. Release queued work in controlled batches. Start with time-sensitive price and availability changes, then reconcile less urgent catalog edits.
6. Check for stale, missing, or duplicated work. Compare the final Merchant Center state with the source catalog instead of assuming every automated retry completed correctly.
7. Review campaign delivery and spend independently. Product processing may recover before every connected workflow returns to normal, or campaign performance may have a separate cause.
8. Close the incident only after documenting the affected period, verified impact, interventions, unresolved items, and any follow-up controls your team needs.
Do not force a root-cause conclusion before Google provides one. Your internal review can still identify useful weaknesses: missing integration logs, unclear feed ownership, no queue for failed updates, excessive permissions, or a recovery process that depends on one person. Those are improvements you can make without pretending to know what caused the platform incident.

For now, anchor your decisions to timestamps and observed behavior. Preserve the catalog state you trust, make the smallest reversible intervention available, and require a successful end-to-end test before normal processing resumes.

References
- Search Engine Land — Google investigates Merchant Center outage
August 10, 2026
Google Search Ad Disclaimer Assets: A Compliance Workflow
If your Search ads must carry a required term, condition, or legal disclosure, Google’s text disclaimer asset gives that message a dedicated place. You no longer have to spend ordinary headline or description space on every piece of required wording.

The asset does not make compliance automatic. The critical failure mode is easy to miss: an ad can continue serving when its disclaimer is disapproved. You therefore need a launch and monitoring process that treats the disclosure as a requirement, not a decorative extension.

Treat the asset as a placement, not a compliance switch

Text disclaimer assets are available worldwide to Google Ads advertisers, including campaigns using AI Max. That broad availability solves a platform-access problem, but it does not decide whether your wording meets a law, regulation, licensing rule, contract, or internal policy.

Keep two approval gates separate. Your legal or compliance reviewer decides what the ad must communicate. Google decides whether the asset is accepted on its platform. Passing one gate does not mean you have passed the other, and platform approval should never be treated as legal advice.

The distinction matters because disclaimer failure does not fail closed. If a required asset is disapproved, Google may serve the associated ad without it. For a campaign that cannot lawfully or contractually appear without the disclosure, the safe operating rule is simple: do not permit the campaign to serve until the asset has been added, approved, and checked. If its status later changes, pause or otherwise prevent delivery until the problem is resolved.

Assign that decision before launch. The person watching the account should not have to interpret the legal significance of a missing disclosure during an incident. Your campaign record should state whether the asset is mandatory, who owns the approved wording, and what action to take if it becomes unavailable.

Write for the visible message, not merely the character limit

Each disclaimer can contain up to 90 characters. Treat that as an input limit, not a promise that all 90 characters will always appear. Disclaimer text may be truncated in some situations, including when larger font sizes are used or when certain languages require more display space.

There is no universal safe character count below 90 that eliminates that risk. Instead, draft the message so its most important meaning arrives first. Work through the copy in this order:
- Identify the indispensable statement. Ask your legal reviewer to distinguish wording that is required from wording that is merely explanatory or preferred.
- Lead with the material qualifier. Do not bury the condition at the end of a long sentence if losing that ending would change how a reasonable reader understands the offer.
- Name the scope precisely. Make it clear what product, price, audience, eligibility condition, or claim the qualifier applies to. Shorter language is not better if it becomes ambiguous.
- Remove promotional repetition. Brand language, benefits, and calls to action belong elsewhere in the ad. The disclaimer’s limited space should carry the disclosure.
- Count the final localized text. Do not approve only the source-language version and assume translations will fit. Review every language as its own display string.
- Review the truncated meaning. Examine what remains understandable if the ending is not visible. If truncation could make the ad misleading or noncompliant, the asset may not be a sufficient placement for that requirement.
A landing page can provide fuller terms, but it should not be used to justify an incomplete ad disclosure unless qualified counsel has confirmed that arrangement for the specific obligation. When the mandatory statement cannot fit reliably, change the ad, offer, landing experience, or campaign plan rather than forcing the legal language into an unsuitable container.

Rebuild the ad around Description Line 1 displacement

A disclaimer is not simply appended to an otherwise fixed layout. When the asset appears, it overrides a pinned Description Line 1. If you pinned that line because it carried a key offer detail, qualification, claim boundary, or call to action, adding the disclaimer changes the structure you thought you had locked down.

Audit the ad as a new composition. Start by writing down the job performed by the pinned first description. Then inspect the ad without that line and ask four concrete questions:
- Does any remaining claim become broader or more absolute when Description Line 1 disappears?
- Does the offer still make sense without a qualification that was carried only in that line?
- Can the disclaimer be understood without wording that was present only in the displaced description?
- Does the remaining copy still tell the user what they will reach after clicking?
If the answer to any of these is no, rewrite the whole ad unit. Do not depend on a pinned slot that the disclaimer can replace. Important context should survive the eligible combinations your campaign can actually show.

This also changes how you should test creative. Compare only configurations that satisfy the same approved disclosure requirement. Turning a legally required disclaimer off for an experimental control group is not an ordinary copy test; it creates a different risk condition. Let counsel decide whether disclosure-free delivery is permissible before any such comparison.

Use a launch sequence that closes the disclosure gap

Google requires the disclaimer to be added after the campaign has been created, through the Assets menu. That sequence can create a gap between campaign creation and disclosure setup. Close it deliberately:
1. Define the obligation. Record the campaign, offer, jurisdiction, audience, language, required wording, approving reviewer, and whether the ad may ever serve without the disclosure.
2. Prepare the final strings. Obtain approval for each language and campaign context, confirm that every string is within 90 characters, and document the exact approved version.
3. Create without releasing. Create the campaign while keeping it from serving. This gives you access to the post-creation asset workflow without exposing an undisclosed ad.
4. Add the disclaimer asset. Use the Assets menu, attach the approved text in the intended campaign context, and check that the saved wording matches the controlled copy exactly.
5. Audit the displaced description. Review the ad without its pinned Description Line 1 and rewrite any claim or offer that loses necessary context.
6. Verify both gates. Confirm the asset’s platform status and complete your own legal or compliance sign-off. Where feasible, inspect representative language, device, and larger-text conditions for truncation.
7. Activate with an incident rule. Release the campaign only after its required checks pass. Monitor the asset after material campaign or copy changes, and stop affected delivery if a mandatory disclaimer is disapproved or cannot be verified.
Your internal disclosure register does not need to be elaborate. A controlled sheet with the campaign identifier, exact text, character count, language, reviewer, approval date, platform status, and failure action is enough to make ownership visible. The important part is connecting an asset-status problem to an immediate operational response.

Apply the same controls to AI Max. Compatibility means the campaign type can use the asset; it does not remove the need to approve the wording, account for truncation, protect the ad’s meaning, or respond when the asset is disapproved.

Key takeaways
- Google Search text disclaimer assets are globally available, work with AI Max, and allow up to 90 characters.
- The campaign must exist before you add its disclaimer through the Assets menu, so keep it from serving during setup when disclosure is mandatory.
- A disapproved disclaimer does not necessarily stop the associated ad. Define a monitoring and pause rule before launch.
- The disclaimer can replace pinned Description Line 1. Review the ad as a changed composition, not as the old ad plus one extra line.
- Text can be truncated in some languages or at larger font sizes. Put indispensable meaning first and have qualified counsel determine whether the placement is sufficient.
Before your next regulated Search campaign goes live, add one explicit release condition: the approved disclosure must be present, eligible, and understandable without relying on the first description line. That single gate turns the asset from a convenient text field into a controlled part of your advertising workflow.

References
- Search Engine Land – Google publishes guidance for text disclaimers in Search ads
August 3, 2026

Tag: Campaign Management

Key takeaways

Start with voice, early branding and useful on-screen text

Make image assets belong in the YouTube feed

Prepare DV360 automation for the October deadlines

Oct. 1: specified exclusion controls are removed

Oct. 12: responsive ads need business identity assets

Run one joined creative-and-delivery sprint

References

The deadline matters, but the unspecified date matters more

Audit the features that will not transfer cleanly

Use a controlled six-step migration runbook

Rebuild audience and measurement assumptions for Demand Gen

Treat Lookalike Audiences as signals, not fences

Decide whether view-through conversions belong in optimization

Add new reach as a test, not a migration default

Key takeaways

References

Separate the category expansion from the platform migration

Key takeaways

Choose the narrowest truthful description of the business

Treat pre-badge leads as paid demand, not test traffic

Build a migration baseline instead of rebuilding the campaign

Use the new taxonomy as a content map, not an SEO shortcut

References

What generative AI resizing changes in Performance Max

Choose your control level from the asset, not the campaign

Review every generated ratio as a new piece of creative

Measure coverage and creative quality on separate scorecards

Key takeaways

References

Know exactly where the language setting stops applying

Rebuild multilingual control around the ad-to-page journey

Make landing-page language an operating requirement

Monitor language matching without waiting for a perfect report

Update Google Ads API workflows by campaign type

Key takeaways

References

The reporting flow is now a direct request-response path

Choose the endpoint by workload, not by which API is newer

Design interactive queries that remain useful under pressure

Start with the user’s question, not every available field

Treat 60 seconds as a ceiling, not a target

Do not equate synchronous retrieval with instant measurement

Put a stable adapter between CM360 and the interface

Separate no data, zero, slow, and failed

A low-risk rollout keeps the batch path intact

Campaign Manager 360 reporting API FAQ

Is reportData.query a streaming API?

Does “real-time reporting” mean every metric is instantly current?

Should an existing Reports service integration be migrated completely?

What is the best first use case?

References

Separate the confirmed changes from account-level guesses

Build a control record before automation moves anything

Audit the business signals before changing bid targets

Write guardrails in business terms

Diagnose movement in a fixed order

Choose a Travel migration path based on control, not convenience

Run this preflight before the Travel switch

Validate the replacement line by line

Key takeaways

References

Read each result as a completeness warning

Run validation before the dashboard is released

Trace a missing metric to the layer that failed

A clean validation result still needs reconciliation

Key takeaways

References

Start with what Google has and has not confirmed

Key takeaways

Separate a platform outage from an account problem

Protect sales without making the account harder to recover

Verify recovery in stages before clearing the backlog

References

Treat the asset as a placement, not a compliance switch

Write for the visible message, not merely the character limit

Rebuild the ad around Description Line 1 displacement

Use a launch sequence that closes the disclosure gap

Key takeaways