Tag: Campaign Automation

AI Ad Campaign Controls: Automate Without Losing Control

When you switch an AI ad campaign from traffic to conversions, you are not handing the platform a complete strategy. You are giving it a score to maximize. If the conversion event, eligible audience, landing page, or budget rule is wrong, automation can repeat that mistake at scale.

The safest operating principle is simple: you keep control of business constraints, while the system optimizes inside them. That means deciding what counts as success, where ads may appear, which destinations are acceptable, how spend should behave, and which changes require human review before you enable more automation.

Key takeaways

Optimize for a conversion only after you have verified that the event fires correctly, represents real business value, and can be reconciled with your own records.
Treat an average daily budget as a pacing instruction, not a promise that every calendar day will spend the same amount.
Set geographic, brand, URL, product, and audience exclusions before launch. They define where the algorithm is allowed to search.
Keep generated assets, URL expansion, customer matching, and audience estimation under separate review because each creates a different failure mode.
Use bulk tools to deploy reviewed change sets. Do not let bulk creation turn an isolated configuration error into an account-wide problem.

Give the system one objective and explicit boundaries

The useful dividing line is not manual versus automated. It is judgment versus calculation. You should retain the decisions that require knowledge of margins, service areas, customer quality, brand policy, and operational capacity. The platform can handle the repeated calculation of which eligible opportunity appears most likely to produce the event you selected.

Control layer	You decide	The system may optimize	What fails when the control is weak
Outcome	Which event represents valuable demand	Which eligible clicks appear more likely to produce that event	Low-value actions accumulate while reported performance looks healthy
Economics	The spend ceiling and acceptable business return	Bid and delivery allocation within available platform settings	More conversions arrive without acceptable margin or lead quality
Eligibility	Geographies, audiences, brands, products, URLs, and inventory that are allowed	Which eligible opportunities receive delivery	Spend reaches people or destinations the business cannot serve
Creative	Approved claims, assets, product data, and disclosure requirements	Asset generation, selection, or combination where enabled	Ads become inconsistent with the offer or brand policy
Measurement	Which data is valid enough to influence optimization	Learning from the conversion feedback supplied	Tracking defects become bidding instructions

This distinction matters in ChatGPT Ads. Its Conversions objective supports optimized cost-per-click campaigns that favor clicks considered more likely to convert while continuing to charge on a CPC basis. That is conversion-oriented selection, not a guarantee of a conversion, acquisition cost, revenue level, or profit. You still need an economic test outside the bidding label.

Write the objective as a complete sentence before configuring the campaign: “Acquire this type of conversion, from these eligible customers, for this business outcome, within these spending and brand constraints.” If you cannot fill in every part, the campaign is not ready for broader automation.

Do not combine several business goals into one vague instruction. A purchase, qualified sales opportunity, app install, account registration, and page view do not carry equal value. If the platform sees all of them as equivalent success events, it can rationally pursue the easiest one rather than the one that matters most to you.

Fix the measurement loop before optimizing conversions

A glowing signal travels from an abstract ad to a landing page, through a verification checkpoint, and back to an optimization engine in a closed loop.

Conversion automation is a feedback loop. An ad receives a click, a user takes an action, measurement sends that action back, and the campaign looks for more traffic resembling the credited result. A broken signal therefore does more than damage a report. It teaches the system the wrong lesson.

Name the primary event. Choose the action closest to business value that you can measure reliably. Keep softer actions as diagnostic metrics unless you intentionally want the campaign to optimize for them.
Test the complete path. Use the same device and journey a customer would use, then confirm that the event appears in the ad platform and in the system your business treats as authoritative.
Check the event payload. Confirm the event name, value, currency where applicable, destination, and deduplication behavior. A successfully received event can still carry the wrong meaning.
Separate platform credit from business acceptance. For lead generation, compare attributed leads with qualified leads. For commerce, compare purchases with valid orders rather than treating the platform count as the final ledger.
Record the change point. When you alter an event definition, matching method, consent flow, or data source, annotate the date in your campaign log. Otherwise, a measurement change can be misread as a performance change.

ChatGPT Ads has added Automatic Advanced Matching under Tools > Conversions > Data Source. It uses hashed customer data to improve website conversion attribution. Hashing changes how the data is represented; it does not answer whether your organization had permission to collect and use it. Review the applicable consent, privacy, and data-governance requirements before enabling the feature. If that review is incomplete, keep it disabled while you validate ordinary conversion tracking.

For mobile campaigns, AppsFlyer and Adjust integrations can measure installs and in-app events. Use that distinction. An install can show acquisition volume, but a later registration, subscription, purchase, or other valuable in-app event may reveal whether that volume produced useful customers. Do not silently substitute the easier event when the business goal depends on the later one.

Before increasing a budget, ask four questions: Did the intended event fire? Did it fire only once for one action? Did the value arrive correctly? Did your business system accept the outcome as real? A “no” to any one of them is a measurement problem to fix, not a bidding problem to automate around.

Use budgets and exclusions as operating controls

Monitor the budget on the window the platform uses

A daily budget can look like a hard calendar-day cap even when the platform treats it as an average. ChatGPT Ads is shifting to average daily budgets evaluated over a rolling seven-day period, allowing daily spend to move while staying within the broader budget limits. It also paces daily budgets through the day.

That changes how you should investigate apparent variance. Do not declare a pacing failure merely because one day is above or below the displayed average. Review the rolling seven-day spend, the campaign’s total constraints, conversion volume, and your own financial cap together. A single-day screenshot is no longer enough to describe budget behavior.

Write down whether the platform field is a fixed cap, an average, or a target. The label determines what a normal day can look like.
Maintain an internal maximum exposure for the reporting window. Your accounting limit should not depend on a team member remembering how a platform interprets “daily.”
Alert on cumulative spend and material configuration changes, not only on one day’s variance.
Check whether a performance swing coincides with a budget edit, conversion edit, or exclusion edit before changing bids.
Do not raise the budget simply because pacing is slow early in the day. The pacing system is already distributing delivery, and an impulsive edit changes the instruction it is following.

A budget is also not a forecast. It describes the amount the system may use under its rules, not the number of valuable outcomes you will receive. Keep the decision to increase spend tied to reconciled conversion quality and acceptable economics.

Apply exclusions from hardest constraint to weakest signal

Exclusions are not merely cleanup settings. They define the search space. Configure the most defensible constraints first:

Operational impossibility: exclude locations you cannot serve, destinations that cannot fulfill the offer, and products that must not be advertised.
Brand and destination policy: restrict brands, landing pages, and URL expansion paths that could create an off-message or irrelevant journey.
Commercial fit: exclude audiences only when reliable performance or eligibility evidence supports the decision.
Estimated attributes: treat modeled classifications as weaker evidence than an explicit location, product, or URL rule.

ChatGPT Ads now provides campaign-level geographic exclusions. Use them when a location is genuinely ineligible, not as a substitute for diagnosing a regional landing-page, pricing, or measurement problem.

Destination controls deserve the same attention as audience controls. Google Ads Editor 2.13 supports AI Max in Shopping with automated text generation, URL expansion controls, brand lists, and URL exclusions. If URL expansion is enabled, review where the system is allowed to send traffic. A relevant query paired with the wrong page is still a failed campaign decision.

Be more cautious with household-income exclusions in Performance Max. The setting has been observed in a European campaign with brackets from the top 10% through the lower 50%, plus an Unknown segment, but the available evidence does not establish a universal rollout. Check whether the control actually exists in your account before designing a process around it.

If it is available, do not interpret Unknown as an income tier. It means the system has not assigned the user to one of the listed estimates. Excluding it can remove people whose commercial fit is simply unclassified. Compare measured business outcomes by segment before excluding a modeled group, document the rationale, and keep a clear route to reverse the change if reach or customer quality deteriorates.

Scale reviewed changes, not unchecked assumptions

A human analyst inspects a campaign module at a gated review station before approved copies move into a larger distribution network.

Bulk management reduces repetitive work, but it also enlarges the blast radius of a bad field. ChatGPT Ads now supports asynchronous bulk creation and updates for campaigns, ad groups, and ads through its Ads API. Because the work is asynchronous, submitting a job and confirming that every requested change completed are separate steps.

Google Ads Editor 2.13 similarly brings more AI campaign controls into an offline bulk workflow, including AI Max for Shopping, Customer Retention Goals in Performance Max, channel performance reporting, and AI-generated asset attestation controls. The practical gain is not just speed. You can review related settings as one change set before posting them.

Capture the starting state. Export or otherwise record the campaigns and fields you are about to change so you can identify exactly what moved.
Give the change set one purpose. Keep a budget revision separate from a conversion-goal migration, URL expansion change, or audience exclusion. If performance moves, you need to know which instruction caused it.
Validate the dangerous fields. Check campaign status, objective, conversion source, budget interpretation, geography, negative targeting, brands, URLs, product scope, generated-asset settings, and any required attestations.
Review the diff. Look for blank values, inherited defaults, duplicated entities, unintended status changes, and changes outside the intended campaign list.
Start with a limited subset. Use a small, representative group of campaigns when the feature or configuration is new to your team. Confirm behavior before applying the same pattern more widely.
Verify completion. For an asynchronous job, inspect the final job result and failed items. Then spot-check the resulting settings in the campaign interface.
Keep a rollback record. Store the prior value, new value, reason, approver, affected entities, and reversal method in the same campaign log.

After deployment, verify controls in a fixed order: eligibility first, destination second, measurement third, spend fourth, and reported outcomes last. This catches the cause before you react to the symptom. An ad that cannot serve, points to an unintended URL, or reports the wrong event should not be evaluated as a bidding-performance problem.

Your next move is to create a one-page control sheet for one live AI campaign. Record its primary conversion, authoritative business record, budget meaning, eligible geographies, audience exclusions, URL rules, brand rules, generated-asset permissions, owner, and rollback method. Resolve every blank field before adding another automated feature. That small document gives the system room to optimize without giving up the decisions only your business can make.

References

July 24, 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

Google Demand Gen Adds Feeds for Non-Retail Advertisers
Google’s Demand Gen campaigns can now draw from business data feeds, giving advertisers outside traditional retail a way to build dynamic ads from structured inventory information. The change matters most to businesses whose available offers, properties, trips, or vehicles change too often for practical manual creative updates.

Search Engine Land reports that the feature does not require a Google Merchant Center feed. However, its initial reach has an important boundary: business data feeds currently work only on the Google Display Network portion of Demand Gen, rather than across all of the campaign type’s inventory.

What business data feeds change in Demand Gen

A business data feed is a structured collection of information that an advertising system can use to assemble or update ads dynamically. Instead of treating every creative variation as a separate manual task, an advertiser can supply organized records representing available inventory or services.

According to Search Engine Land, Demand Gen can use those records to display content based on audience interests and available inventory. That shifts part of creative maintenance from repeatedly editing individual ads to keeping the underlying business data accurate and current.

Why the update extends beyond ecommerce

Merchant Center is closely associated with retail product feeds. Requiring it can be an awkward fit for advertisers whose inventory is not a conventional catalog of products. The new feed option gives those businesses a route to dynamic advertising without forcing their data into a retail-oriented workflow.

The source identifies three example industries that could benefit:
- Travel businesses promoting available destinations or offers
- Real estate advertisers working with changing property inventory
- Automotive advertisers presenting available vehicles
These examples share a common operational challenge: availability changes, while the underlying ad format may remain consistent. A structured feed can help connect that changing information to reusable creative, reducing the need to revise assets one by one.

Organic visibility, paid media and artificial intelligence merge into one connected search ecosystem, where vivid data streams link a creative website with a powerful analytics dashboard.

Key takeaways for campaign teams
- Business data feeds can now be connected to Demand Gen campaigns.
- The capability supports dynamic content based on audience interests and available inventory.
- A Google Merchant Center feed is not required.
- Travel, real estate, and automotive are among the industries highlighted by the source.
- Support is currently limited to the Google Display Network within Demand Gen.
The main constraint affects campaign planning

The Display Network limitation means advertisers should not assume that feed-driven creative will automatically appear everywhere a Demand Gen campaign can run. Campaign design, expectations, and reporting should account for the difference between the supported placement environment and the campaign’s broader inventory.

That distinction also makes controlled evaluation important. Teams can assess whether feed-powered ads reduce production work and produce more relevant combinations, but results from the supported inventory should not be generalized to placements where the feature is unavailable.

What advertisers should prepare before using feeds

The reporting establishes the capability, but it does not provide performance results. Advertisers should therefore treat improved relevance as a potential benefit rather than a guaranteed outcome. Feed quality, inventory accuracy, creative suitability, targeting, and measurement still influence whether automation produces useful ads.

A practical readiness review should focus on whether business records are consistently structured, updated when availability changes, and suitable for customer-facing creative. Clear ownership of the feed is also essential: automating ad assembly can reduce manual asset work, but inaccurate source data can distribute mistakes just as efficiently.

The update gives non-retail advertisers a more natural path into dynamic Demand Gen creative. Its near-term value will depend on disciplined data maintenance and realistic planning around the current Display Network boundary.

Inspired by this post on Search Engine Land.
July 17, 2026
Performance Max Placement Controls Enter an Early Alpha
A limited Performance Max alpha could give selected advertisers a consequential new choice: whether a campaign includes Search Partners and the Google Display Network. The reported setting does not dismantle campaign automation, but it may let advertisers define two important boundaries around the inventory that automation can use.

The distinction matters for both expectations and testing. This is a reported network-level control, not evidence of comprehensive placement management, and its value will depend on whether advertisers can measure the effects of each configuration reliably.

Key takeaways
- CrushPress.AI reported that a Partners (Alpha) setting is appearing in some Performance Max campaigns.
- The reported interface provides separate inclusion choices for Search Partners and the Google Display Network.
- Because the setting is labelled Alpha and has limited availability, it should be treated as an experiment rather than an established campaign feature.
- The most useful evaluation is a controlled comparison based on business outcomes such as cost per acquisition or return on ad spend.
- The reported controls apply to networks; they should not be interpreted as proof of granular control over individual websites, apps, searches or placements.
The alpha changes the boundary of automation

According to CrushPress.AI’s report, advertisers with access can use checkboxes to include or exclude Search Partners and the Google Display Network. The publication said both networks had previously been included automatically in Performance Max without a corresponding exclusion option.

That makes the test notable without making Performance Max a manually managed campaign type. Google would still automate decisions within the inventory available to the campaign; the advertiser would gain a higher-level choice about whether two sources of inventory are available at all. In practical terms, the control changes the perimeter in which the system operates rather than replacing automated delivery.

The terminology also deserves care. Although network selection affects where ads may appear, the reported setting is broader than a conventional placement exclusion. It does not, based on the available report, establish controls for selecting particular sites, apps, pages or search contexts.

Why network choice could improve campaign diagnosis

When several inventory sources contribute to one automated campaign, an aggregate result can show whether the campaign succeeded without fully explaining which environments helped or hurt. An option to remove Search Partners or the Google Display Network creates a clearer diagnostic question: does the campaign produce stronger business results when either network is unavailable?

That question should be framed around the campaign’s actual objective. CrushPress.AI identified return on ad spend and cost per acquisition as relevant measures for evaluating the setting. Advertisers may also need to examine whether changes in those outcomes accompany changes in conversion volume, reach or delivery stability. A lower cost per acquisition is less useful if the configuration can no longer produce the required volume, while additional reach is not automatically valuable if it fails to support the campaign goal.

The setting may also help separate an inventory concern from a broader campaign problem. If excluding a network does not materially improve the chosen outcome, attention may be better directed toward inputs such as creative, offers, audience signals, conversion measurement or landing-page experience. If performance changes consistently, the result supplies a more focused basis for deciding which inventory belongs in the campaign.

A useful test requires more than toggling a checkbox

A credible comparison begins with a decision rule established before the configuration changes. The advertiser should specify the primary business metric, the acceptable trade-off between efficiency and volume, and the conditions that would justify retaining or reversing the exclusion. This reduces the risk of choosing whichever metric looks most favorable afterward.

The comparison should also avoid unnecessary simultaneous changes. Major adjustments to budgets, conversion definitions, creative assets or landing pages can make it difficult to attribute a result to network selection. Normal volatility and automated learning further argue against drawing a conclusion from a brief movement in performance.

Interpretation should account for interaction effects. Excluding inventory can change the opportunities available to the campaign, which may alter how automation distributes delivery elsewhere. The meaningful comparison is therefore the campaign’s total outcome under each configuration, not an assumption that removed activity would have transferred unchanged to another network.

What remains unresolved while access is limited

The available evidence is preliminary. CrushPress.AI described the control as an Alpha available to a limited group and reported that Google had not announced whether or when it would become more broadly available. The report attributed the discovery to PPC Growth Strategist Saquib Syed, who shared the setting on LinkedIn.

The report does not establish how eligibility is determined, whether the interface will remain unchanged, or whether Google will add related reporting and controls. Those omissions are especially important because a network toggle is most actionable when advertisers can clearly evaluate the inventory affected by it.

The next meaningful signal will be broader availability accompanied by documented behavior and sufficient reporting to support sound comparisons. Until then, advertisers with access can treat the alpha as a structured learning opportunity, while those without it should avoid planning around a control that has not been confirmed as a general release.

References
- CrushPress.AI — Google Tests New Performance Max Search and Display Controls
July 15, 2026
Google Ads API Ending Smart Campaign Creation: My Take

I see Google’s latest Google Ads API change as another clear move away from legacy automation and toward newer AI-driven campaign types, especially Performance Max.

Beginning August 3, 2026, Google says developers will no longer be able to create new Smart Campaigns through the Google Ads API. For me, the key detail is that this change is about new campaign creation only.

Existing Smart Campaigns are not being shut down. They can keep serving ads, and advertisers and developers will still be able to update and manage those campaigns through the API.

What changes is the ability to create brand-new Smart Campaigns through API workflows. If I depend on automated campaign setup, that is the part I would review now.

I care about this because it signals where Google wants advertisers to go next. Smart Campaigns may continue running, but the path for new API-based campaign creation is moving toward newer products such as Performance Max, Search campaigns, and Demand Gen campaigns.

Google is specifically pointing advertisers toward Performance Max as the primary alternative. Since Performance Max runs across Google’s advertising inventory and uses AI to automate more of the campaign process, it fits the broader direction Google has been taking for years.

I also see this as part of a wider consolidation around automated campaign formats. Google has increasingly emphasized systems that handle bidding, targeting, and creative optimization across channels, and limiting new Smart Campaign creation reinforces that shift.

For developers, the practical next step is to audit any application that creates Smart Campaigns before the August 3, 2026 deadline. The affected requests are campaign creation operations where advertising_channel_type is set to SMART and advertising_channel_sub_type is set to SMART_CAMPAIGN.

After August 3, attempts to create new Smart Campaigns through the API will fail. In version 24 of the Google Ads API, developers will receive a SmartCampaignError.CREATION_FAILED error.

In version 23 and earlier, the same type of request will return an OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED error.

My main takeaway is that advertisers, agencies, and software providers should not treat this as a last-minute technical cleanup. If campaign creation is built into an internal tool, onboarding flow, or platform integration, I would start mapping the replacement path now.

Google is not ending existing Smart Campaigns, but it is removing a key creation path for new ones. To me, that is a strong signal that future campaign planning should center on Performance Max and other AI-driven Google Ads campaign types.

Dig deeper: Changes to Support for Smart Campaigns in the Google Ads API

Inspired by this post on Search Engine Land.

July 3, 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

When Is a Brand Campaign Ready for Google Ads AI Max?

AI Max can extend a Search campaign beyond its existing keywords, but a high-performing brand campaign is not automatically a good place to activate it. Readiness depends on whether broader automation serves a defined growth objective without weakening the measurement and control that make branded search valuable.

The available reporting points to a practical decision rule: separate eligibility for Google’s AI-driven search surfaces from the business case for expanding brand traffic. Then assess signal quality, account structure, learning volume, and testing safeguards before changing the campaign.

AI surface eligibility and campaign readiness are different questions

According to the source article, AI Max uses keywords, landing pages, and site content as signals to reach searches beyond explicitly targeted phrases. It can therefore uncover demand that a tightly constrained brand campaign would not ordinarily enter. The article also notes that brand exclusions, URL exclusions, text guidelines, and location targeting provide boundaries for that expansion.

That expanded reach may be useful, but access to AI-driven placements is not by itself a reason to alter a successful brand campaign. The article reports that Google Ads liaison Ginny Marvin identified three routes to AI Overview eligibility: broad match with Smart Bidding, Performance Max, and AI Max for Search. It further reports that exact-match keywords are not eligible for AI Overviews.

This distinction matters because an account already using Performance Max may already have the desired surface coverage. Adding AI Max to brand Search in that situation could duplicate an eligibility benefit while introducing broader query matching into the account’s most predictable traffic source. The relevant question is not simply whether AI Max can obtain more reach, but whether that reach is incremental, measurable, and aligned with the campaign’s role.

The article cited Semrush data indicating that AI Overviews reached approximately 2.5 billion monthly users and that ads appeared in 25.6% of AI Overview results. Those reported figures help explain advertiser interest, but they do not establish that every brand campaign needs AI Max or that eligibility will produce profitable incremental demand.

The reported performance evidence does not settle the brand question

Google’s reported upside and the independent observations cited in the article point in different directions. More importantly, the independent findings were not specific to brand campaigns, so they should inform test design rather than be treated as a verdict on branded search.

Evidence reported by the source	Reported result	What it can and cannot show
Google’s AI Max claim	A potential 14% conversion increase, rising to 27% for campaigns using exact and phrase match	Provides a platform benchmark, but not an account-specific forecast or a brand-only result
Smarter Ecommerce test across 600 accounts	AI Max produced 35% lower ROAS than traditional match types	Shows that broader automation can underperform in some account mixes; the article says the test was not brand-focused
Xavier Mantica’s four-month examination	Reported cost per conversion was $100.37 for AI Max, $43.97 for phrase match, and $52.69 for exact match	Illustrates a cost gap in one examination, but does not establish a universal ordering of match strategies
Ezra Sackett’s analysis of 30,000 search terms	According to the article, 99% of AI Max impressions produced no conversions	Raises a query-quality concern, but does not isolate the effect on defensive brand campaigns

Taken together, these reports support caution rather than a blanket rejection. AI Max may create value where an account has trustworthy optimization signals and room to expand. The evidence presented does not, however, demonstrate that a stable exact-match brand campaign is the best testing ground. A campaign already capturing known branded demand efficiently has a different job from a generic campaign designed to discover new demand.

Readiness starts with signals, structure, and an unmet objective

AI Max learns from the objectives and data supplied to it. If a campaign optimizes toward low-value actions, incomplete lead records, or conversions dominated by existing brand demand, broader automation can reinforce those biases. Strong historical performance does not compensate for a weak definition of success.

Readiness dimension	Evidence of readiness	Risk when it is weak
Conversion integrity	Macro and micro actions are clearly separated, primary goals reflect business value, and tracking is reliable	AI Max may optimize toward easy but commercially weak actions
Offline feedback	Qualified leads, completed sales, or other downstream outcomes return to the advertising platform consistently	High lead volume can be mistaken for high lead quality
Learning volume	The campaign or account supplies enough relevant conversion activity and variation for automation to distinguish useful patterns	Results may be unstable or overly influenced by a narrow set of branded conversions
Account architecture	Searches such as brand plus pricing, reviews, or other modifiers have deliberate treatment where their intent warrants it	AI Max can conceal structural gaps instead of resolving them
Generic growth	Budget constraints, landing-page mismatches, outdated queries, and campaign structure have already been examined outside brand	Attention may shift to squeezing more from efficient branded demand while larger growth barriers remain untouched
Strategic purpose	The team can name the incremental audience, query class, or coverage gap the test is meant to address	Activation becomes a response to a platform recommendation rather than a business objective

This framework also prevents a common measurement error: interpreting additional conversions as incremental conversions. Brand campaigns often capture people who already know the advertiser. Any evaluation therefore needs to distinguish newly reached, valuable demand from traffic that would have converted through existing brand coverage or another campaign.

Key takeaways

AI Max eligibility for AI-driven search surfaces does not prove that a brand campaign is operationally ready for broader automation.
Performance Max may already provide relevant AI surface eligibility, so overlap should be checked before AI Max is added to brand Search.
The independent results cited by the source are mixed and not brand-specific; they justify controlled experimentation, not universal conclusions.
Reliable conversion tracking, downstream quality feedback, sufficient learning data, and intentional campaign architecture are prerequisites.
A test needs an incremental-growth hypothesis and explicit safeguards, especially when the existing brand campaign is efficient and predictable.

A controlled experiment should protect the brand baseline

If the readiness conditions are satisfied, AI Max is better treated as a hypothesis to test than as a routine account upgrade. The hypothesis should state what additional value is expected, such as reaching a defined class of relevant searches that existing coverage misses. Success criteria should include business-quality outcomes, not conversion count alone.

The baseline should remain interpretable throughout the test. Query expansion, landing-page selection, conversion quality, cost, and overlap with other campaigns all need review. The controls cited by the article can limit unwanted reach, but controls do not replace monitoring or a clear threshold for stopping an unproductive experiment.

Accounts that fail the readiness assessment have a more immediate priority: repair measurement, restore downstream feedback, clarify branded intent segments, and remove constraints from generic growth. As those foundations improve, AI Max can be reconsidered with a cleaner baseline and a more credible definition of incrementality.

The durable standard is whether automation advances the advertiser’s objective while preserving trustworthy evidence. Brand campaigns should move toward AI Max only when the account can answer that question through a disciplined test.

References

CrushPress.AI – Is Your Brand Campaign Truly Ready for AI’s Prime Time?

June 9, 2026

Tag: Campaign Automation

Key takeaways

Give the system one objective and explicit boundaries

Fix the measurement loop before optimizing conversions

Use budgets and exclusions as operating controls

Monitor the budget on the window the platform uses

Apply exclusions from hardest constraint to weakest signal

Scale reviewed changes, not unchecked assumptions

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

What business data feeds change in Demand Gen

Why the update extends beyond ecommerce

Key takeaways for campaign teams

The main constraint affects campaign planning

What advertisers should prepare before using feeds

Key takeaways

The alpha changes the boundary of automation

Why network choice could improve campaign diagnosis

A useful test requires more than toggling a checkbox

What remains unresolved while access is limited

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

The delayed timetable creates a structured testing window

A measurement-first migration plan

Key takeaways

References

AI surface eligibility and campaign readiness are different questions

The reported performance evidence does not settle the brand question

Readiness starts with signals, structure, and an unmet objective

Key takeaways

A controlled experiment should protect the brand baseline

References