Tag: AI Max

How AI Is Rewriting Paid Search and Conversion Strategy

Your keyword coverage can be clean, your bids controlled, and your landing page tightly focused, yet the account can still miss how people now make decisions. AI is changing two parts of the journey paid search used to take for granted: how demand forms before a query and how much evaluation happens before a referral click.

That doesn’t make PPC obsolete. It changes the job. You now need a connected system for creating interest, capturing explicit intent, earning inclusion in AI-generated answers, and converting visitors who may arrive with most of their research already complete.

The click now sits inside a longer AI-shaped journey

Traditional search advertising begins when a person declares a need. A query can reveal the product, problem, constraints, and likely buying stage in a few words. The advertiser’s job is to respond with the right offer, message, destination, and bid.

AI-driven discovery adds two different jobs around that click. Before the query, a campaign may need to make an unrecognized problem feel worth investigating. After the query, an AI assistant may compare options, apply the user’s constraints, and present a shortlist before the user visits any website.

Google’s Demand Gen campaigns make the first change visible. They can reach people across YouTube, Shorts, Discover, Gmail, Maps, and the Google Display Network, where the person has not necessarily asked for the advertiser’s product. The creative must earn attention and create enough interest for the next question to form.

AI Mode makes the second change visible. Google has reported that its average AI Mode query is three times longer than a traditional query, while one in six AI Mode searches uses a non-text input such as an image or voice. A longer, contextual request gives the system more information about fit than a short keyword ever could.

Map each important offer across five decision states:

Unnamed need: The customer recognizes a situation but has not identified the underlying problem. Show the situation and its consequence.
Emerging interest: The customer understands the problem but may not know the solution category. Explain the outcome and how the category works.
Explicit search: The customer can name the product, service, or requirement. Match the query with a precise promise and destination.
AI-assisted evaluation: A search engine or LLM is comparing options against detailed constraints. Supply facts, distinctions, evidence, and clear fit boundaries.
Verification and action: The customer has a likely choice and wants to confirm it. Remove the final uncertainty and make the appropriate transaction easy.

Assign every campaign, creative concept, content page, and landing page to one primary state. If an asset cannot be placed, its job is probably too vague. A hard-sell form is a poor first response to someone who has only just recognized the problem; a generic educational page is equally unhelpful to someone checking a specific recommendation before buying.

AI Max turns campaign inputs into governance decisions

A strategist oversees glowing campaign inputs as they pass through human-controlled gates into branching AI-managed pathways.

The AI Max migration schedule turns platform automation from a distant trend into an operational deadline. Campaign-level Broad Match, legacy Automatically Created Assets, and Dynamic Search Ads are moving into the AI Max framework on different schedules.

Date	Platform change	What you should do
August 3, 2026	New Campaign-level Broad Match configurations and legacy Automatically Created Assets can no longer be created through the interface, Ads Editor, or API.	Stop designing new workflows around the retired structures and identify any existing campaigns that still use them.
September 1-30, 2026	Affected Broad Match and Automatically Created Assets campaigns are automatically migrated to AI Max.	Export a pre-migration baseline, document guardrails, and schedule post-migration quality assurance.
September 2026 and January 15, 2027	Dynamic Search Ads migration notices and reminders appear before the automatic transition.	Inventory DSA ad groups, their destinations, and every script or report that depends on the legacy structure.
February 1-28, 2027	Dynamic Search Ads begin migrating automatically, and new DSA ad groups can no longer be created.	Verify that the migrated campaigns still represent the intended products, pages, brands, and conversion goals.
Approximately September 2027	Older Google Ads API versions that retain legacy Broad Match and asset support are expected to reach their normal sunset.	Update integrations before the API deadline instead of relying on an old version as a permanent workaround.

Google says affected campaigns will be migrated in place with equivalent settings, and existing brand inclusions and exclusions should carry over. That reduces rebuilding work, but it does not remove the need for validation. A setting can transfer correctly while the campaign still behaves differently within the new system.

Use this migration checklist for every affected account:

Freeze a readable baseline. Record campaign structure, budgets, bid strategy, conversion definitions, destinations, brand rules, and performance over an evaluation window that reflects your normal conversion lag.
Map technical dependencies. List scripts, dashboards, API integrations, naming rules, bulk sheets, and alerts that refer to legacy campaign or asset entities. Future API versions released after September 1 remove support for the retired entities, even though older versions continue until their scheduled sunset.
Restate the business guardrails. Write down which brands, offers, locations, claims, pages, and conversion actions are eligible. Platform settings should reflect a decision that exists outside the platform.
Separate migration from experimentation. Do not combine the structural transition with a budget increase, new attribution model, bid-strategy change, and landing-page redesign. If performance moves, you need a plausible way to identify why.
Run outcome-level quality assurance. Compare destination use, branded and non-branded distribution, conversion mix, cost per qualified outcome, and revenue efficiency against the baseline. A stable headline conversion count can conceal a shift toward weaker actions.

The central control is your conversion objective. Automation can pursue only the outcomes and constraints it receives. If a low-value form submission and a completed sale are treated as interchangeable signals, more automation will not repair the underlying definition.

Creative must create intent, not decorate the campaign

When there is no keyword, the creative has to carry the context that the query used to provide. It must identify the relevant person, surface a recognizable problem, demonstrate an outcome, answer an objection, and propose a next step that matches the viewer’s current intent.

Use a brief that can survive automation

A list of dimensions is not a creative strategy. Give the media buyer, writer, designer, and video producer the same brief:

Audience situation: What is happening in the person’s work or life when this message becomes relevant?
Problem trigger: What should the opening three seconds communicate before the viewer scrolls away?
Desired response: Should the viewer recognize a problem, understand a category, compare approaches, or feel ready to act?
Core proof: What demonstration, product detail, customer evidence, or explanation makes the promise credible?
Primary objection: Which concern must this concept resolve: complexity, fit, effort, risk, price, or uncertainty?
Placement behavior: Will the idea still make sense in a vertical short, a square image, and a longer landscape video?
Next action: Is the appropriate step to learn, compare, configure, request information, or buy?

Supply formats that fit the placement instead of cropping one master asset into every slot. Google’s own guidance calls for vertical, square, and landscape assets plus a combination of image and video. In Google’s global campaign data, advertisers using both image and video received 6% more conversions at the same spend than advertisers using images alone. That is a platform-reported aggregate, not a forecast for your account, but it gives you a sound reason to test format diversity rather than treating it as optional polish.

Test concepts before you test cosmetic variations

Three versions of the same product image are not three different ideas. Build distinct concept families around the problem, the demonstration, the comparison, and the proof. Then adapt each viable concept to the required placements.

Write a hypothesis before launch. For example: showing the workflow will reduce uncertainty for people who understand the category but doubt the setup effort. Label assets by that hypothesis, not just by file size or color. When results arrive, you can decide whether the underlying message deserves another iteration rather than merely declaring one crop the winner.

Treat audience settings as distribution hypotheses, not customer understanding. Demand Gen can use first-party data, lookalike segments, interests, behavioral signals, and optimized targeting, but those controls do not tell you why a person cares or what prevents action. Brief the audience in terms of situation, belief, desired outcome, objection, and required proof. Feed what you learn from creative response and conversion quality back into the next audience and message decision.

LLM referrals need proof before pressure

An informed visitor approaches a landing-page space where evidence, transparent product details, and trust markers are presented before sales pressure.

A paid-search click and an LLM citation click can land on the same URL while representing different moments. The PPC visitor may be beginning a comparison. The LLM visitor may have already given an assistant detailed constraints, reviewed a synthesized answer, and clicked because they need confirmation or a transaction the assistant cannot complete.

That selection effect can produce unusually strong conversion rates at modest volume. In one published dataset, LLM referral traffic converted at 20%, which was 61% higher than paid search. Do not adopt those figures as an account benchmark. Use them as a reason to isolate the channel and test whether its visitors behave differently in your own funnel.

Build the page for verification

A stripped-down PPC page often assumes that fewer choices and a dominant call to action will improve focus. That can fail when a visitor expects to verify a nuanced AI recommendation. If the promised detail has been replaced by a gated form and a generic benefit list, the page breaks continuity with the answer that produced the click.

Build the destination in layers so a ready buyer can act without hiding the evidence from a careful evaluator:

Confirm the answer immediately. State what the offer is, who it fits, and which problem or decision the page resolves. The heading should make the citation click feel intentional rather than accidental.
Expose the decisive facts. Make capabilities, constraints, integrations, process details, pricing conditions, or product specifications easy to find when they are relevant to the decision.
Show why the claim is credible. Use original data, a transparent method, named expertise, demonstrations, and clearly attributed evidence where available. Content with unique information gives an AI system a stronger reason to cite it in the first place.
State fit boundaries. Explain who the offer is for, who may need a different option, and which limitations matter. This helps a visitor test the AI’s recommendation against their actual edge case.
Offer more than one sensible next step. Keep the primary purchase, demo, or inquiry action visible, but also provide a route to documentation, a detailed comparison, or implementation information.
Make the page machine-readable without making it robotic. Use descriptive headings, direct answers, consistent entity names, and structured data that matches the visible content. Schema can clarify evidence; it cannot manufacture evidence the page does not contain.

You do not necessarily need separate websites or duplicate pages for PPC and LLM traffic. A single destination can place a concise answer and action near the top, then provide navigable evidence below. The requirement is message continuity, not a separate URL for every channel.

Measure LLM conversion as its own behavior

Create distinct reporting segments for paid search, Demand Gen, and identifiable LLM referrals. Preserve the referring channel and landing page, then connect the session to downstream outcomes whenever your consent, analytics, and customer systems allow it.

Report more than the first conversion:

Sessions and conversion rate by referral type and landing-page class.
The mix of purchases, forms, calls, trials, and other conversion actions.
Qualified-lead, opportunity, or completed-sale rates where the buying cycle continues offline.
Revenue, order value, or another business-quality measure appropriate to the offer.
Time from the referral session to the completed outcome.
Assisted conversions when an LLM visit informs a later branded search, direct visit, or paid click.

Compare like with like. A high-intent citation click should not be judged against every upper-funnel ad impression or every broad paid-search visit. Segment by decision stage, destination, and conversion definition before concluding that one channel is more efficient. Otherwise, you risk confusing a more selective click with a universally better acquisition channel.

Key takeaways: run paid media, GEO, and CRO as one loop

Choose one commercially important offer. Avoid beginning with an account-wide rebuild. A contained offer gives you a readable path from demand creation to revenue.
Map its five decision states. Identify the message, asset, channel, destination, and appropriate action for each state from unnamed need through verification.
Audit the automation boundary. Check affected Google Ads structures against the AI Max schedule, record a baseline, document business guardrails, and update scripts or API integrations before their legacy support disappears.
Build creative around hypotheses. Create distinct problem, demonstration, comparison, and proof concepts. Adapt viable ideas to native placements instead of treating format variants as the strategy.
Give each visitor the evidence their click implies. Preserve fast actions for ready buyers while making detailed facts, fit boundaries, and supporting evidence accessible to AI-referred visitors.
Join acquisition and conversion reporting. Segment paid-search, demand-generation, and LLM traffic, then judge them by qualified outcomes and revenue rather than blended conversion rate alone.

At your next account review, pick the single offer where an AI Max migration, a creative gap, or an LLM referral pattern is already visible. Record the baseline, change one part of the system, and follow the result through to business quality. That is the practical path from AI-driven reach to conversion you can defend.

References

August 14, 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

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 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

AI-Generated Creatives in Google Ads: A Practical Control Plan

You turned on AI-generated assets to cover more searches without writing every headline and description by hand. The hard part is not getting Google to produce usable copy. It is giving the system enough freedom to improve relevance without letting it invent an offer, weaken an audience qualifier, or claim credit for conversions that merely moved from another campaign.

Treat AI creative as controlled production, not unattended optimization. Start where automation has a clear job, encode the claims it must not make, review what it produces, and judge the result at account level. That operating model gives you useful scale without making brand safety and performance impossible to audit.

Give AI creative a narrow job before expanding it

Your best-managed campaigns are rarely the safest place to begin. Their assets may reflect years of query analysis, qualification language, pinning decisions and offer testing. Replacing that accumulated control with generated variants creates a high bar: the automation must outperform deliberate human work without disrupting traffic elsewhere.

A better starting point is a long-tail campaign that performs acceptably in aggregate but receives less creative attention. In an evaluation spanning ecommerce, B2B lead generation and B2C lead generation, AI text customization was less effective than human asset management in highly optimized campaigns but useful in the less-attended long tail. That is directional evidence, not a universal promise, but it gives you a sensible placement rule: use automation first where the alternative is limited human coverage, not where your team already has a refined message.

The scale of that evaluation matters. Its selected campaigns were nonbrand, spent at least $20,000 per month and contained at least 100 ad groups. Those were eligibility conditions, not minimum requirements for using AI Max. If your account is smaller, do not assume the same behavior or copy those thresholds as a prescription.

Select a nonbrand campaign with a stable conversion setup. Brand traffic can hide weak creative because the searcher already knows what they want.
Prefer a long-tail campaign with a real coverage gap. Define that gap explicitly, such as neglected ad groups or repetitive assets that do not reflect query themes.
Avoid a first test in campaigns that depend heavily on pinning. Pinning often protects message order, legal language or audience qualification. If it is essential, do not remove it merely to make the test easier.
Keep final URL expansion off during the initial creative test. If copy and destinations change together, you will not know which intervention caused the result.
Write down the permitted scope. Name the campaign, ad groups, markets, offers and landing pages included. Anything not listed remains outside the test.
Define the stopping conditions before launch. Pause or narrow the test if generated copy misstates the offer, attracts the wrong audience, shifts valuable traffic from established campaigns or reduces account-level business results.

Do not enable every automation in the same experiment. A test that changes copy, query matching and landing-page selection at once may produce a result, but it will not produce a useful decision.

Turn brand policy into enforceable messaging restrictions

Abstract advertising asset cards pass through policy gates, while noncompliant cards are diverted into a separate review bin.

AI Max text customization can tailor assets to the keywords in each ad group. That flexibility is also the risk: auto-created assets can promote products, services or promotions that the advertiser does not offer. A general instruction to follow the brand voice is too vague to prevent that failure.

Messaging restrictions should translate your approval policy into explicit boundaries. The fastest way to find those boundaries is to make the model fail deliberately before Google writes on your behalf.

Build an approved-claims inventory. List the products and services you sell, the audiences you serve, the promotions currently available, the geographic limits and any wording that must appear.
Generate ordinary sample ads. Use Gemini to produce initial assets from the approved inventory. Mark anything that is factually wrong, commercially misleading or off-brand.
Red-team the message. Prompt the model to become overly promotional, make stronger promises, broaden the audience and invent adjacent offers. The goal is to expose plausible copy that your team would reject.
Convert each failure pattern into a restriction. Write a direct rule for the category, not just the rejected sentence. For example: do not imply guaranteed outcomes; do not mention discounts unless an approved promotion is supplied; do not advertise services outside the approved list.
Run the hostile prompts again. Keep refining the restrictions until the generated set remains within your approved boundaries, including when the prompt pressures the model to overstate the offer.
Assign an owner and version the restrictions. Record who approved them and which campaigns use them. When the offer or brand policy changes, update the restrictions before expanding automation.

Audience qualification deserves its own rules. A B2B ad often needs to discourage consumers while attracting business buyers. If phrases such as “for businesses,” an industry requirement or another qualifier are essential and accurate, protect them. A higher conversion count is not an improvement if the generated copy removes the language that kept unsuitable leads out.

Restrictions are preventive controls, not approvals. They reduce the range of unacceptable output, but every generated asset can still fail in a way you did not anticipate. That is why the next layer is asset-level review.

Review every asset, then measure the whole account

Inspect generated copy before it earns material delivery

Generated assets can be easy to miss in the interface. When looking for them, change the default filters so the ad is included; that option is not selected by default. Review newly created assets repeatedly while the test is active and remove unacceptable variants before they collect substantial impressions.

This is not a ceremonial check. In the monitored ecommerce and B2C activity, excluding the B2B result, reviewers removed approximately 19% of auto-created assets. That percentage should not be treated as an industry benchmark, but it demonstrates why an enabled feature cannot also be an assumed approval.

Offer accuracy: Does the company sell exactly what the asset promises?
Claim support: Could the team substantiate every benefit, comparison and outcome?
Promotion validity: Is the price, discount or time-sensitive offer real and currently available?
Audience fit: Does the wording retain the qualifiers that separate suitable buyers from unsuitable clicks?
Destination alignment: Can the landing page fulfil the expectation created by the ad without making the visitor search again?
Brand acceptability: Would the team approve this language if a person had written it?
Disclosure status: If the asset is an AI-generated or AI-modified image or video, has its provenance and required labelling been recorded?

Separate campaign performance from incremental growth

A successful-looking automated campaign can be a redistribution mechanism. In the ecommerce evaluation, AI Max initially appeared highly successful, but deeper analysis found that it was taking impressions, clicks and conversions from other campaigns while total account revenue declined. The local dashboard improved while the business result worsened.

Review level	What to inspect	Warning sign	Response
Asset	Generated headlines and descriptions	Unsupported claims, invalid offers or lost qualifiers	Remove the asset and strengthen the matching restriction
Search term	Queries receiving impressions, clicks and conversions	Valuable intent moves from a controlled campaign into the automated one	Improve query routing with keywords and negatives
Campaign family	Results across the test campaign and campaigns serving similar demand	The test gains while established campaigns lose comparable volume	Treat the gain as possible cannibalization and narrow the scope
Account	Total revenue or qualified lead outcomes	The automated campaign improves while the account declines	Do not declare a win; correct routing and rerun the test

When search-term overlap appears, use the observed data to restore control. In the ecommerce account, the response was to add relevant search terms as keywords, introduce more negative keywords and use audience lists to slow cannibalization before rerunning the test. Those controls are not a guaranteed recipe for every account. They illustrate the right sequence: diagnose where demand moved, change routing, and then test again rather than accepting campaign-level attribution at face value.

For ecommerce, keep account revenue in view. For lead generation, inspect qualification and downstream outcomes, not just submitted forms. In both cases, ask the decisive counterfactual: did the AI creative create additional business, or did Google move existing demand into a campaign that could claim it?

Make AI disclosure a workflow, not a last-minute badge

Two marketers review blank creative cards at a light table as approved assets are linked to provenance markers and campaign containers.

Creative governance now includes provenance. Google is gradually rolling out AI content labelling across Google Ads, Display & Video 360, Campaign Manager 360, Merchant Center and Google Ads Editor. Advertisers can add text or visual disclosures to eligible image and video creatives or use the platform’s AI label setting. Labelled assets display an AI disclosure icon where they appear.

Google may also label certain assets created with its own AI tools automatically. Those platform-applied disclosures do not violate the existing creative policies that prohibit text overlays or watermarks. Neither point means that every AI-assisted asset will be identified for you, especially while availability is rolling out gradually.

Record the asset’s origin. Mark each image and video as human-created, AI-generated or AI-modified.
Record the production path. Keep the tool, responsible owner and approval status with the asset so the team can answer how it was made.
Map where it will run. List the campaigns and markets using the asset; disclosure obligations can vary by jurisdiction.
Apply the relevant label. Use the built-in setting or an eligible text or visual disclosure as appropriate, then verify the status in the available AI Label field and the rendered ad.
Retain the approval record. If an asset is revised, update its provenance and reassess whether its disclosure status changed.

The built-in control is not a legal safe harbor. It was designed to help advertisers address emerging transparency requirements in markets including the European Union, India and New York, but using Google’s AI label setting alone does not guarantee compliance. If your campaigns create regulatory exposure, obtain jurisdiction-specific legal guidance instead of treating a platform toggle as the final interpretation of the rules.

Keep the four controls separate. A disclosure explains that AI was involved. A messaging restriction limits what the system may say. Human review decides whether a particular asset is acceptable. Account-level measurement decides whether the automation creates incremental value. None can substitute for the others.

Key takeaways

Start AI-generated copy in a nonbrand, long-tail campaign where creative coverage is limited, not in the account’s most carefully optimized campaign.
Test creative separately from final URL expansion so you can attribute the result to the asset change.
Red-team your own offer, then convert every unacceptable claim, promotion and audience expansion into a messaging restriction.
Review auto-created assets explicitly and measure search-term movement, related campaigns and total account outcomes before calling the test successful.
Track the provenance of AI-generated and AI-modified images and videos; use Google’s labels where applicable, but verify legal requirements separately.

Your next move is small: choose one bounded long-tail campaign, write its prohibited claims and audience rules, and record the account-level outcome that must improve. Do not expand AI creative until the generated assets pass review and the account shows genuine additional value rather than rearranged attribution.

References

July 28, 2026

How to Grow Product Discovery With AI-Powered Google Ads

If you run Google Ads for a large product catalog, your next growth problem may not be finding more keywords. It may be helping Google’s systems understand which products fit searches that are longer, more specific, and harder to classify.

That changes the work. You need product data that makes relevance clear, a controlled way to give overlooked SKUs another chance, and measurement that distinguishes genuine discovery from automated spend.

The opportunity has shifted from keywords to interpretable intent

A conventional product query might name a category and little else. A conversational query can include the shopper’s use case, constraints, preferred features, and stage of decision-making in one sentence. That extra context is commercially valuable if the ad system can interpret it and find a suitable product.

Google says AI Max can match ads to complex or ambiguous searches that traditional keyword targeting could not readily monetize. The company described this as billions of additional potential ad-bearing searches. AI Max had also moved out of beta and reached more than 500,000 advertisers by Alphabet’s Q2 2026 earnings call.

The scale is notable, but it shouldn’t be mistaken for a performance guarantee. Google attributes an average 15% lift in conversions or conversion value at a similar return on ad spend to advertisers using AI Max or Performance Max. It also says Gemini has improved Shopping-ad relevance for complex queries by about 20%. These are aggregate, vendor-supplied figures. Your result will depend on your catalog, margins, tracking, offers, product information, and the demand available in your market.

The important distinction is that better matching creates reach; it does not manufacture qualified demand. A shopper still needs a real problem, and your product still needs to solve it at an acceptable price. Treat AI-powered reach as an opportunity to enter more relevant decisions, not as proof that every new impression is valuable.

Layer	Primary job	What you need to control	Question it should answer
AI Max	Interpret more complex Search intent and connect it with an eligible ad	Offer clarity, creative relevance, landing-page quality, and conversion measurement	Are we entering useful searches that our earlier targeting missed?
Performance Max recovery campaign	Give underexposed products a separate opportunity to collect serving and performance signals	SKU eligibility, campaign isolation, budget limits, entry rules, and exit rules	Which overlooked products can earn their way back into the main campaign?

Google is also testing AI Mode formats that move ads closer to an answer experience. Highlighted Answers can place labeled sponsored links in AI-generated lists, while contextual sitelinks and Direct Offers are intended to respond to information surfaced during a conversation. These formats indicate where discovery could go, but they are still developing. Build your strategy around accurate product evidence and sound economics, not an assumption that any particular experimental placement will become material.

Give Google a product record it can match to real needs

An unbranded hiking shoe is surrounded by visual product attributes that connect it to a matching shopper intent.

When matching moves beyond literal keywords, the quality of your inputs matters more. Google needs enough consistent information to connect a shopper’s stated need with the product that can satisfy it. A generic title, thin product page, recycled image, and incomplete feed leave the system very little evidence to work with.

Translate conversational intent into product evidence

Start with the language of a decision, not a list of keyword variants. A useful intent statement combines the product, the intended use, and the constraint that will decide the purchase. For example, a shopper may need an item for a particular environment, compatible with equipment they already own, within a size limit, or suitable for a specific recipient.

For each important intent, create a short query-to-evidence record:

Write the shopper’s need in plain language.
Identify the product fact that proves suitability, such as dimensions, material, compatibility, capacity, fit, intended user, or supported use.
Confirm that the fact is accurate and present in the feed where an appropriate attribute can carry it.
Show the same fact in the creative when it is visually or verbally important.
Make the proof easy to find on the landing page, close to the price and purchase decision.

This isn’t a keyword-stuffing exercise. Repeating a phrase doesn’t establish relevance. A precise compatibility statement, measurement, material, or use limitation gives the system and the shopper something concrete to evaluate.

Your feed, visible product page, and Product structured data should also agree. Check prices, availability, variants, identifiers, names, and decisive attributes across those surfaces. If they conflict, you are asking automated systems to resolve uncertainty at the moment they should be deciding whether to show the product.

Use the same standard for creative assets. The image and copy should distinguish the SKU rather than merely represent its category. If two products solve different problems but use interchangeable descriptions and images, the system has weak evidence for choosing between them.

Apply an eligibility gate before buying more reach

Not every low-traffic SKU deserves more exposure. Before a product can enter an AI-powered discovery or recovery campaign, verify that it is:

Currently sellable, correctly priced, and available to the intended customer.
Economically viable under the budget and loss limits you are prepared to accept.
Represented by accurate feed data, useful creative, and a functioning landing page.
Distinct enough that you can explain why someone would choose it over nearby products in your own catalog.
Appropriate for the current season and market rather than temporarily irrelevant by design.
Measured by a conversion action that reflects business value, not merely an easy on-site interaction.

This gate prevents a common misreading of automation. More reach can reveal latent product demand, but it can also expose weak merchandising faster. If a SKU is unavailable, poorly differentiated, or uneconomic, the right action is to repair or exclude it rather than pay an algorithm to rediscover the same problem.

Create a recovery lane for products the algorithm stopped testing

A sidelined unbranded product travels along a separate recovery lane back into a glowing automated testing route.

Large catalogs develop a performance feedback loop. Products with strong history keep winning impressions and conversions. Products with little history receive less traffic, which leaves them with even less evidence to compete for future traffic. A viable SKU can become invisible without ever receiving a clean test of demand.

A recovery campaign interrupts that loop. It moves eligible but underexposed products into a dedicated Performance Max campaign, where they can receive another opportunity to generate impressions, clicks, and conversions. The goal is not to force every product to spend. It is to separate lack of opportunity from lack of demand.

Define a recovery SKU with rules you can audit. Its status should mean that the product is sellable and strategically eligible but has fallen below your business’s floor for meaningful opportunity during a chosen lookback period. Align that period with your buying cycle and seasonality. A universal impression or click threshold would be misleading because catalog size, price, purchase frequency, and demand differ.

Your operating rules should cover five decisions:

Entry: What combination of low impressions, low clicks, or absent conversion opportunity qualifies an otherwise viable SKU?
Exclusion: Which products are intentionally paused, out of season, unavailable, disapproved, unprofitable, newly launched under a different process, or missing required data?
Isolation: How will you remove the product from its original Shopping campaign while it is in recovery so the campaigns do not overlap?
Graduation: What evidence means the product has earned a return to its original campaign?
Retirement: When should repeated spend without useful progress end the test?

Isolation is essential. If a recovery SKU remains active in its original campaign, you won’t know which environment produced its new opportunity, and the two campaigns may compete to serve the same product. The label that admits a SKU to recovery should also trigger its exclusion from the original campaign.

At catalog scale, automate the movement rather than relying on periodic manual cleanup. One working pattern uses BigQuery to evaluate each SKU, a Google Sheet to carry eligible IDs, Feedonomics to apply a custom label, and Google Ads to route labeled products into a dedicated Performance Max campaign. When a SKU no longer meets the recovery criteria, the label is removed and the product returns to its original campaign.

You don’t need that exact technology stack. You do need one authoritative SKU list, deterministic entry and exit logic, an automated feed label, mutual campaign exclusions, and a log of every movement. Without those controls, a useful recovery strategy becomes a recurring campaign-maintenance task with unreliable measurement.

The potential is visible in an early two-week implementation involving 13,829 previously overlooked SKUs. Those products moved from zero activity to 198,774 impressions, 1,617 clicks, $5,072.17 in cost, 24.42 conversions, and $5,161.70 in conversion value. That produced 101.77% ROAS during the recovery period.

Those figures demonstrate that an isolated campaign can restart data collection; they are not a general benchmark for profitability. The result came from one early implementation, and its stated objective was rehabilitation rather than maximizing immediate ROAS. The decisive test comes later: whether graduated products retain useful performance after returning to their normal campaign structure.

Measure discovery separately from harvest performance

A mature Shopping campaign usually optimizes around revenue, conversion value, or ROAS. A product-recovery campaign has an earlier job: determine which neglected SKUs can attract qualified attention and build enough evidence to rejoin the main system. Applying only the mature campaign’s efficiency target can recreate the same feedback loop you are trying to break.

That does not mean cost is secondary or unlimited. Automation can spend quickly, so define the campaign budget, the maximum acceptable loss, and the conditions for stopping an unproductive SKU before launch. Discovery is a learning objective, not permission to buy data indefinitely.

Track each entry cohort through a measurement ladder:

Eligibility: How many products passed the data, availability, margin, and operational checks?
Activation: What percentage of entering SKUs received at least one impression?
Engagement: What percentage received at least one click, and how much did that engagement cost?
Commercial evidence: Which SKUs generated conversions or conversion value while in recovery?
Graduation: What percentage met the exit condition and returned to the original campaign?
Post-return performance: Did graduated SKUs continue receiving impressions, clicks, conversions, and value after re-entry?
Incrementality: Did the process produce more total catalog value, or merely redistribute traffic that other products would have captured?

Keep the cohort log at product level. At minimum, record the SKU, entry date, reason for entry, prior campaign, recovery impressions, clicks, cost, conversions, conversion value, exit date, exit reason, destination campaign, and post-return results. This record becomes more important as AI matching reduces your visibility into exactly how every query was interpreted.

Four simple derived metrics make the operation easier to manage:

Activation rate = SKUs with an impression divided by SKUs entering recovery.
Engaged-product rate = SKUs with a click divided by SKUs entering recovery.
Graduation rate = SKUs meeting the exit rule divided by SKUs entering recovery.
Cost per graduated SKU = total recovery spend divided by the number of graduates.

These metrics won’t replace revenue or ROAS. They tell you where the recovery mechanism is working or failing before you evaluate downstream commercial value.

Observed pattern	What it may mean	First place to inspect
No impressions	The SKU may still be ineligible, poorly routed, or too weakly described to enter auctions	Feed status, custom label, campaign inclusion, exclusions, and core product attributes
Impressions but no clicks	The product may be eligible without appearing relevant or competitive to the shopper	Title, image, differentiating attributes, price, and fit between product and intended use
Clicks but no commercial action	The ad may create interest that the offer or landing experience does not convert	Page consistency, availability, variant selection, price, purchase friction, and conversion tracking
Conversions in recovery but little activity after graduation	The main campaign may be suppressing the product again	Core campaign segmentation, prioritization, and the graduation rule
Spend rises while graduation stalls	The cohort may contain weak products or permissive entry rules	Loss ceiling, SKU economics, retirement criteria, and eligibility gate

Treat these as diagnostic starting points, not automatic conclusions. Several causes can produce the same pattern. A click without a conversion, for example, could reflect the offer, the landing page, measurement, or simply insufficient evidence. Inspect the full path before changing bids or removing the SKU.

If you need to estimate incrementality, keep a comparable group of eligible products outside the recovery campaign or introduce cohorts in stages. Compare total catalog outcomes, not only the isolated campaign’s dashboard. Without a comparison, a rise inside the recovery campaign cannot tell you how much demand was genuinely added versus shifted from another product or campaign.

Key takeaways

AI Max expands the range of Search intent Google may be able to monetize, while a Performance Max recovery campaign can give overlooked products a separate route back into consideration.
Better matching begins with discriminating product facts carried consistently across the feed, creative, visible landing page, and structured data.
A low-traffic SKU is not automatically a bad product. Separate products that lack opportunity from products that are unavailable, uneconomic, seasonal, or genuinely unwanted.
Use explicit entry, exclusion, graduation, retirement, and loss rules. A recovery campaign should be a controlled system, not a permanent holding area.
Measure activation, engagement, graduation, and post-return performance before deciding whether the process creates durable value.
Google’s aggregate lift figures are directional context, not targets for your account.

Your practical next step is to export product-level performance for a lookback period that fits your purchase cycle. Filter for sellable SKUs that received no meaningful opportunity, inspect their product records, and admit only the clean, viable candidates to a bounded recovery cohort. Give every SKU an entry reason, an exit condition, a loss ceiling, and a scheduled post-return review. That is how AI-powered reach becomes a product-discovery system you can govern rather than another opaque campaign setting.

References

July 24, 2026

Google Ads AI Automation: A Practical Control Framework
Your Google Ads account can hit its conversion target while the business quietly loses ground. Spam leads, duplicate customers, weak inquiries, irrelevant searches, and unsuitable placements can all look like success to an automated system if your setup rewards them.

The answer isn’t to switch off every automated feature. It is to give Google a business outcome it can learn from, define where it may explore, and detect drift before wasted spend becomes a new baseline. Here is the control framework we would use.

Define the outcome before you automate the campaign

Google Ads automation solves the objective represented by your data. It cannot independently decide that a qualified opportunity matters more than a form submission, that an approved applicant matters more than a completed application, or that a rental booking matters more than research about rental insurance.

That makes conversion configuration a control, not merely a reporting choice. Your primary conversion tells the system what kind of outcome to reproduce. If that event includes low-quality or duplicated outcomes, automation can become very efficient at finding more of them.

Start by finishing one sentence in business language: This campaign should produce more of what? The answer should be specific enough that sales, finance, operations, and marketing would classify the outcome the same way.
1. Name the business outcome. Use a booking, qualified opportunity, approved applicant, completed sale, cross-sell opportunity, or another result the business genuinely values. Do not begin with the easiest event Google can observe.
2. Map the observable steps. List the ad click, page visit, form submission, qualification, opportunity, approval, purchase, and any other stages that connect the ad to the outcome.
3. Choose the bidding signal intentionally. Keep diagnostic events available for analysis, but make an event primary only when you actually want bidding to seek more of it.
4. Remove false success. Look for spam, test records, duplicate submissions, existing customers counted as new acquisition, and leads that fall outside the serviceable market.
5. Return downstream outcomes. Where the valuable event occurs outside the website, connect advertising data with CRM or operational data and return stronger signals through offline conversion imports, enhanced conversions, or appropriate first-party data.
More conversion volume is not automatically better training data. If every lead is sent back as equally valuable, Google has no reason to distinguish a sales-ready prospect from a record that will never progress. A smaller set of outcomes that matches the business objective can be more useful than a larger but mixed pool.

Audience inputs require the same discipline. A net-new acquisition campaign should not learn that repeat customers are ideal new prospects. A cross-sell campaign, by contrast, may intentionally use existing customers and their stage in the customer journey. In one B2B application, customer audiences aligned to complementary solutions helped create new CRM opportunities and cross-sell pipeline. The useful principle is not simply to upload more audience data; it is to supply the audience that fits the stated outcome.

Put guardrails around reach, messaging, and destinations

Once the outcome is sound, automation still needs boundaries. Google can recognize statistical relationships without understanding every commercial distinction behind them. Closely related searches may imply different intent, a relevant-looking page may be a poor conversion destination, and inexpensive inventory may produce leads the business cannot use.

AI Max makes this especially important. The website is only one targeting input alongside existing keywords, ad copy, budget, and real-time intent signals. It can also use broad-match and keywordless technology to reach searches beyond narrower keyword matching. That creates discovery opportunities, but it also enlarges the area you must govern.

Separate definite mismatches from ambiguous search intent

Do not manage expanded search traffic as one undifferentiated pile. Use two decision lanes:
- Definite mismatch: The query clearly represents a product, location, audience, or intent the campaign cannot serve. Exclude it under a documented rule.
- Ambiguous intent: The wording could represent a valuable customer or an adjacent research task. Send it to human review with its volume, cost, conversions, and downstream quality.
The distinction matters. A car-rental campaign, for example, repeatedly matched searches about car-rental insurance. The language was adjacent to the advertiser’s service, but the searcher was researching insurance rather than trying to book a vehicle. Business rules applied to recent search terms can automatically handle clear mismatches while surfacing uncertain terms for a person to decide.

A practical search-term script or rules workflow should therefore do three jobs: exclude queries that unmistakably violate a business rule, queue borderline cases, and flag recurring high-volume modifiers that fail to convert so you can investigate them early. No conversions alone is not proof that a term is irrelevant, especially when volume is limited. Require an intent-based reason before an automated exclusion blocks future traffic.

Control what AI says and where the click lands

AI Max text customization can build headlines and descriptions from website copy, existing assets, and query context. Review the output as advertising copy, not as a harmless platform suggestion. Check product claims, offer terms, geography, tone, brand representation, and whether the message accurately describes the landing page.

Text Guidelines, also described as guardrails, let you provide up to 25 search-term exclusions and 40 messaging restrictions for automatically created copy. Use those limited fields for restrictions that are precise and consequential. A vague instruction such as maintain our tone is hard to evaluate; a rule that forbids an unsupported product claim is concrete enough to audit.

After enabling AI Max or upgrading a campaign, go to Ads > Assets > Performance and include the Added by column. That view identifies assets added by Google AI so you can inspect them separately from advertiser-supplied assets. Review more frequently immediately after a material change, then make the check part of recurring account governance.

Final URL expansion needs its own review. Unlike a Dynamic Search Ads target that confines traffic to a defined part of the site, AI Max can route a searcher to another relevant page across the domain, subject to URL exclusions. A page can be topically relevant yet commercially wrong because it serves another region, describes an unavailable offering, targets existing customers, or lacks the path needed to complete the campaign’s intended action.
1. List the page groups that are valid destinations for the campaign’s objective.
2. Exclude sections that cannot serve that objective, rather than waiting for each individual URL to spend.
3. Inspect the actual landing pages receiving traffic, not only the final URL entered in the ad setup.
4. Confirm that the query, generated message, landing page, and conversion action describe one coherent journey.
5. Check regional routing explicitly when campaigns or websites have location-specific pages.
AI Max also provides brand inclusion and exclusion lists at the ad-group level and geographic intent controls. Treat them as explicit statements of campaign scope. They should reflect whether the campaign is meant to capture branded demand, exclude another brand relationship, or serve people expressing intent for a particular market.

Evaluate placement patterns in aggregate

Placement waste does not always arrive as one obvious offender. A large collection of individually inexpensive placements can create a costly pattern that remains hidden when each URL is reviewed alone.

In one Demand Gen campaign, thousands of low-cost placements collectively generated expensive, weak quote requests. URL-based business rules excluded clearly unsuitable placements and escalated borderline ones. Within a month, the close rate for quote leads rose from below 1% to about 8%. That is one account outcome, not a universal benchmark, but it shows why downstream quality and aggregate placement patterns matter more than cheap inventory by itself.

Build placement rules around suitability and business outcome. Automatically exclude only what clearly falls outside those rules. Review the uncertain group, preserve a change log, and keep a way to reverse exclusions if later evidence changes the decision.

Protect the feedback loop from silent drift

A good launch configuration can still decay. Tracking may stop firing, a conversion setting may change, CRM feedback may disappear, a campaign may point to the wrong regional page, or the customer mix may shift. Because these failures often accumulate gradually, the bidding system can keep learning while the meaning of its training data deteriorates.

Your monitoring should cover the input pipeline as well as campaign performance. Automated quality assurance can validate tracking configurations, verify regional URLs, and flag significant daily, weekly, or monthly performance changes. Each check answers a different question:
- Tracking integrity: Is the event still recorded and classified as intended?
- Data delivery: Are offline and CRM outcomes still reaching the advertising system?
- Destination integrity: Do campaigns still send each market to the correct page?
- Traffic composition: Have search terms, placements, audiences, or landing pages shifted?
- Business quality: Are the conversions becoming qualified opportunities, approvals, sales, bookings, or other intended outcomes?
- Performance movement: Has a daily, weekly, or monthly measure changed enough to require investigation?
An anomaly is an alert, not an explanation. When a metric moves sharply, investigate in a fixed order so you do not train the system around bad data:
1. Verify that tracking, conversion configuration, and downstream data transfers are intact.
2. Check whether the mix of queries, placements, audiences, generated assets, or landing pages changed.
3. Compare platform conversions with the business outcomes recorded elsewhere.
4. Correct broken inputs or scope violations before judging the bidding strategy.
5. Evaluate budget or bidding changes only after you trust the feedback loop again.
This sequence prevents a common mistake: reacting to a measurement failure as if it were a media-performance problem. Changing bids while CRM imports are missing does not repair the signal. It merely asks automation to make a new decision from incomplete evidence.

Long sales cycles make the feedback gap more visible. If Google can observe the lead today but the business values a qualified pipeline event much later, document the handoff between the ad platform and the CRM. Assign ownership for the import, its validation, and its failure alerts. A sophisticated bidding setup cannot compensate for a feedback process that nobody owns.

Move from DSA to AI Max on your own schedule

If you use standalone Dynamic Search Ads campaigns, the transition to AI Max is a change in operating model, not a renamed campaign. Standalone DSA begins with the website and uses defined dynamic ad targets. AI Max sits within the existing Search campaign structure, combines more targeting signals, creates more ad text, and can expand landing-page selection across the domain.

The current transition window gives you time to manage that change. Advertisers can continue creating DSA campaigns through January 2027, with automatic migrations beginning in February 2027. Waiting for automatic migration gives you less control over when new targeting, creative, and routing behavior enters the account.

Before selecting the manual Upgrade campaign option in the Dynamic Search Ads settings, preserve the information DSA already gave you:
1. Inventory the current structure. Record dynamic ad targets, negative keywords, URL exclusions, conversion configuration, budgets, and the pages allowed to receive traffic.
2. Extract useful search-term history. Identify the themes that generated meaningful outcomes and the terms that revealed adjacent or unsuitable intent. DSA search-term performance can also show where explicit keyword coverage deserves attention.
3. Write the new boundaries first. Prepare URL exclusions, brand controls, geographic intent settings, negative keywords, and text restrictions before exposing more traffic to expanded matching.
4. Capture a business-quality baseline. Keep the downstream rates and outcomes you will need to judge the change, not just clicks and platform conversions.
5. Upgrade deliberately. Start where you can observe the new behavior closely. Avoid combining the migration with unrelated measurement changes when possible, because simultaneous changes make the result harder to diagnose.
6. Inspect from the first post-upgrade traffic. Review search terms, AI-created assets, actual landing pages, and downstream conversion quality as separate control surfaces.
The first question after migration should not be whether AI Max produced more traffic. Ask whether it found more of the commercial intent you wanted, represented the offer correctly, chose viable destinations, and produced outcomes the business accepts. Volume without those checks can conceal a widening gap between platform performance and business performance.

Key takeaways
- Make the primary conversion represent the result you want automation to reproduce, not merely the easiest event to count.
- Return qualified downstream outcomes through connected CRM, analytics, and first-party data processes where the valuable event happens after the lead.
- Automatically block only clear search or placement mismatches; send ambiguous cases to human review.
- Review AI-created assets through Ads > Assets > Performance with the Added by column visible.
- Control Final URL expansion with page-group rules, exclusions, and checks of the actual destinations receiving traffic.
- Verify measurement and data delivery before responding to a performance anomaly with bidding or budget changes.
- Plan the DSA-to-AI Max transition before automatic migrations begin in February 2027.
This week, choose one automated campaign and trace a real business outcome backward to its query, ad, landing page, conversion action, and CRM status. Wherever that chain becomes invisible or changes meaning, add a measurement check, a boundary, or a named owner. That is where control will produce more value than another round of bid adjustments.

References
- Search Engine Land — Google Ads automation makes governance a competitive advantage
- Search Engine Land — How to prepare for Google’s DSA sunset and move to AI Max
July 23, 2026

Google Ads Automation Updates: A Practical Measurement Plan

Your biggest Google Ads risk is no longer a lack of automation. It is allowing the platform to make a wider range of decisions while your reporting still collapses those decisions into one campaign total.

If you run Standard Shopping campaigns or maintain a Google Ads integration, you now have two different changes to prepare for. AI Max functionality in Standard Shopping remains an unconfirmed test, while Google Ads API v25 is a released engineering change. In both cases, the practical goal is the same: define what Google may decide, record what it actually does, and connect each decision to a business outcome.

Automation and measurement are changing at the same time

Standard Shopping has traditionally appealed to advertisers who want more direct control than Performance Max provides. That distinction could become less clear. A reported AI Max test in Standard Shopping includes conversational query matching, feed-based ad copy, Final URL Expansion, and the ability to choose between a Shopping ad and a text ad based on the query.

The reported implementation would preserve existing bidding and targeting settings while adding campaign-level controls for asset optimization, brand exclusions, and Final URL Expansion. Advertisers could reportedly disable URL expansion when they want traffic to remain tied to Shopping ads. That combination matters: it suggests Google may expand the decisions made inside Standard Shopping without forcing advertisers to migrate the campaign into Performance Max.

Do not treat those capabilities as settled product behavior. Google has not formally announced the Standard Shopping test, so availability, controls, and final functionality could change. Treat it as a scenario for which you can prepare, not a feature you should promise to a client or build into a forecast.

Google Ads API v25 is different. It adds new YouTube reporting, Shorts engagement metrics, creator insights, a loyalty retention goal, and a revised implementation of new customer acquisition goals. It also requires developers to update client libraries and code to use the new functionality, while the removal of legacy resources can affect compatibility. The API v25 changes therefore belong in an engineering release plan, not on a product-watch list.

Key takeaways

Prepare for AI Max in Standard Shopping, but preserve the distinction between a reported test and a released feature.
Treat query matching, message generation, destination selection, and ad-format selection as separate automation permissions.
Record feature settings alongside campaign results so you can explain why performance changed.
Use API v25 to deepen YouTube and lifecycle reporting rather than adding new metrics to an undifferentiated dashboard.
Upgrade integrations through staging and regression checks because legacy lifecycle resources have changed.

Write an automation contract before enabling AI Max

An automation contract is a short operating document that states which decisions the platform may make and which boundaries it must respect. You do not need legal language or a lengthy policy. You need an explicit answer for each decision layer before a campaign starts spending under new rules.

Decision layer	Potential automated behavior	What you should decide first
Query	Match Shopping inventory to conversational and long-tail searches	Which brand, intent, and relevance boundaries must be protected
Message	Create ad language from Merchant Center attributes	Which attributes are accurate, current, and safe to present as claims
Destination	Send a visitor to a page selected through Final URL Expansion	Which page types are eligible and whether expanded routing should be enabled
Format	Choose between a Shopping ad and a text ad	How each format will be identified and evaluated in reporting

Start with the feed. Materials, fit, durability, and other Merchant Center attributes may become inputs to generated ad copy. A feed value that was previously visible only in a product listing can therefore become a prominent advertising claim. Check those attributes for accuracy, consistency, and substantiation. Do not use automation to amplify language that merchandising or legal reviewers would reject on the landing page.

Then decide how much routing authority the campaign should receive. Final URL Expansion is not merely a media setting; it is permission to select a different part of your site as the destination. A technically valid page can still be commercially wrong if it shows the wrong product set, weak availability, conflicting prices, or a conversion path that was not built for paid traffic.

Verify that eligible pages show the same material product facts used in the feed.
Confirm that price, availability, promotional language, and conversion tracking remain correct on every likely destination type.
Use brand exclusions where matching or generated messaging could cross a brand boundary.
Keep Final URL Expansion disabled until broader destinations have passed the same review as product pages.
Document who may approve a wider set of destinations after the initial validation.

The downside of skipping this work is direct: budget can move to a page or message that does not represent the offer you intended to advertise. If you cannot verify destination eligibility, keep traffic constrained to the known Shopping path until you can.

Make every automated decision observable

Transparent routing gates direct product-shaped objects along illuminated paths while sensors record each decision point.

Aggregate campaign performance cannot tell you whether a change came from broader query matching, generated messaging, a different destination, a different ad format, or the bid strategy already in place. You need a record that separates inputs, permissions, delivery, and outcomes.

Measurement layer	What to record	Question it answers
Inputs	Feed revisions, attribute changes, landing-page changes, and tracking changes	Did the campaign receive different information?
Permissions	Asset optimization state, brand exclusions, Final URL Expansion state, bidding settings, and targeting settings	What was Google allowed to change or select?
Delivery	Available search-query detail, served ad format, selected destination, product coverage, and traffic mix	What did the system actually do?
Outcomes	Spend, conversions, conversion value, engagement, acquisition outcomes, and retention outcomes relevant to the campaign	Did the behavior produce the intended business result?

Capture the current state before changing a setting. Screenshots can help during a preliminary rollout, but a structured change record is more useful because it can be joined to reporting later. At minimum, store the account, campaign, setting name, previous state, new state, approval owner, deployment point, expected effect, and rollback condition.

Next, write a falsifiable hypothesis. Broader conversational matching, for example, is not a complete hypothesis. A usable version identifies the eligible product group, the type of demand you expect to reach, the outcome you expect that traffic to produce, and the signal that would show the expansion is commercially irrelevant.

Snapshot campaign settings, feed state, destination rules, and baseline reporting dimensions.
Choose the specific automation permission being evaluated.
Predefine the primary outcome and the business guardrails.
Change one permission at a time where the platform and campaign structure allow it.
Inspect query, format, and destination behavior before relying on the aggregate result.
Keep, constrain, or reverse the change based on the predefined outcome and guardrails.

Do not copy a universal efficiency threshold from another account. A defensible guardrail comes from your margins, sales cycle, conversion quality, inventory constraints, and tolerance for exploratory demand. The important discipline is to set it before seeing the result. A threshold invented after the test becomes a justification, not a decision rule.

Use API v25 to separate YouTube signals from business outcomes

Anonymous video engagement signals pass through separate data channels toward shopping, repeat-customer, and new-customer outcome scenes.

Segment non-skippable ads by sub-format

API v25 introduces the ad_sub_format_type segment for non-skippable in-stream YouTube ads. It can distinguish standard duration, ads up to 30 seconds, and ads up to 60 seconds. That dimension prevents materially different creative experiences from disappearing inside one format total.

Add the segment where it answers a real creative or delivery question. Compare performance within a consistent campaign objective and audience context. If duration, targeting, bidding, and creative concept all change at once, the new field gives you a cleaner label but not a causal explanation.

Keep Shorts engagement diagnostic

Comments, likes, and shares are now available for Shorts ad reporting. These metrics can show how viewers respond socially to a creative, but they are not substitutes for conversions, revenue, qualified acquisition, or retention. Use them to diagnose resonance and participation, then read them beside the outcome the campaign was funded to produce.

A practical Shorts view should keep delivery, engagement, and business results in separate groups. That structure stops a highly interactive ad from being declared successful when it misses the commercial objective, while still preserving the engagement data that can guide creative development.

Treat creator insights as conditional data

API v25 can expose creator-channel information including average views, engagement rates, likes, comments, and audience attributes. Non-public details depend on creators opting to share them. Build reports that make missing or unavailable creator data explicit rather than treating absent values as zero performance.

Creator metrics are best used to improve selection and contextual interpretation. They do not remove the need to measure the actual ad, audience, offer, and conversion path used in your campaign.

Separate retention optimization from customer acquisition

API v25 adds a loyalty retention goal with campaign- and account-level settings. It also supports bid adjustments and loyalty-member benefits in Product Listing Ads. This gives advertisers a way to optimize for keeping loyalty members rather than treating every valuable action as another acquisition event.

That distinction should survive all the way into your dashboard. Acquisition asks whether you gained the intended new customer. Retention asks whether an existing loyalty member stayed active or received an experience designed for that relationship. Combining them can make campaign efficiency look healthy while concealing which lifecycle objective produced the value.

New customer acquisition goals have also moved to Google’s unified goals framework, replacing legacy lifecycle goal resources. Before upgrading, map each existing resource, field, report, and internal label to its intended counterpart. Do not let an engineering migration silently redefine the business meaning of a goal.

Give acquisition and retention goals distinct names in campaign documentation and reporting.
Identify the first-party data and membership logic on which each goal depends.
Assign an owner to validate member benefits shown in Product Listing Ads.
Keep bid adjustments visible in the same change record as the lifecycle goal.
Check that executive dashboards do not merge retained members with newly acquired customers.

This is where media, analytics, customer relationship management, and engineering teams need one shared definition. The API can transport the goal, but it cannot resolve a disagreement about who counts as new, retained, or eligible for a member benefit.

Put API and campaign changes into production safely

Begin the API v25 migration with an inventory of affected client libraries, queries, resources, report schemas, calculated fields, dashboards, and downstream exports. Pay particular attention to code that depends on legacy lifecycle goal resources. New reporting fields are useful only after the existing integration remains trustworthy.

Map current dependencies and identify removed or replaced lifecycle resources.
Upgrade the supported client library and update code in a non-production environment.
Add the YouTube sub-format, Shorts engagement, creator, and loyalty fields only where a defined use case exists.
Run unchanged reports through regression checks and compare row structure, totals, null handling, and field meaning.
Test reports with and without the new optional dimensions so downstream users understand how segmentation changes the output.
Deploy with monitoring and a documented recovery path for failed jobs or incompatible consumers.

Use the same release discipline for campaign automation. A campaign ticket should state the setting before and after the change, eligible products and brands, permitted destination types, expected query behavior, primary outcome, guardrail, data location, approval owner, and rollback condition. This turns an AI feature from an opaque switch into a governed campaign change.

Your first move should be simple: capture the current state of the campaigns and integrations that would be affected. If the Standard Shopping test never reaches your account in its reported form, that record still improves your control over existing automation. If it does arrive, you will be ready to test it without sacrificing the ability to explain where an ad appeared, what it said, where it sent the visitor, and whether that decision helped the business.

References

July 23, 2026

AI Campaign Automation Shifts Control From Tasks to Rules
AI-powered campaign automation is moving beyond isolated recommendations and into campaign execution. The two systems covered here illustrate that shift at different layers: Shopify’s Campaign Autopilot is designed to coordinate marketing across channels for merchants, while Google’s AI Max is reshaping how advertisers manage and evaluate automated Search campaigns.

Together, the reports suggest a new operating model for marketers. The human role becomes less about configuring every campaign element and more about defining objectives, setting boundaries, reviewing evidence and intervening when automation produces an undesirable result.

Key takeaways
- Shopify’s reported approach automates campaign creation, budget distribution and ongoing optimization across selected marketing channels.
- Google’s reported direction applies AI-led intent matching within Search and pairs it with more detailed search-term and landing-page reporting.
- Automation does not eliminate advertiser control: approvals, budgets, exclusions, URLs and performance reviews remain important safeguards.
- The practical skill shift is from manual campaign assembly to objective setting, governance and cross-channel performance interpretation.
Two automation models are emerging

Campaign Autopilot represents an orchestration model. According to the Shopify-focused source, a merchant selects a monthly budget, participating channels and operating guidelines. The system can then create and launch campaigns, allocate funds across channels, adjust spending in response to performance, recommend automated email initiatives and continue refining the campaign.

The source says the early-access feature works from Shopify’s admin and supports Meta, Shop Campaigns and email. It also reports that support is planned for ChatGPT Ads, Microsoft Advertising and Snapchat. Those prospective integrations should be treated as a roadmap described by the source, not as currently available functionality.

AI Max reflects a different model: automation within a particular advertising environment. The Google-focused source reports that updated guidance emphasizes intent rather than strict keyword matching, with conversion goals taking priority over surface-level keyword relevance. It also says Dynamic Search Ads campaigns are scheduled to begin upgrading automatically to AI Max in February 2027.

The distinction matters. Shopify is described as choosing and coordinating actions across merchant channels, whereas Google is described as expanding how a Search campaign discovers and matches demand. One system aims to simplify the marketing mix; the other changes the mechanics and management of paid search.

Control is becoming a governance layer

Neither report supports a fully hands-off interpretation of campaign automation. The Shopify source says merchants can approve or modify campaigns, change budgets and stop actions. It also notes that Campaign Autopilot operates separately from existing Meta or Shop advertising campaigns, so previously planned campaigns are not automatically displaced.

Google’s guidance places control in reporting and exclusions. The source describes reporting views for AI Max search terms and landing pages, as well as comparable views for Dynamic Search Ads. Advertisers can respond to weak traffic with negative keywords or URL exclusions. At the same time, the guidance reportedly cautions against excessive filtering because narrow restrictions can prevent the system from using broader intent signals.

This creates a governance problem rather than a simple on-or-off decision. Useful controls need to prevent unacceptable placements, destinations or spending without constraining the automation so tightly that it cannot explore. A practical governance framework should define:
- Objectives: the conversion outcomes the system is expected to pursue.
- Financial limits: the approved budget and the conditions for changing it.
- Channel boundaries: where campaigns may run and which existing activity must remain separate.
- Exclusions: unsuitable search terms, landing pages, URLs or other traffic that should not be targeted.
- Intervention triggers: the performance or brand-safety conditions that require a human review, adjustment or pause.
Measurement must explain what the automation did

As campaign systems make more decisions, aggregate results alone become less informative. A marketer also needs to understand which demand was captured, where users landed, how funds moved and which conversion goals guided the optimization.

Google’s updated documentation, as summarized by the source, addresses part of that need by connecting search terms with landing pages and clarifying that search-term reporting reflects the destinations users reach after clicking. For travel campaigns, the source says advertisers can consolidate performance information and segment it by formats including Travel Promotion Ads, Booking Links and Travel Feed-based ads.

The Shopify source describes another measurement advantage: Campaign Autopilot reportedly draws on performance insights from millions of Shopify stores to inform optimization and budget allocation. That claim indicates the scale of the data informing the system, but the supplied report does not detail the methodology, the degree of transfer between merchants or how those insights affect any individual campaign. Advertisers should therefore judge recommendations by their own outcomes rather than treating scale as proof of effectiveness.

The Google source recommends reviewing search-term and item-group performance every one to two weeks. Shopify’s source, meanwhile, describes ongoing evaluation and gives merchants access to recommendations and results through its Sidekick assistant. Although the interfaces differ, both accounts preserve a recurring review function for the advertiser.

How teams can prepare for more autonomous campaigns

The immediate preparation is operational rather than purely technical. Teams need clear goals and clean decision rights before delegating campaign work to an automated system. Otherwise, faster execution can simply amplify unclear priorities.
1. Specify the business outcome. Define the conversion objective before selecting channels, budgets or targeting constraints.
2. Document the starting state. Record existing campaigns, exclusions and budget commitments so new automation can be evaluated without confusing it with pre-existing activity.
3. Set boundaries before launch. Establish approved channels, spending limits, destination rules and conditions requiring human approval.
4. Review decision-level evidence. Examine search terms, landing pages, channel allocation and conversion outcomes rather than relying only on a headline performance figure.
5. Adjust controls selectively. Use exclusions to address identifiable problems while avoiding restrictions so broad that they defeat intent-based optimization.
6. Plan for platform transitions. Advertisers using Dynamic Search Ads should account for the reported February 2027 start of automatic AI Max upgrades and use the available lead time to understand the newer reporting model.
The larger shift is not simply from manual work to automatic work. It is from managing campaign components to managing an adaptive system. As channel orchestration and intent-based advertising mature, the strongest teams will be those that can give automation enough room to learn while retaining clear accountability for budgets, customer journeys and business outcomes.

References
- CrushPress.AI — Empower Your Marketing with Shopify’s AI Campaign Autopilot
- CrushPress.AI — Google’s AI Max Update: Key Insights for Future Search Strategies
June 23, 2026

How AI Attribution Should Shape the DSA-to-AI Max Migration

Google’s planned transition from Dynamic Search Ads (DSA) to AI Max is more than a campaign-format change. It arrives as AI is also altering how buyers discover brands, how platforms select audiences and placements, and how much of the decision journey advertisers can observe.

The extended migration window gives advertisers an opportunity to build a measurement baseline before adopting more automation. The practical goal is not simply to determine whether AI Max records more conversions than DSA, but whether it produces additional qualified business outcomes without obscuring where demand originated.

Campaign migration and attribution are now the same problem

The two source articles address different developments, but their implications converge. The migration report says Google postponed automatic DSA migration from September 2026 to February 2027 and recommends experiments comparing existing campaigns with AI Max for Search. The attribution analysis warns that platform automation can improve reported performance while reducing the detail available for explaining why that performance changed.

That combination raises the standard for a successful migration. A campaign can appear more efficient because it reaches people who were already likely to convert, captures demand created elsewhere, or counts actions that do not become meaningful customer outcomes. Broader targeting may also introduce weak leads that influence later automated optimization.

The attribution article describes an increasingly fragmented journey in which a buyer might encounter a brand through social media, video, community discussions or an AI recommendation before completing a branded search. In such a journey, the campaign receiving conversion credit may have captured existing intent rather than created it. AI Max testing therefore needs to examine both reported attribution and the business contribution behind it.

The measurement risks that can distort an AI Max comparison

Overlapping customer-journey signals pass through transparent measurement layers, creating duplicated reflections and obscured attribution paths.

More attributed conversions may not mean more incremental demand

A platform comparison based only on conversions or return on ad spend can favor the campaign that is best at claiming observable demand. The attribution source highlights branded search as a common example: it often looks highly efficient because it reaches people who already know the advertiser, even when another channel or an AI-generated answer initiated their interest.

Advertisers should consequently separate demand capture from demand creation before interpreting a test. Search activity close to conversion can be evaluated for efficiency, while upper-funnel activity should also be assessed through path analysis, changes in branded interest and incrementality experiments. The source specifically points to GA4 path reports and Google’s Conversion Lift as useful approaches, while cautioning that no single report represents the complete customer journey.

Lead volume can conceal declining business quality

The attribution analysis also reports that generalized targeting can generate poor-quality traffic when conversion signals are weak. If every submitted form is treated as equally valuable, automated bidding may optimize toward inexpensive leads rather than opportunities or sales.

CRM outcomes provide the necessary counterweight. Qualified leads, opportunities and completed sales can reveal whether a lift in platform conversions represents genuine progress. Where technically and operationally feasible, importing deeper outcomes can also give automated campaigns signals that are closer to business value.

Conversion definitions and settings require equal attention. The attribution source recounts cases in which changed reporting settings inflated conversion totals. A migration benchmark is unreliable if the legacy and experimental campaigns count different actions, use inconsistent values or are affected by unnoticed setting changes.

The delayed timetable creates a structured testing window

According to the migration report, Google restored the ability to create DSA campaigns in June 2026, plans to stop new DSA creation in January 2027 and expects automatic migration of remaining campaigns to begin in February 2027. The reported schedule creates distinct phases for baselining, experimentation and final transition.

Reported period	DSA status	Measurement priority
June 2026	New DSA creation restored	Document existing campaign structure, settings and business outcomes
June 2026 through January 2027	Extended testing and voluntary migration period	Run comparisons with AI Max and investigate differences in traffic and lead quality
January 2027	New DSA creation ends	Finalize the migration sequence and preserve benchmark data
February 2027	Automatic migration begins for remaining campaigns	Monitor post-migration changes against the established baseline

A useful comparison should keep conversion definitions, CRM mappings and evaluation periods consistent. It should record more than aggregate performance: branded versus non-branded behavior, search themes where available, lead disposition, sales outcomes and any material changes in settings all help explain the result. Side-by-side campaign data is evidence about performance under the test conditions, while incrementality testing addresses the separate question of what would have happened without the advertising.

A measurement-first migration plan

Two parallel campaign-testing lanes receive matching audience signals and pass through controlled checkpoints toward equivalent outcome markers.

Audit the DSA baseline. Record campaign structure, conversion actions, values, targeting controls, exclusions and recent CRM outcomes before changing the account.
Define success in business terms. Choose the downstream result that matters, such as a qualified lead, opportunity or sale, rather than relying only on the easiest platform event to collect.
Separate capture from creation. Segment branded activity and other high-intent demand where possible so that AI Max is not credited with creating interest it merely intercepted.
Run an AI Max experiment. Use the voluntary testing period reported by the migration source to compare performance while keeping measurement definitions aligned.
Inspect quality and paths. Review CRM progression, attribution paths, AI-referred sessions and branded search behavior alongside platform metrics. These indicators do not prove causation individually, but they can identify results that need further investigation.
Add an incrementality check. Where practical, use a lift experiment to test whether advertising caused additional outcomes rather than assuming every attributed conversion was produced by the campaign.
Migrate in stages and retain human review. Move campaigns only after documenting the evidence, then monitor placements, settings, lead quality and downstream results as automation learns.

This sequence also protects against a common analytical mistake: changing the campaign format, conversion setup and success metric simultaneously. When several inputs change at once, even a strong performance movement becomes difficult to interpret.

Key takeaways

The reported DSA delay provides time to establish benchmarks and test AI Max before automatic migration begins in February 2027.
Platform-attributed conversions should be evaluated separately from incremental demand, especially when branded search captures interest created elsewhere.
CRM outcomes are essential for detecting whether broader automated targeting is producing qualified opportunities or merely more leads.
Comparable conversion settings, documented account changes and regular human checks make migration results easier to trust.
The strongest decision combines platform reporting, customer-journey evidence and incrementality testing rather than depending on one ROAS figure.

Advertisers that use the extension to improve their measurement system will enter the automated transition with more than a replacement campaign. They will have a defensible way to decide when AI Max is creating business value, when it is capturing existing demand and when its optimization signals need correction.

References

June 12, 2026

Tag: AI Max

The click now sits inside a longer AI-shaped journey

AI Max turns campaign inputs into governance decisions

Creative must create intent, not decorate the campaign

Use a brief that can survive automation

Test concepts before you test cosmetic variations

LLM referrals need proof before pressure

Build the page for verification

Measure LLM conversion as its own behavior

Key takeaways: run paid media, GEO, and CRO as one loop

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

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

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

References

Give AI creative a narrow job before expanding it

Turn brand policy into enforceable messaging restrictions

Review every asset, then measure the whole account

Inspect generated copy before it earns material delivery

Separate campaign performance from incremental growth

Make AI disclosure a workflow, not a last-minute badge

Key takeaways

References

The opportunity has shifted from keywords to interpretable intent

Give Google a product record it can match to real needs

Translate conversational intent into product evidence

Apply an eligibility gate before buying more reach

Create a recovery lane for products the algorithm stopped testing

Measure discovery separately from harvest performance

Key takeaways

References

Define the outcome before you automate the campaign

Put guardrails around reach, messaging, and destinations

Separate definite mismatches from ambiguous search intent

Control what AI says and where the click lands

Evaluate placement patterns in aggregate

Protect the feedback loop from silent drift

Move from DSA to AI Max on your own schedule

Key takeaways

References

Automation and measurement are changing at the same time

Key takeaways

Write an automation contract before enabling AI Max

Make every automated decision observable

Use API v25 to separate YouTube signals from business outcomes

Segment non-skippable ads by sub-format

Keep Shorts engagement diagnostic

Treat creator insights as conditional data

Separate retention optimization from customer acquisition

Put API and campaign changes into production safely

References

Key takeaways

Two automation models are emerging

Control is becoming a governance layer

Measurement must explain what the automation did

How teams can prepare for more autonomous campaigns

References

Campaign migration and attribution are now the same problem

The measurement risks that can distort an AI Max comparison

More attributed conversions may not mean more incremental demand

Lead volume can conceal declining business quality