I’m thrilled to share that Google has just unveiled Ask Advisor, a new AI-driven tool designed to transform the way we approach campaign management, analytics, and optimization. Announced at Google Marketing Live 2026, this Gemini-powered AI is here to integrate seamlessly across Google Ads, Google Analytics, Merchant Center, and the Google Marketing Platform.
Making Waves. Ask Advisor is set to be a game-changer, acting as a unifying force that weaves together insights, workflows, and recommendations across Google’s vast marketing ecosystem.
For those of us in marketing, this means we can launch campaigns, analyze performance, and uncover optimization recommendations all without having to juggle between different tools.
Imagine asking Ask Advisor to “find new customers for my hair care products.” It would seamlessly pull details from the Merchant Center and assist in crafting a campaign right in Google Ads.
Understanding the Process. Ask Advisor connects the dots between Google Ads, Analytics, the Merchant Center, and the Marketing Platform via a Gemini-powered interface. This connectivity allows it to access a range of data to create recommendations, automate tasks, and offer insights that align with marketing goals.
It doesn’t stop there. The integration of insights from Google Ads and Google Analytics helps explain campaign performance and suggests subsequent steps.
The aim, Google states, is to democratize advanced campaign management, enabling even those without extensive technical expertise to make the most out of their advertising strategies.
This launch supports Google’s expanding lineup of AI-driven in-product agents, positioning Gemini as a fundamental layer in advertising and measurement tools.
Why This Matters to Us. Ask Advisor symbolizes one of Google’s most direct steps into agent-based advertising workflows.
Instead of interacting manually with separate reporting dashboards, campaign tools, and optimization settings, AI agents are being poised to handle operational tasks and present strategic insights.
The more substantial evolution is structural: Google is anchoring Gemini as the core across its advertising platform, potentially redefining how campaigns are developed, optimized, and evaluated.
Keep an Eye On. The biggest discussion point will be how much control advertisers are willing to cede to AI agents. Transparency over recommendations, automation choices, and reporting accuracy will be under scrutiny as Ask Advisor rolls out.
When You Can Get It. Currently in beta, Ask Advisor is available for English-language accounts, with more features anticipated later this year.
Want to Learn More? Here’s additional news from Google Marketing Live 2026:
If your paid search account is hitting its platform targets but you cannot explain which customers are real, why automation moved spend, or whether the resulting leads create value, your problem is no longer bidding. It is control.
AI has not removed human demand. It has inserted more software between a person’s intent and your business outcome. Marketing now operates among systems assessing intent, identity, risk, relevance, and value at the same time. To stay effective, you need an operating model that gives automation a clear objective, trustworthy signals, and firm boundaries.
Key takeaways
Optimize around the customer’s goal and the business outcome, not the keyword or platform conversion in isolation.
Audit identity, deduplication, qualification, and revenue signals before giving automation more freedom.
Give every automated campaign an operating envelope: a budget boundary, an approved objective, monitoring rules, an owner, and a rollback condition.
Use longer, context-rich prompts to understand intent, but do not treat entire prompts as a new keyword list.
Let PPC, SEO, GEO, content, analytics, and CRM teams work from one shared record of customer problems, constraints, evidence needs, and outcomes.
Rebuild paid search around the customer goal
The durable advantage of paid search was never the keyword itself. It was the ability to reach expressed demand, test a message, and connect acquisition to measurable post-click activity. That combination made paid search accessible, testable, and accountable in a way that traditional advertising often was not.
The keyword was simply the interface available at the time. It gave you a compressed clue about what someone wanted. A prompt or conversation can reveal much more: the underlying problem, the constraints, the desired output, the urgency, and the standard by which an answer will be judged. As discovery moves toward prompts, conversations, and AI assistants, that fuller context becomes more useful than an isolated phrase.
This does not mean copying complete prompts into a campaign and calling them keywords. It means designing your acquisition strategy around the job the person is trying to complete.
Create an intent brief before a campaign brief
For each meaningful demand theme, write a short intent brief with these fields:
Customer goal: the outcome the person is trying to achieve.
Trigger: the situation that made the goal important now.
Constraints: budget, timing, compatibility, risk, internal approval, or another limiting condition.
Evidence required: the proof the person needs before moving forward.
Disqualifiers: conditions under which your offer is not suitable.
Next useful action: the smallest meaningful step the person can take with your business.
Consider a hypothetical search for “best CRM.” The phrase is too broad to support a precise message. The actual job might be to replace a spreadsheet before a sales team expands, preserve existing contact history, and avoid a developer-led migration. A useful campaign speaks to that job and those constraints. A weak campaign repeats “best CRM” in the ad and sends every visitor to a generic product page.
Turn the intent brief into campaign decisions in a fixed sequence:
Choose the customer goal you are willing and able to serve.
Group queries by that goal, not merely by shared words.
Write the message around the desired outcome and the most important constraint.
Make the landing page state who the offer is for, what it helps them do, and what evidence supports the claim.
Include disqualifying information early enough to prevent low-fit clicks from becoming misleading conversions.
Measure the next action that represents genuine progress toward business value.
The same brief can guide paid ads, organic pages, answer-oriented content, and AI-search optimization. Each channel may need different formatting, but the underlying customer problem should not change when the channel changes.
Fix signal integrity before expanding automation
A customer journey is no longer a neat line from impression to click to conversion. Multiple systems can evaluate the same person simultaneously. An ad platform may predict high purchase intent while a fraud model lowers trust, an identity service fails to join the session to a known account, a CRM labels the record as a duplicate, or a messaging system suppresses further contact. These decisions can all be internally reasonable and still produce a broken journey.
More automation makes those contradictions move faster. It does not resolve them. When identity or conversion data is ambiguous, autonomous systems operationalize the ambiguity: they bid on it, suppress it, personalize around it, or feed it into the next model.
Write a conversion contract
A conversion contract is a shared definition of what each tracked event means. For every event used in reporting or optimization, record:
the exact user action that creates the event;
the system that first records it;
the identifier used to connect it to a person, account, order, or lead;
the rule used to prevent duplicate counting;
the timestamp and value passed downstream;
the conditions that make the event eligible for bidding;
the later business event that verifies its quality; and
the team responsible for investigating a mismatch.
Do not allow labels such as “lead,” “qualified lead,” and “customer” to carry different meanings in the ad platform, analytics system, CRM, and finance records. If the definitions must differ, document the differences and prevent teams from comparing them as if they were identical.
Then run a controlled quality-assurance journey through the whole path: ad click, landing-page action, analytics event, CRM record, qualification state, and final business outcome. Record where an identifier is created, transformed, lost, or replaced. If privacy or consent boundaries prevent a complete join, preserve that limitation in reporting. A documented blind spot is safer than invented precision.
Build a ladder from activity to verified value
Keep raw activity separate from increasingly reliable business outcomes:
Delivery: an impression or other opportunity to be seen.
Engagement: a click, visit, or interaction.
Declared conversion: a submitted form, registration, call, or purchase event.
Accepted outcome: a deduplicated event that passes your validity rules.
Qualified outcome: a lead, order, or account that meets your business criteria.
Verified value: the downstream result your organization actually wants.
Only some of these levels should steer bidding. The rest can remain diagnostic. If a form submission is easy to generate but only qualified opportunities create value, optimizing solely for submissions teaches the system to find more submissions. It does not necessarily teach it to find more qualified opportunities.
This distinction becomes critical when bot activity, fraud, or other synthetic behavior can imitate engagement. Automated systems tend to optimize what is measurable rather than determine what is true. Your measurement design must therefore separate a recorded action from a verified human or business outcome.
Watch the movement between levels. If declared conversions rise while accepted and qualified outcomes remain flat, investigate event quality, duplication, traffic mix, and identity resolution before changing bids or creative. If the platform reports improvement but the verified-value layer moves in the opposite direction, the optimization target is not representing the business goal.
Give automation an operating envelope
Effective automated bidding changes the human job. When a system can make auction-level decisions more quickly than a person, repeatedly adjusting individual bids is not a durable source of value. The higher-value work becomes monitoring automation, setting limits, and diagnosing failures.
An operating envelope defines where an automated system may act without intervention and what forces a review. It should contain:
An outcome boundary: the one primary result the campaign is permitted to optimize toward.
A spend boundary: the budget and financial exposure the system may control.
A data boundary: the events, values, audiences, and exclusions considered reliable enough to use.
A message boundary: the claims, offers, and brand language that may appear.
A change record: the date, owner, reason, and expected effect of every material configuration or measurement change.
An intervention rule: the condition that triggers investigation, limits delivery, or rolls back a change.
There is no universal threshold that fits every account. Set boundaries from your own economics, sales capacity, data quality, and risk tolerance. The important part is that the limits exist before the anomaly, not that they copy another advertiser’s settings.
Use failure patterns to decide where to look
Observed pattern
Likely control problem
First check
Spend rises while verified value stays flat
The system is finding a cheaper proxy rather than more business value
Compare platform conversions with accepted and qualified outcomes
One system marks a person high value while another suppresses the same person
Identity, consent, fraud, duplication, or eligibility rules conflict
Trace the identifier and suppression reason across systems
Reported performance changes immediately after a tracking edit
The measurement definition changed
Inspect the change record before treating the movement as customer behavior
The platform reaches its target while sales quality deteriorates
The steering metric is too far from the business outcome
Review which event and value are eligible for optimization
Teams report different totals for the same conversion
Definitions, timestamps, deduplication, or attribution rules differ
Reconcile each system against the conversion contract
Separate steering metrics from observation metrics
A campaign should not have several competing definitions of success. Choose one primary steering outcome. Keep supporting metrics visible for diagnosis, but do not let every measurable action vote equally on where money goes.
For example, clicks can explain delivery, form starts can expose landing-page friction, and submitted forms can show response volume. None of them has to be the bidding objective if qualified opportunities are the meaningful outcome. The platform dashboard is an operational view, not your business ledger. Reconcile it with downstream outcomes instead of asking it to serve both purposes.
Change one important layer at a time when practical. If you replace the conversion definition, expand targeting, change the offer, and alter the landing page together, you may get a different result without learning which change caused it. When a bundled change is unavoidable, document every component and treat the result as a system change, not a clean test of one idea.
Prepare for prompt-based journeys without guessing the ad format
AI-assisted discovery is moving beyond retrieving information toward helping people produce an answer, solve a problem, or complete a task. That raises unresolved questions about how advertising, auctions, attribution, and agent-mediated actions will work. You do not need those questions settled before improving the durable parts of your strategy.
The durable work is to understand the goal, capture its context, explain your value clearly, provide credible evidence, and measure whether the person reached a useful outcome. Those capabilities transfer across keyword search, conversational discovery, recommendations, and future agent interfaces.
Maintain a shared intent ledger
An intent ledger turns customer language into an operating asset shared by PPC, SEO, GEO, content, analytics, sales, and CRM teams. Give each intent theme a record containing:
the wording customers use;
the underlying goal behind that wording;
the trigger and constraints that shape the decision;
the questions and objections that must be resolved;
the evidence needed to establish relevance and trust;
the ad, page, or answer that serves the intent;
the next meaningful action; and
the verified business outcome associated with that action.
Populate the ledger from the customer language you can legitimately observe: query data, site search, landing-page behavior, sales questions, support requests, and customer-supplied wording. Search-query visibility has historically moved between greater transparency and greater restriction, with privacy changes obscuring some of the detail advertisers once received. Treat visible query data as a partial observation of demand, not a complete census.
Do not create separate, conflicting intent taxonomies for every channel. A person does not acquire a different underlying problem because one interaction happens in paid search and another happens in an AI assistant. Channel-specific teams can add the details they need while preserving the same customer goal, constraints, and outcome definition.
Move one campaign through the new operating model
Select one campaign with meaningful spend and a downstream outcome you can inspect.
Write its intent brief and name one primary customer goal.
Build a conversion contract for every event currently used in optimization or reporting.
Trace controlled journeys through the ad platform, analytics, CRM, qualification, and final business record.
Document contradictions between identity, fraud, suppression, audience, and value decisions.
Set the campaign’s operating envelope, including ownership and intervention rules.
Revise the message and landing page around the customer’s goal, constraints, proof needs, and next useful action.
Compare platform-reported improvement with accepted, qualified, and verified outcomes before expanding the model to more campaigns.
Start with the campaign whose reported success you trust least. Making its signals coherent and its automation legible will give you a reusable pattern for the rest of the account. That is the practical advantage in the AI era: not trying to control every machine decision, but building a system in which those decisions remain bounded, observable, and tied to real customer value.
Recently, I found myself captivated by a story shared by Dean Kadi, Head of Paid Growth at One Link Media. He recounted a fascinating experience from a PPC Live podcast that really highlighted what can go wrong when you ignore performance data. It involved a client who overrode a winning ad strategy with new creatives that just didn’t deliver.
Dean Kadi’s team had developed an exceptionally successful Meta advertising strategy for a premium woodworking brand, Rubio Monocoat, using user-generated content (UGC). Their intensive testing across creators and formats resulted in a significant ROAS improvement, proving the power of well-tested strategies.
However, the client decided to halt all the high-performing ads in favor of new, heavily branded content. Despite the polished look, these ads didn’t blend well with the Meta platform, and it was clear that engagement and conversion would likely suffer.
The client’s assumption was rooted in a customer survey that praised the brand’s color range, leading them to mistakenly prioritize this over proven data. This is a classic marketing pitfall where assumptions can cloud judgment and overshadow hard-earned data insights.
The most eye-opening moment came when the client expressed a simple wish for their new strategy to be a winner. Dean explained that in paid media, success isn’t driven by preferences or hopes—it’s determined by what resonates with audiences, as clearly shown by performance data.
When facing such situations, Dean advises agencies like us to stay calm, present evidence, and communicate risks effectively. Professionalism and clear documentation can help maintain client relationships while asserting the agency’s expertise.
As expected, the new strategy did not perform well. Underperformance became evident with increasing costs and decreasing campaign efficiency. After eight weeks of this, the client recognized the necessity to revert to the original strategy.
Reintroducing UGC ads quickly turned the tide, proving the original strategy’s effectiveness. Performance metrics showed immediate improvements, reinforcing the importance of data-driven decisions.
The overarching lesson here is that data should be your guiding light in PPC campaigns. Clients sometimes need to see failures themselves before they trust data insights. Consistently providing clear, transparent reports helps rebuild trust and guide future strategies.
Dean also pointed out that many PPC accounts still suffer from poor tracking setups. This issue is a major roadblock to optimizing performance and should be addressed urgently.
Additionally, while AI tools can enhance efficiency, they cannot replace the need for a strong strategy. Human judgment remains crucial for evaluating AI outputs and guiding successful campaigns.
In conclusion, successful PPC is all about balancing data, strategy, and communication. Document recommendations thoroughly, trust your expertise, and let audience data guide your actions. Remember, it’s the audiences who ultimately decide what works.
Recently, I’ve discovered that Google is stepping up its game in AI tools for advertisers and retailers.
They’re testing something quite futuristic called Merchant Advisor, an AI assistant integrated directly into the Merchant Center. This tool aims to simplify the process of setup, troubleshooting, and optimization for us all.
What’s happening. As someone who watches Google’s every move, I’ve noticed them testing Merchant Advisor, a cutting-edge AI-powered chatbot right within Google Merchant Center. Although in beta, its purpose is clear: to offer personalized recommendations and support, making my experience smoother than ever.
How it works. The Merchant Advisor acts like a proactive assistant, offering tasks and suggestions like setting up a returns policy or finalizing account setup steps. It feels like having an assistant who is always available to enhance my feed quality and account health.
The bigger trend. This development is part of Google’s strategy to weave AI assistants throughout its marketing products, reminding me of earlier launches like Google Ads Advisor and Analytics Advisor. The AI co-pilots are evidently becoming the norm for managing campaigns and analytics.
Between the lines. Let’s face it, Merchant Center can be a technical labyrinth, especially for smaller retailers juggling feeds, policies, and diagnostics. But now, with an embedded AI guide, I’m finding it less daunting to get onboarded quickly and spot optimization opportunities I might have overlooked.
Spotted by. This feature first caught the eye of Tamara Hellgren during a Google Ads Decoded podcast episode that focused on retail innovations.
The bottom line. It’s clear to me that Google is transforming the Merchant Center into a more intuitive, AI-assisted environment, which reflects a larger trend towards automation within its advertising landscape.
I’ve noticed that Google Search Query Reports are moving towards AI-driven interpretations, reflecting inferred intent rather than exact user searches.
What’s happening. Google has clarified that the search terms in Search Query Reports might not precisely match what users typed. Instead, the system displays the “closest approximation” due to the complexity of modern search behaviors.
What’s behind it. It’s fascinating how heavily AI now influences Google Ads’ matching systems. Rather than depending solely on specific keywords, Google increasingly interprets user intent, context, and behavioral signals to decide which ads to display.
Why we care. For those of us in advertising, Search Query Reports might become less of a mirror reflecting user language and more of a summarized representation of intent. This shift might complicate query analysis, decisions on negative keywords, and strategy around match types.
Discovered by. This update was brought to my attention by Adsquire founder, Anthony Higman, on an official Google help page discussing ad group and asset group prioritization in Google Ads.
The bottom line. Google Ads continues its evolution from keyword matching to AI-driven intent modeling, meaning we might have less insight into the exact searches that activate our ads.
Starting June 10, I’ll enjoy seamless access to valuable YouTube engagement data through Google Ads, all thanks to an automated linking feature.
I received a notification from Google alerting me that my Google Ads accounts will soon be automatically linked to any associated YouTube channels. This change comes into effect on June 10, 2026, and eliminates the need for manual connections.
Now, without lifting a finger, I can access a world of video engagement data and targeting features directly through Google Ads.
Why it matters to me. By linking my YouTube channel, I can now dive into deeper insights and leverage more advanced targeting options that I might have otherwise overlooked.
With this automation, video data becomes a standard tool in my campaign optimization arsenal.
Take a closer look. I’ll have instant access to organic video metrics like view counts right within Google Ads.
I’m also able to create audience segments based on user interactions with my YouTube content, such as video views and channel engagement.
Extra benefits. This integration means I can track ‘earned actions’ like subscriptions or additional views spurred by my ads, making these interactions valuable conversion signals.
Such insights offer a clearer picture of how my video campaigns impact user behavior beyond mere clicks.
What I’m watching for. It’ll be fascinating to see how my measurement strategies evolve with the integration of organic and paid video data, and whether this encourages a broader adoption of engagement-based conversion tracking.
The bottom line. Google is making it impossible to ignore YouTube insights, turning automatic linking into a necessary step for honing targeting, measurement, and performance.
First spotted. Multiple advertisers, including myself, were informed by Google. Notable mentions are Menachem Ani, Hana Kobzová, and Arpan Banerjee.
You are not choosing between manual Google Ads and a black box. You are deciding which decisions the system may make, what evidence it may use, and which mistakes it must never be allowed to make.
If AI Max, journey-aware bidding, or demand-led budgeting is on your roadmap, build that control system before you enable more automation. The safest operating model is simple: let AI handle frequent, reversible decisions, while you keep firm boundaries around landing-page eligibility, business goals, spending, and measurement.
Control has moved upstream of the individual decision
Advertisers often judge control by counting settings: keywords, bids, URL rules, daily budgets, and exclusions. That worked when campaign management centered on direct instructions. AI-driven campaigns change the location of control. You increasingly govern the inputs and boundaries, while the system makes more of the execution decisions inside them.
This is still control, but only when your inputs express the business clearly. A page feed full of loosely classified URLs is not a meaningful boundary. A conversion setup that treats every lead as equally valuable is not a meaningful objective. A flexible budget with no period-level ceiling is not a financial policy.
Before automating a campaign decision, assign it to one of five layers:
Control layer
Question you must answer
Proper division of responsibility
Eligibility
Which pages, products, locations, or offers may receive traffic?
You define the allowed set; automation works only inside it.
Objective
Which measurable action represents progress, and which represents business value?
You define and validate the signals; automation responds to them.
Economics
How much may be spent, over what period, and for what return?
You set the financial limits; automation allocates within them.
Execution
Which eligible opportunity should receive the next unit of spend?
Automation can make the high-frequency decision.
Evidence
What would prove that automation improved the business outcome?
You set the evaluation standard and decide whether to continue.
The distinction matters because execution errors and policy errors have different consequences. A single imperfect bid may be recoverable. A campaign-wide permission to send traffic to the wrong section of a large site can waste money repeatedly. Keep direct controls where an error would be expensive, difficult to detect, or hard to reverse.
Protect landing-page eligibility before activating AI Max
Landing-page control is the most immediate gap for teams moving from Dynamic Search Ads to AI Max. DSA could be arranged around categories, URL paths, and page rules that reflected a site’s architecture. AI Max does not reproduce every one of those targeting methods. In particular, the familiar “page contains” condition is not fully supported.
For a large or structured site, make that translation as a separate migration project:
List the pages that are allowed to receive paid traffic. Do not begin with the whole index and remove bad pages later. Start with a deliberate eligible set. A mistaken exclusion can block useful demand, but an overly broad inclusion can repeatedly spend against irrelevant, unavailable, or low-value pages.
Classify eligible pages with stable custom labels. Labels should describe business meaning such as product family, service line, region, margin group, lead type, or promotional eligibility. Avoid labels that merely repeat temporary campaign names; they become useless when the account structure changes.
Use ad-group inclusions to create local relevance. An ad group should receive only the URL groups appropriate to its intent and offer. If every ad group can reach every eligible page, the page feed is an inventory list rather than a targeting control.
Use campaign exclusions for non-negotiable boundaries. Apply them where a page class must not receive traffic from that campaign. Record the business reason for each exclusion so a future cleanup does not remove a safeguard that looks redundant.
Check the resulting landing pages, not just the configuration. Review where real traffic lands and ask whether the page matches the user’s likely intent, presents the intended offer, and supports the conversion action used by bidding.
Custom labels are the key design choice. A label such as “campaign-7” tells the system where a URL happened to be used. A label such as “enterprise-demo-eligible” states a policy. The second survives campaign reorganizations and gives you a reusable boundary for testing.
Be especially cautious with migrated DSA rules. Unsupported rules may continue functioning as read-only legacy rules that cannot be edited. That makes them dependencies, not durable controls. Document what each one permits or blocks, then recreate the intended outcome with page feeds, labels, inclusions, or exclusions where possible. Do not build a new operating model around a setting you can no longer maintain.
AI Max already applies an inventory-aware safeguard for out-of-stock items, but stock status is only one reason a page may be unsuitable. A page can be technically available while carrying the wrong offer, serving the wrong market, or producing poor downstream value. Keep your own eligibility model for those business distinctions.
Google has also signalled future account-level exclusions based on page content and titles. Treat those as prospective capabilities until they are present and usable in your account. A planned control cannot protect current spend.
Give automated bidding an optimization brief it can actually follow
Automated bidding cannot infer the distinction between a convenient measurement event and a valuable business outcome. If your account reports both as equivalent conversions, the system receives permission to pursue whichever is easier to generate.
That risk becomes more important as Google gives bidding a wider view of the customer journey. Journey-aware Bidding is a beta capability that can incorporate non-biddable conversions as additional journey context. More context can help only when the events are reliable and their roles are clear. An event should not be included merely because it is measurable.
Write a conversion map before changing the bidding system. For each event, record:
What the user actually did.
Whether the event is a progress signal or the business outcome.
Whether it is recorded consistently across campaigns and devices.
Whether duplicates, spam, cancellations, or low-quality leads can inflate it.
Which team owns its definition and can explain a sudden change.
Whether the event’s value reflects the economics you want the campaign to pursue.
Consider a campaign that records an inquiry form immediately but learns lead quality later. The form is useful journey evidence, but it is not automatically equivalent to a qualified opportunity or sale. If the system sees only form volume, it can improve the reported metric while sending the sales team more poor-fit leads. The automation is following the brief it received; the brief is the problem.
Use three tests for every signal you expose to bidding:
Interpretability: Can you describe the event in one sentence without vague terms such as “engagement” or “intent”?
Stability: Would a tracking, form, or CRM change alter the event count without changing actual demand?
Economic direction: If the system produced more of this event, would that usually move the business toward revenue, margin, retention, or another declared outcome?
If an event fails one of those tests, repair or separate it before asking AI to use it. Adding an unreliable signal does not create a fuller customer journey. It creates a larger measurement surface for the bidding system to exploit unintentionally.
Apply the same discipline to expansion features. Google reported that Smart Bidding Exploration produced 27% more unique converting users and has said the capability is expanding beyond Search into Performance Max and Shopping. Treat that figure as a vendor-reported result, not a profitability guarantee for your account. Unique converting users, conversion quality, revenue, and profit answer different questions.
Your test should therefore have two scorecards. The platform scorecard can include conversion volume and unique converters. The business scorecard should use the downstream outcome that justifies the spend. Expansion earns a larger rollout only when both move in an acceptable direction.
Automate budget pacing without outsourcing financial policy
Demand-led budgeting changes when money is spent, not why the money is available. It can increase spend when the system detects stronger opportunity and conserve it when demand is weaker. Total budgets can also shift management away from repeated daily changes toward a defined spending period.
That can remove genuine operational work. Advertisers using total budgets saw a Google-reported 66% reduction in manual budget adjustments. But fewer adjustments measure workload, not commercial success. A campaign can require less maintenance and still spend against low-quality conversions or an unsuitable product mix.
Before enabling demand-responsive pacing, write down four constraints outside the campaign interface:
The hard period ceiling: the maximum amount the campaign is authorized to spend over the relevant period.
The unit-economics condition: the business result that must remain acceptable as spend increases.
The capacity condition: the inventory, fulfillment, sales, or service limit beyond which additional demand loses value.
The intervention condition: the specific measurement or business change that requires a human review, pause, or budget reduction.
This matters because the system can respond to demand visible in the advertising environment, but it does not automatically know every private constraint in your business. If cash timing, fulfillment capacity, or lead-handling capacity cannot tolerate a high-spend day, flexible pacing creates financial exposure unless you constrain the period and monitor the limiting resource.
Do not pool campaigns under one flexible budget merely because they share a channel. Keep materially different economics separate. A campaign optimized for immediate purchases and one optimized for leads with delayed qualification should not inherit the same scaling decision unless you can compare their downstream value on a consistent basis.
Budget automation should be the last layer you expand, not the first. First confirm that eligible traffic reaches appropriate pages. Then confirm that bidding responds to trustworthy outcomes. Only then give the system more freedom to alter spend timing. Otherwise, faster pacing amplifies an unresolved targeting or measurement problem.
Roll out one delegated decision at a time
Turning on new landing-page selection, bidding exploration, journey signals, and budget pacing together may produce a different result, but it will not tell you which change caused it. A controlled rollout preserves your ability to diagnose and reverse.
Name the delegated decision. State whether the test concerns page selection, opportunity exploration, bid response, or budget pacing. Do not use “more AI” as the test definition.
Define forbidden outcomes. Examples include traffic to an ineligible site section, spend beyond the authorized period total, or growth in leads without acceptable downstream quality.
Prepare the input layer. Finish the URL classification, conversion audit, or financial constraints needed for that decision.
Capture a comparable baseline. Use the same campaign scope and the same business definitions you will apply after the change.
Change one control layer. Hold the others stable enough to make the result interpretable.
Review platform and business outcomes separately. More conversions may be a useful platform result, but it does not settle whether the change produced better customers or better economics.
Apply a prewritten rollback rule. Decide what failure means before spend is affected. If you wait until after the result, pressure to defend the test can move the standard.
Scale only after the boundary holds. A good average result is not enough if the campaign repeatedly violates landing-page, quality, or spending constraints.
The review cadence should match the business process, not the speed of the interface. A lead-generation campaign cannot be judged responsibly before the quality signal exists. An ecommerce campaign should not be scaled from order volume alone if cancellations or product mix materially change its value. Wait for the outcome needed to answer the commercial question, while keeping hard spend limits in place.
Key takeaways
Keep firm human control over eligibility, objectives, economic limits, and the evidence required to continue.
Translate DSA URL logic into page feeds, meaningful custom labels, ad-group inclusions, and campaign exclusions before relying on AI Max.
Treat unsupported read-only DSA rules as temporary legacy dependencies, even when they still function.
Use journey signals only when you can explain their relationship to the business outcome and trust their measurement.
Do not treat a vendor-reported increase in conversions or reduction in manual work as proof of profitable growth.
Expand budget automation only after landing-page selection and conversion quality are under control.
Delegate one decision at a time and define rollback conditions before the test begins.
Google Ads is moving the advertiser’s job from repeated intervention toward system design. Your next move is to choose one campaign and write a one-page policy covering eligible landing pages, optimization signals, spending authority, and rollback conditions. If the available controls cannot enforce that policy, do not automate that decision yet.
If your parked-domain revenue dropped after Google’s Search Partner Network changes, do not move every name to the first network promising replacement income. First determine which domains lost a productive demand source, which never covered their costs, and which should be sold, developed, held, or allowed to expire.
The practical goal is not to recreate the old arrangement at any cost. It is to give every domain a defensible job, measure that job using net income rather than headline revenue, and avoid exposing an entire portfolio to an untested provider or a careless DNS change.
Google removed a monetization route, not every possible use
This distinction matters. The change affected a Google Ads inventory channel. It was not an organic search algorithm update, a domain-registration rule, or a declaration that an unused domain has no value. A domain can still receive direct traffic, attract a buyer, protect a brand, support a real website, or use a monetization provider operating through a different advertising ecosystem.
It also means SEO, AEO, and JSON-LD are not workarounds for the lost placement. Adding generated text or schema to a parking page does not turn it into a useful developed site. If you decide to develop a domain, build something that serves an identifiable audience and use structured data only to describe what is genuinely visible on the page.
When a replacement provider says its setup is compatible with Google, ask what that means. Is Google supplying the advertising demand, or is the provider using an independent network? If Google is involved, which product and policy govern the inventory? If Google is not involved, what ad formats, traffic restrictions, disclosures, and destination controls apply? A vague reference to Google is not a compliance answer.
Rebuild the economics one domain at a time
A portfolio total can hide weak domains. One valuable name may subsidize dozens of renewals, while dashboard revenue can look healthy even when deductions and recurring costs leave little cash. Build a domain-level ledger before testing a replacement.
Record the domain, registrar, renewal date, renewal cost, nameservers, and current purpose.
Preserve the longest comparable traffic history available. Separate direct, referral, search, geographic, and device data where the reporting supports it. Treat an analytics label such as direct as a traffic bucket, not proof that every visitor typed the domain.
Record estimated revenue, adjustments, invalid-traffic deductions, and the amount actually paid. The paid amount is the useful starting point for cash-flow decisions.
Keep the old Google-linked monetization period separate from any replacement-provider period. Blending them makes a declining domain look stable and prevents a fair test.
Add sale inquiries, offers, marketplace activity, and any evidence that the name has value independent of advertising income.
Flag email records, redirects, verification records, brand-protection reasons, trademark concerns, and other dependencies that make a DNS change or expiration risky.
Calculate net contribution as paid monetization revenue minus renewal fees, provider or marketplace charges, payment costs, and other direct operating expenses. If the available history does not cover a complete renewal cycle, mark the result as provisional instead of annualizing a short burst of traffic.
Then sort the portfolio by renewal date and net contribution. A domain approaching renewal with negative or unknown economics needs a decision before the charge occurs. A profitable domain still needs review if its traffic cannot be explained, its name creates legal exposure, or its provider can change the user experience without adequate controls.
Assign each domain a specific job
Do not force every domain into the same monetization model. Assign one primary role and document why the domain belongs there.
Cash-flow asset. Use this role when the domain has repeatable, explainable traffic and produces positive net contribution. Keep monitoring deductions, complaints, landing behavior, and traffic composition; passive does not mean unmonitored.
Monetized sale asset. A domain can remain monetized while it is listed for sale when the provider and marketplace support that arrangement. Give prospective buyers a clear route to the sale page, and retain clean revenue records that show dates, gross income, deductions, net income, traffic sources, and provider dependencies.
Development candidate. Choose this only when the name supports a credible subject, service, product, or community that you are prepared to maintain. A real site requires useful content, a clear owner, navigation, support, security, and ongoing operations. Thin pages created only to escape a parked-domain classification are not a durable strategy.
Defensive holding. Some names justify renewal because they protect a brand, campaign, product, or common variation even when they produce no ad revenue. Track that purpose separately so the domain is not judged by a monetization metric it was never meant to satisfy.
Exit or lapse candidate. Use this role when a domain has no meaningful traffic, buyer interest, development case, or defensive purpose. Expiration can be difficult to reverse because another party may register the name. Before allowing it to lapse, check email and recovery-address use, redirects, verification records, internal links, contracts, trademarks, and ownership obligations.
Revenue can strengthen a sale case, but it is not the domain’s entire value. A buyer needs to know whether the income is repeatable, whether it depends on one provider, and whether the traffic will survive a transfer. Do not present a short monetization run as a permanent yield.
Be especially cautious with mistyped or trademark-adjacent names. Advertising revenue does not cure an intellectual-property problem, and a provider’s willingness to accept a domain does not establish your right to monetize it. If ownership or use could conflict with another party’s mark, obtain advice from a qualified intellectual-property lawyer before monetizing, marketing, or transferring the domain.
Test replacement providers without risking the portfolio
Replacement platforms may use formats such as Direct Click or Related Search on Content. RSOC units direct visitors toward sponsored search results, while Direct Click is a provider label whose exact user flow should be demonstrated rather than assumed. Some platforms also use DNS-level integration to connect domains at scale. That can simplify deployment, but it also increases the cost of a configuration mistake.
Select a limited test cohort. Include domains with enough explainable traffic to produce useful observations, but exclude critical brand names, active email domains, and irreplaceable assets from the first migration.
Export the full DNS zone before changing nameservers. Record A, AAAA, CNAME, MX, TXT, and verification records, along with the current redirect behavior. A nameserver change can interrupt email, authentication, redirects, and third-party verification even when the parked page itself appears to work.
Read the provider agreement and ask which traffic types are accepted. Confirm how invalid traffic, deductions, clawbacks, account suspension, payout timing, exclusivity, domain sales, and termination are handled.
Inspect the actual visitor experience on relevant devices and locations. Record the page, ad disclosure, clicks, redirects, advertiser destinations, sale link, consent behavior, and any browser or security warning. Do not rely on a dashboard screenshot as evidence that the user experience is acceptable.
Measure paid revenue per valid visit, net contribution, geographic and device mix, deductions, complaints, and unexplained traffic changes. Compare the test cohort with its own preserved baseline rather than with a provider’s best-performing example.
Define rollback conditions before launch. Misleading presentation, unwanted redirects, broken email, malware warnings, abuse complaints, missing reports, or unexplained deductions should trigger investigation or restoration of the previous DNS configuration.
Provider case studies require particular care. One vendor-supplied example describes a redacted .ws domain acquired for $5.95 and earning about $7 per month after being connected exclusively to the platform. It also reports no abuse complaints during operation. The domain, traffic volume, audience mix, portfolio distribution, and full cost basis are not disclosed, and the publisher does not confirm or dispute the sponsor’s conclusions.
That example can show that monetization is possible; it cannot forecast your return. Do not multiply its monthly figure by the number of names you own. Your decision should come from paid results on your own traffic, after costs, with enough operational detail to explain why the result occurred.
Keep an abuse log even when no complaint has arrived. Record user reports, registrar notices, advertising-policy messages, security warnings, and provider responses by domain. The absence of a report is not evidence that every ad destination or redirect is safe; it only means no report has reached you through the channels you monitor.
Key takeaways
Google’s change removed the previous parked-domain placement route from its Search Partner Network; it did not eliminate every sale, development, defensive, or independent monetization option.
Judge each domain by paid net contribution and strategic purpose, not gross dashboard revenue or portfolio-wide averages.
Give every domain one documented role: cash-flow asset, monetized sale asset, development candidate, defensive holding, or exit candidate.
Treat provider projections and single-domain examples as sales evidence, not expected portfolio performance.
Test DNS-based monetization on a limited cohort, preserve the full DNS zone, inspect the visitor journey, and establish rollback conditions before migration.
Do not use thin content, AI-generated pages, or schema markup as a cosmetic workaround for a domain that has no genuine developed-site purpose.
Start with the renewal calendar and the domains responsible for most of your recorded income. Give each one a job before its next renewal, and test replacement demand only where you can explain the traffic and safely reverse the setup. The useful question is no longer whether parked domains still make money in general. It is whether each domain earns, protects, or supports enough value to justify another cycle.
If any reporting, bidding, or campaign-management workflow still calls Google Ads API v20, June 10, 2026 is a hard failure boundary. Any request sent to v20 after the cutoff will fail, so a healthy dashboard or successful scheduled job on June 9 does not prove that you are ready for June 10.
Your job is to find every remaining v20 request, move each affected workflow to a newer version, and produce evidence that the replacement works in production. That requires more than changing a version string. It requires an inventory, representative testing, a staged cutover, and monitoring that can distinguish fresh data from stale output.
Know exactly what will fail at the cutoff
The sunset applies at the API request boundary. It does not, by itself, mean that a Google Ads account or campaign disappears. It means a workflow loses access whenever the request it needs still targets v20.
The business consequence depends on what that request does:
Reporting and data pipelines can stop collecting new data, leaving dashboards, attribution processes, or client reports with gaps.
Campaign automation can stop reading or applying intended changes, including workflows connected to bidding and campaign management.
Internal tools can fail when a user opens a screen, requests a report, or submits a change that depends on v20.
Third-party platforms can break even when your own code is current, because the version choice may live inside the vendor’s backend.
A failed reporting job is not always visually obvious. A dashboard may continue showing its last successful dataset unless it also displays data freshness. A failed write does not necessarily leave an account in a safe or paused state; it may simply leave the previous campaign settings in place. Review each workflow’s retry, alerting, and failure behavior so that an API error cannot masquerade as a successful run.
Translate every technical dependency into an operational consequence. Instead of recording only “reporting service uses v20,” document which report stops, who consumes it, how quickly stale data becomes harmful, and who owns recovery. That mapping tells you which migrations must move first.
Key takeaways
Google Ads API v20 requests will fail after June 10, 2026; the deadline is not a warning-only deprecation milestone.
Inventory observed API traffic and stored configuration. Either view alone can miss a dependency.
Test complete workflows on a newer API version, not merely authentication or one sample request.
Run read-only comparisons in parallel where useful, but do not duplicate campaign-changing requests across versions.
Cut over early enough to observe a full operating cycle and restore v20 temporarily if the new implementation fails before the sunset.
Build an inventory that includes hidden and dormant calls
Start with actual traffic, then reconcile it against code, configuration, schedules, and vendor dependencies. An application list assembled from memory will miss old scripts, shared services, and jobs owned by teams that no longer think of themselves as Google Ads API users.
List the environments and projects. Include production, staging, reporting infrastructure, serverless jobs, shared integration projects, and systems managed by another team.
Inspect recent activity. Record which projects still produce v20 traffic and which methods they call.
Cover the complete job cadence. Your observation period must include infrequent workloads such as weekly, monthly, or manually triggered jobs. Zero traffic during an idle period proves nothing.
Search stored configuration. Look for literal v20 references, version selectors, client-library dependencies, deployment variables, request builders, infrastructure definitions, and copied scripts.
Attach an owner to every dependency. An unidentified service is not ready merely because it appears inactive. Someone must decide whether it should be migrated, retired, or verified as unused.
Traffic inspection and configuration inspection answer different questions. Traffic tells you what ran. Configuration tells you what may run later. Keep both in the migration register.
Dependency surface
What to locate
Useful readiness evidence
Custom applications
Version settings, client dependencies, request construction, and deployment configuration
Representative requests succeed on the target version and production activity no longer shows v20
Scheduled data pipelines
Job definitions, orchestration schedules, exports, and downstream consumers
A complete scheduled run finishes with fresh, complete output
Campaign automation
Read and write paths, retry behavior, approval controls, and alerts
A controlled test produces the intended state once and failures reach an owner
Third-party platforms
Vendor-owned connectors, reporting modules, and automation features
The vendor confirms the production version and you verify your own affected workflows
Dormant or manual tools
Occasional scripts, archived repositories, runbooks, and analyst utilities
The tool is migrated, formally retired, or blocked from future v20 use
Ask vendors for feature-level confirmation
A generic claim that a platform “supports the Google Ads API” is not enough. One module may be current while a less visible exporter or automation feature still uses v20. Ask the provider:
Which API version does each feature used by your account call in production?
Has every v20 workload been migrated, or only the primary integration?
When will the production cutover occur?
How can you verify that your tenant is using the newer version?
What happens to queued jobs, retries, and cached reports if a request fails?
Keep the response with your migration record, then test the feature yourself. Vendor confirmation transfers information, not operational responsibility.
Migrate the workflow, not just the version label
Choose a newer supported API version that works with your client stack and the capabilities your workflows need. Use Google’s release notes and upgrade guides to identify required changes. Do not assume that editing a version constant is sufficient: client dependencies, available fields, request structures, generated types, and response handling may also need attention.
A practical migration sequence looks like this:
Capture a baseline. Record representative inputs, expected outputs, normal completion signals, and current error behavior for each workflow. Use stable comparisons where possible because live campaign data can change during testing.
Update the client and application together. Change the supported client dependency, version configuration, request construction, and any code affected by the official upgrade guidance. Check deployment manifests and runtime variables as well as the repository.
Test authentication and simple reads. Confirm that the application can connect using the credentials and account scope it will use in production. Connectivity is only the first gate, not the completion criterion.
Exercise representative read workflows. Run the same account scope, date range, filters, pagination path, and downstream transformation used by the real job. Compare required fields, completeness, row-level invariants, and freshness rather than relying on a single successful response.
Test writes under controlled conditions. Do not change live spend merely to prove connectivity. Use an approved test environment, test account, or non-spend-altering path where your setup supports one. Verify that the intended resource changes once and that retries cannot duplicate an action.
Validate downstream consumers. A successful API response does not prove that a dashboard, warehouse load, bid process, notification, or internal interface can consume the new output correctly.
Release in stages. Move a bounded set of workloads first, watch their results, and expand only after the expected operating signals remain healthy.
Parallel validation is useful for read-only workloads. You can run equivalent reporting requests on v20 and the target version, then compare the resulting datasets while v20 remains available. Avoid sending campaign-changing requests through both versions: duplicate writes can produce real account changes and financial consequences. For write paths, use a controlled test followed by a staged production rollout.
Preserve a temporary rollback path during the early cutover, but recognize its expiration date. Before June 10, a rollback to v20 may buy time to fix a problem. After the sunset, v20 is no longer a viable recovery plan because its requests will fail. Your post-cutoff contingency must keep the newer version in place, disable the affected workflow safely if necessary, and route the failure to a named owner.
Define readiness with production evidence
“The code was upgraded” is a progress update. It is not a definition of done. Close the migration only when you have evidence across configuration, runtime traffic, workflow output, and ownership.
Every known application, script, scheduled job, and integration has an owner and an explicit migrate-or-retire decision.
Each active workflow completes successfully on the selected newer API version using representative accounts and request types.
Production configuration and deployed client dependencies point to the intended version.
No v20 activity appears across the relevant Cloud projects during a period that covers the full operating cadence of the workflows.
Reporting outputs expose freshness and completeness, so stale data cannot look current.
Campaign-changing automation has controlled retry behavior and a human receives actionable failure alerts.
Third-party features have been confirmed by the provider and verified through your own account-level test.
The rollback plan works before the cutoff, and the post-cutoff contingency does not depend on v20.
Campaign owners, analysts, engineers, and support staff know when the cutover occurred and where failures will be reported.
Be careful with negative evidence. Seeing no v20 requests is meaningful only if every relevant workload had an opportunity to run. A monthly exporter that has not reached its schedule can remain invisible until after the deadline. Pair runtime inspection with the dependency register, then record the last successful target-version execution for every retained workflow.
Set your internal cutover early enough to run a complete operating cycle while v20 can still serve as a temporary fallback. Name the owner, start the inventory, and schedule the target-version validation now. The date that matters internally should be the day you can prove v20 is gone, not June 10 itself.
Your Performance Max campaign can look efficient while your sales team rejects nearly every lead. That isn’t a contradiction. It means the campaign is succeeding against a conversion signal that doesn’t represent the business outcome you actually need.
You don’t need complete visibility into every automated bid to fix that problem. You need a reporting chain that connects platform activity to qualified pipeline, plus a disciplined way to intervene when the chain breaks. Here is how to build it.
Start with the business outcome, not the campaign CPL
Cost per lead is only useful when the word lead has a stable business meaning. A form submission, sales-accepted lead, opportunity and closed deal are not interchangeable outcomes. If PMax counts the first while your team values the third, a falling CPL can hide deteriorating performance.
Begin with a conversion inventory. List every action available to the campaign, then write down what each action proves. A form submission proves that someone completed a form. It does not prove that the person fits your market, has buying authority or represents a real organization. Treating those facts as equivalent gives automation an easy target and gives you misleading reporting.
Define the funnel stages your team can verify. Use the stages already applied consistently in your CRM, such as inquiry, accepted lead, opportunity and won business. Don’t create a more elaborate taxonomy than sales can maintain.
Choose the deepest dependable optimization signal. The ideal event is close to revenue, recorded consistently and available often enough to guide the campaign. If closed business is too sparse or delayed, use the nearest reliably graded stage rather than pretending a raw form fill is equally valuable.
Keep earlier actions for diagnosis. An inquiry can still reveal landing-page or creative behavior. It simply shouldn’t be allowed to masquerade as qualified demand in your business reporting.
Remove obvious form abuse before asking the algorithm to learn. Controls such as reCAPTCHA can reduce low-quality submissions. They don’t replace qualification, but they prevent some worthless activity from being treated as useful training data.
No tracking configuration can rescue an undefined lead. Sales and marketing must agree on the rule for accepting or rejecting one, and that rule must be applied consistently. Otherwise, imported outcomes encode internal inconsistency rather than buyer quality.
This also changes how you evaluate cost. A campaign with a higher form-fill CPL may be the better investment if more of those forms become accepted leads or opportunities. Compare cost at the deepest mature stage available, not merely at the fastest stage the ad platform can report.
Build a reporting chain that answers five different questions
No single PMax report can tell you whether a campaign is working. Placement data explains where ads appeared. Channel data shows how automated delivery was distributed. Intent reports add search context. Asset reporting helps you inspect messages and formats. Your CRM determines whether any of that activity produced business value.
Reporting layer
Question it answers
Evidence to inspect
Decision it can support
Business outcome
Did the lead progress?
CRM qualification, opportunities, won business and imported offline outcomes
Change the optimization signal, qualification process or lead controls
Campaign and channel
Where did automated delivery produce recorded conversions?
Campaign results, segmented conversion metrics and account-level channel reporting
Investigate channel mix and decide where a more focused follow-up test belongs
Publisher placement
Which inventory received spend and recorded conversions?
Microsoft’s Website Publisher URL report with spend and conversion data
Identify inventory worth studying, protect brand safety or add a justified URL exclusion
Intent and competition
What demand patterns surrounded performance?
Google search term insights, auction insights, search themes and brand controls
Refine intent guidance, separate branded demand or investigate a competitive change
Creative asset
Which messages and formats appear to attract response?
Asset-level reporting and controlled creative tests
Retire weak messages, add qualification or develop a stronger variant
Microsoft’s PMax reporting makes the placement layer more actionable by adding conversion and spend metrics to the Website Publisher URL report. That is materially better than a list of domains with no economic context. You can see which placements consumed budget and which were associated with recorded conversions.
But recorded conversions are still only as trustworthy as the conversion definition. A publisher with several form fills is not automatically a strong B2B placement if none of those people survive qualification. Conversely, a publisher with spend and no immediate conversion is not automatically waste if your evaluation window closes before leads mature. Join placement evidence to the CRM before making an efficiency judgment.
Google’s channel, search-term, auction and asset reporting answers different questions. Channel reporting can expose where reported results originate, while search term insights add context about demand. Auction insights help you notice competitive conditions. Asset reporting shows how creative components are being evaluated. None of these views, by itself, proves incremental revenue.
The practical rule is simple: use platform reporting to locate a pattern, then use downstream data to decide whether that pattern deserves action. A report is diagnostic evidence, not a verdict.
Apply PMax controls in the order that reduces uncertainty
When lead quality is poor, it is tempting to change audience signals, creative, themes and exclusions at once. That creates activity without producing a clear lesson. Apply controls from the bottom of the measurement chain upward.
1. Repair the conversion signal and form hygiene
First confirm that legitimate leads can be connected to later CRM stages and that obvious spam is filtered. If the campaign is rewarded for an event your business doesn’t value, every targeting adjustment rests on a faulty objective.
Inspect conversion metrics separately rather than blending every action into one total. A campaign that produces many shallow actions and few qualified outcomes should not receive the same interpretation as one that advances prospects through the funnel. Segmented conversion reporting and offline outcomes give you the distinction needed to see that difference.
2. Feed the system a clean first-party audience signal
A large CRM export is not automatically a useful audience input. It may mix customers, unqualified inquiries, inactive records, students, vendors and prospects at unrelated stages. That teaches the system that all records deserve equal attention.
Clean and segment the data before using it. Start with groups closest to a verified revenue event, provided each group has a consistent business definition. A list of accepted leads or opportunities usually carries clearer intent than an undifferentiated list of everyone who has ever completed a form. The value comes from the label, not the file size.
Treat audience signals as guidance to be validated. After launch, compare the resulting leads with the segment characteristics you intended to emphasize. If the campaign finds cheap conversions outside your real customer profile, the CRM outcome should overrule the attractive platform metric.
3. Use search themes and brand exclusions to clarify intent
Search themes can guide Google PMax toward the demand you want it to explore. Build them around the problems, use cases and buying situations your qualified prospects actually express. Avoid turning themes into a loose catalogue of every phrase related to your industry.
Brand exclusions solve a separate problem. If your objective is to assess incremental acquisition, branded demand can make an automated campaign look more efficient than its prospecting work really is. Search themes and brand exclusions provide useful control over those inputs and costs. Decide explicitly whether a campaign should capture existing brand demand or discover new demand, then configure and judge it against that purpose.
Review search term insights after the campaign has produced meaningful evidence. Look for patterns that indicate the wrong buyer, job seeker, student, consumer use case or research intent. Those patterns should lead to a specific hypothesis about themes, messaging or conversion quality. They shouldn’t trigger an indiscriminate attempt to block anything unfamiliar.
4. Treat placement exclusions as a precise control
Microsoft’s placement spend and conversion data can expose publishers that are clearly unsuitable for the brand or economically unproductive after downstream outcomes are considered. High-performing inventory can also inform a separate Audience Ads or remarketing strategy, while unsuitable inventory can be added to an account-level URL exclusion list.
Account-level exclusions have a wider blast radius than a campaign-specific observation. Before adding one, verify the exact domain, the reason for exclusion and the other campaigns that may rely on it. A clear brand-safety conflict can justify immediate action. An apparent performance problem needs more context: adequate spend relative to your economics, a review window long enough for lead grading and evidence that the recorded conversions did not progress.
Do not turn the placement report into a manual bidding console. Its best use is to find material exceptions: unsafe environments, obvious mismatch, persistent waste or inventory that deserves a focused follow-up strategy.
5. Make creative qualify the prospect
B2B creative should do more than generate attention. It should help the right buyer recognize relevance and help the wrong visitor recognize a mismatch. State the use case, intended role, business context or other genuine qualifier that distinguishes your offer. Vague creative may attract more interactions while making lead quality harder to control.
Video deserves deliberate treatment because YouTube is an important part of PMax inventory. Google also provides AI-assisted asset creation, creative testing and asset-level reporting. Use those capabilities to test a defined message difference, not merely to produce more variations. A useful test might compare problem-led positioning with outcome-led positioning, or broad language with a clear buyer qualifier.
Read asset results alongside lead quality. An asset that attracts many conversions but disproportionately weak prospects may be doing its job badly, even if the platform labels it positively. The next variation should address the mismatch in the message rather than simply changing the visual treatment.
Run a decision loop that sales can audit
PMax optimization becomes safer when every change starts with an observed business problem. Use the table below as a diagnostic map. The first column is a symptom, not a conclusion.
What you notice
What to verify
What to do next
Platform conversions rise while accepted leads stay flat
Which conversion actions increased, whether form abuse changed and whether offline outcomes are returning correctly
Correct the optimization signal or lead-quality controls before changing audience inputs
Form-fill CPL rises while opportunity creation improves
Cost per accepted lead and opportunity for a fully graded cohort
Judge the campaign on the deeper outcome rather than cutting it solely because the shallow CPL increased
A publisher consumes spend without qualified progression
Placement spend, recorded conversions, CRM outcomes, evaluation lag and brand suitability
Exclude a verified unsafe or persistently wasteful URL; otherwise gather enough context to distinguish delay from failure
One channel appears to overperform
Conversion mix and lead quality by channel
Use the pattern to design a focused channel or audience test instead of assuming every reported conversion has equal value
An asset attracts response but weak prospects
The CRM quality of leads associated with its message and offer
Add a buyer, use-case or business-context qualifier and test the revised message
Branded demand dominates the visible intent pattern
Whether the campaign’s job is brand capture or incremental acquisition
Use brand controls where appropriate and report branded and non-branded intent against separate expectations
Auction conditions change near a performance shift
Whether conversion quality, creative, landing experience or campaign inputs changed at the same time
Treat auction data as context and test the most plausible cause rather than declaring competition the cause automatically
Make the review window match your buying process. If sales has not yet graded the leads in a cohort, that cohort cannot support a final quality conclusion. Label it incomplete instead of filling the gap with the platform’s faster metrics.
Keep a short decision log for every material intervention. Record the observed problem, the evidence from each reporting layer, the change made, the downstream metric expected to move and the point at which the affected leads will be mature enough to review. This prevents the team from repeating tests or crediting an unrelated performance swing to the latest edit.
Change one major layer at a time where practical. If you replace the audience signal, add themes, exclude publishers and rewrite every asset together, you may improve results but learn very little about why. Sequencing changes turns automation from an opaque system into a set of testable business decisions.
Key takeaways
PMax optimizes the conversion definition you provide, so a cheap form submission is not evidence of efficient B2B growth.
Use offline outcomes and consistent CRM stages to evaluate cost per qualified result, not just cost per initial lead.
Placement, channel, intent, auction and asset reports answer different questions. Join them to downstream outcomes before acting.
Clean first-party audience segments, focused search themes and qualifying creative give automation better guidance.
Use URL and brand exclusions deliberately. Confirm the scope, business purpose and downstream evidence before restricting delivery.
Log each material change and wait until the affected lead cohort is mature enough to judge.
Start with the latest lead cohort that sales has completely graded. Compare its CRM outcomes with the campaign, channel, intent, placement and asset evidence available on your platform. Find the largest break in that chain and change that layer first. The goal is not to control every automated decision. It is to make sure automation is learning from, and being judged by, the same definition of value your business uses.
