Tag: Ad Control

How to Manage Google Ads Video Frequency Across Campaigns

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

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

Campaign-level frequency can hide account-level saturation

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

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

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

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

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

Choose between broader reach and managed repetition

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

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

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

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

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

Build a campaign group around one coherent job

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

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

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

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

Measure delivery changes, not just cleaner reporting

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

Evaluate the beta in three layers:

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

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

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

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

Key takeaways

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

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

References

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

October 6, 2026

Google Ads Brand Controls and PMax Creative Testing

Your business name does not exactly match your landing-page domain, and the creative inside your Performance Max campaign needs work. Those may look like two versions of the same branding problem, but Google Ads handles them very differently.

The clean way through is to make two separate decisions. First, establish whether you are entitled to present the brand name on that domain. Then test how the brand should speak and look. That sequence protects brand accuracy while giving you usable evidence about creative performance.

Key takeaways

A business name can differ from the destination domain in limited cases, but the name must accurately represent the advertiser’s recognized name or brand.
You must have a verifiable, direct relationship with the domain owner, and your products or services must be offered directly on the destination website.
Third-party resellers, independent booking intermediaries, affiliate distributors, and secondary sellers cannot use the exception to present another company’s standalone brand as their own business name.
Performance Max asset-group experiments can compare changes to headlines, descriptions, images, and videos without immediately replacing the existing creative.
Once an experiment starts, the asset group cannot be changed while the test is running. Decide what you are testing and secure stakeholder approval before launch.
Identity approval and creative performance are separate gates. Passing one does not answer the other.

Separate brand identity from creative performance

Start by naming the decision in front of you. A business-name review asks whether the advertiser is representing itself truthfully. A Performance Max experiment asks whether a creative change improves the campaign outcome. Treating both as generic ad optimization makes it easy to use performance data to excuse an identity problem or to mistake an approved name for effective creative.

Decision	Question to answer	Evidence that matters	Common mistake
Business-name eligibility	Are you entitled to advertise under this name on this destination?	The recognized brand identity, the relationship with the domain owner, and direct availability of the advertised offering	Assuming a familiar brand name can be used merely because you sell or arrange access to it
Creative experiment	Does a defined asset change improve the selected campaign outcome?	A controlled comparison between the existing asset group and a purposeful variant	Changing several unrelated elements and then attributing the result to one asset

The order matters. If your identity is not eligible, better imagery or copy will not fix that underlying issue. If the identity is eligible, approval still tells you nothing about whether a new headline, video, or visual direction will perform better.

Audit a mismatched business name before resubmitting it

A difference between the business name and destination domain is no longer automatically disqualifying for every advertiser. The flexibility is narrow, however. It applies when the name accurately reflects the advertiser’s recognized identity and Google can verify the advertiser’s direct connection to the website. Use the following audit before relying on the exception.

Write down the exact business name you want displayed. Do not evaluate a shortened, expanded, or idealized version; assess the actual asset you intend to submit.
Compare that name with the recognized advertiser or brand. The name should identify your business accurately, not borrow recognition from a company whose offering you happen to distribute.
Identify the destination domain owner and your direct relationship with that owner. The updated rules require that relationship to be verifiable, so an informal association or a commercial link several steps removed should not be treated as sufficient.
Confirm that your own products or services are offered directly on the destination website. A page that merely refers visitors elsewhere is not the same arrangement as a business offering its services at the destination.
Classify your role honestly. If you are a third-party reseller, independent booking intermediary, affiliate distributor, or secondary seller, you do not qualify to use the standalone name of the product, service, or property as though it were your own business name.

These conditions are the practical boundary around the more flexible relationship between a business name and its destination domain. The change helps legitimate brands with complex domain arrangements; it is not permission for intermediaries to make themselves look like the underlying brand.

Create a short identity record for every affected account. Record the submitted business name, destination domain, domain owner, advertiser-domain relationship, the offering available at the destination, and whether the advertiser acts as the direct provider or an intermediary. This gives whoever handles an approval problem a factual map instead of a collection of assumptions.

If the account previously received business-name asset disapprovals, revisit the rejection against each condition rather than simply resubmitting the same asset. A mismatch may now be acceptable, but only when all the qualifying facts line up. If they do not, use an identity that truthfully describes the advertising business instead of trying to force the better-known brand name through review.

Design a Performance Max test around one creative claim

Performance Max asset-group experiments give you a cleaner alternative to replacing creative and comparing the weeks before and after. A before-and-after result can move because the creative changed, but it can also move because the surrounding conditions changed. A concurrent experiment provides a more controlled answer to the question you actually care about: did this creative approach contribute to a different result?

The feature is rolling out, so first confirm that asset-group experimentation is available in the account you are managing. Where it is available, build the test in this order:

Write a single hypothesis. Examples supported by the available controls include user-generated-content-style creative versus polished brand creative, one messaging approach versus another, a different image style, or the effect of adding or changing video.
Define the baseline. Preserve the current asset group as the control so the proposed direction has something meaningful to beat.
Build a variant that reflects the hypothesis. Performance Max experiments can cover headlines, descriptions, images, and videos, but access to several asset types is not a reason to change all of them at once.
Select the decision signal before launch. Use the outcome tied to the campaign’s real objective, and decide in advance what secondary effects would make a nominal improvement unacceptable.
Get copy, design, legal, and brand approvals before starting. This is operationally important because the asset group cannot be changed after the experiment begins.
Record exactly what differs between control and variant. If the result surprises you later, this record determines what you can reasonably claim to have learned.

The strongest test changes one creative idea, even when that idea requires several coordinated assets. For example, a test of a user-generated-content-style concept may reasonably involve a related image, video, headline, and description. The resulting conclusion applies to that package. It does not prove that the video alone, the wording alone, or the image alone caused the difference.

A weaker test combines unrelated edits: a new value proposition, a new visual style, different calls to action, and a new video at the same time. That variant can still win or lose, but it leaves you unable to identify which decision should carry into the next asset group.

Turn the experiment result into a bounded decision

An asset-group experiment improves creative evidence without making Performance Max fully transparent. Google’s automation still determines how eligible assets are assembled and served. Interpret the result as evidence about the tested change within that automated environment, not as a universal verdict on the concept in every campaign, audience, or channel.

If the variant improves the preselected decision signal without causing an unacceptable tradeoff, adopt the winning direction and document what changed.
If the result is mixed, do not choose whichever metric makes the preferred creative look best. Return to the objective selected before launch and use the secondary results to frame a narrower follow-up question.
If the experiment does not establish a useful difference, do not rewrite the result as proof that the two approaches are identical. It means this test did not give you a sufficient reason to replace the baseline.
If the variant changed several asset types, describe the winner as a creative package. Run a narrower follow-up experiment if you need to isolate the contribution of an image, message, or video.
If the setup no longer represents the original hypothesis, treat the outcome cautiously. A controlled test is valuable because its boundaries are clear; once those boundaries become ambiguous, so does the lesson.

Keep a compact experiment record with the hypothesis, control, variant, exact asset differences, primary decision signal, relevant secondary signals, result, decision, and next question. This prevents the same creative debate from restarting when a new stakeholder joins the account and stops a qualified finding from turning into an unsupported rule.

Use a two-gate workflow for every brand change

A workable operating model has an identity gate followed by an evidence gate. The identity gate confirms that the advertiser can legitimately use the business name at the destination. The evidence gate determines whether a particular creative expression deserves to replace the current one.

Resolve the business-name and domain relationship before developing multiple creative variants around that identity.
Save the approved name, destination, and direct-provider status in the account’s identity record.
Translate the next creative disagreement into one testable claim.
Prepare and approve every required asset before the experiment begins.
Run the asset-group experiment without introducing additional changes to the test group.
Apply only the conclusion the test supports, then write the next question instead of declaring the creative problem solved.

Start with the account most exposed to a name-domain mismatch. Complete the identity audit, resolve any weak condition, and only then choose one Performance Max asset group for a tightly framed creative experiment. That gives your next change both a defensible brand foundation and a measurable reason to exist.

References

October 2, 2026

Google Ad-Tech Antitrust Litigation: A Publisher’s Playbook

If you depend on programmatic advertising revenue, the Google ad-tech litigation creates a planning problem before it creates a financial opportunity. The wrong response is to put a recovery into your forecast or make a rushed platform change. The useful response is to determine whether your business touches the surviving claims and whether you can still explain, with records, how money moved through your ad stack.

Major claims remain alive, but that is not the same as a finding that every publisher was harmed. Your immediate job is to separate what the court has established, what the publishers still must prove, and what evidence your own legal and finance teams would need to evaluate any potential exposure or recovery.

The ruling preserved a path, not a payout

On Sept. 30, U.S. District Judge P. Kevin Castel issued an 88-page opinion denying Google’s requests for summary judgment on the publishers’ principal ad-tech claims. He also declined to exclude important expert testimony supporting their damages cases.

Summary judgment is a pretrial mechanism for resolving claims that do not require a trial to decide. Denying it means Google did not persuade the court to dispose of the principal claims on the pretrial record. It does not mean the publishers have won a damages award, that every expert assumption has been accepted, or that every remaining dispute will necessarily reach trial.

What the decision did	What it did not do
Kept the publishers’ principal ad-tech claims in the litigation	Decide how much, if anything, Google owes
Allowed key damages testimony to remain in the case	Adopt the experts’ estimates as proven losses
Preserved claims involving the AdX publisher class and Mikula Web Solutions	Preserve every claim brought by every plaintiff
Prevented Google from relitigating certain findings from the separate Virginia case	Establish injury and damages for each publisher automatically

The mixed outcome matters. Castel ruled for Google on the New York General Business Law claims brought by Gannett and Daily Mail, on claims brought by The Progressive, and on Inform’s federal antitrust claims. Claims involving the AdX publisher class and Mikula Web Solutions were allowed to continue. A headline saying publishers cleared a major hurdle is accurate, but it is too broad to answer whether a particular company, legal theory, or alleged loss remains in play.

When you brief executives, use a claim matrix rather than a win-or-loss label. Give each claimant and legal theory its own row, then record whether the claim survived, which issues are already established, which issues remain disputed, and what procedural event comes next. That prevents a partial ruling from turning into an inaccurate company-wide assumption.

The economic dispute sits between inventory and demand

An abstract publisher page and advertiser nodes connected through a layered auction system carrying metallic tokens.

A publisher ad server manages advertising inventory and helps decide which demand source can fill an opportunity. An exchange provides a marketplace in which demand can compete for that inventory. When one company controls important infrastructure on both sides of that handoff, the rules connecting the products can affect which demand participates, how an auction operates, what fees are charged, and what reaches the publisher.

That connection is central here. The publishers allege that Google’s control over its publisher ad server and the AdX exchange, combined with practices governing ad auctions, reduced publisher revenue or produced excessive fees. Google contests those allegations. The disputed question is therefore not simply whether publishers used Google technology; it is whether challenged conduct caused a measurable economic injury.

The litigation also draws on the federal government’s separate ad-tech case in Virginia. Castel had already determined that Google could not relitigate certain findings from that proceeding, including the finding that Google unlawfully tied its publisher ad server to AdX. That gives the publisher plaintiffs an important established point, but it does not calculate the consequences for a particular publisher. Injury, causation, and damages still have to be connected to the conduct at issue.

For your business, the practical unit of analysis is an ad-monetization dependency map. It should show:

The legal entities, sites, applications, and business units that sold digital inventory.
The publisher ad server and exchanges used during each relevant period, including migrations and material configuration changes.
Which demand paths were direct, exchange-based, mediated, or otherwise dependent on the publisher ad server.
The contracts, amendments, fee schedules, invoices, and reporting accounts associated with each path.
The identifiers that connect domains, properties, accounts, reports, and payment records across systems.
The employees or vendors who understood auction configuration, yield management, billing, and reporting definitions at the time.

This map does not establish that you belong to a class or have a claim. It gives counsel the facts needed to assess those questions without relying on institutional memory. It also reveals whether a change in revenue coincided with traffic, inventory, auction, fee, or platform changes instead of treating every decline as one undifferentiated problem.

Do not mistake the damages estimates for recoverable amounts

The public figures are large because they are damages estimates prepared by experts retained by the plaintiffs. They are not court-awarded compensation:

Claimant or group	Plaintiffs’ expert estimate
Gannett	Roughly $901 million
Daily Mail	$600 million
Publisher class	$1.72 billion through March 31, 2024

The plaintiffs claim additional class damages after March 31, 2024, but no additional amount was provided. Do not extend the $1.72 billion estimate beyond that date, apply it as a percentage of industry revenue, or use it to derive a hypothetical recovery for your company. None of those calculations is supported by the disclosed figures.

An expert’s testimony can remain admissible while its assumptions, method, causal reasoning, and conclusions remain disputed. The publishers still need to prove that the challenged conduct injured them and that the requested damages are attributable to that conduct. Google can continue contesting those points.

Your finance team should therefore treat the amounts as allegations supported by the plaintiffs’ models, not as receivables or operating income. If you need an internal scenario, build it in layers:

Use zero recovery as the operating baseline unless legal and accounting advisers determine otherwise.
Ask counsel whether the relevant legal entity, products, time periods, and transactions could fall within a surviving claim or class.
Identify which revenue, fee, and auction records could support or contradict economic injury.
Document every assumption in any contingent scenario, including eligibility, time boundaries, allocation method, legal costs, and uncertainty.
Keep the scenario outside normal performance targets so an unresolved lawsuit does not distort hiring, content, or technology decisions.

The same restraint applies to vendor decisions. A surviving antitrust claim is not proof that your current contract is invalid, that a migration will improve yield, or that another stack will produce a particular result. Evaluate a change using your own fees, demand access, reporting quality, operational cost, and measured auction outcomes.

Build a counsel-led evidence pack while the systems are identifiable

An overhead view of storage drives, blank records, archive envelopes, and a magnifying glass arranged as an evidence pack.

This is an operational preparation checklist, not a determination that your company is part of the litigation or subject to a legal-hold obligation. If the surviving claims may be relevant to your business, ask qualified antitrust or litigation counsel to assess eligibility and preservation duties. Do that before changing retention policies or launching a broad data collection.

Create a system inventory. Record each ad server, exchange, reporting interface, billing system, data warehouse, and archive, along with its owner and available date range.
Preserve the commercial record. Locate contracts, order forms, amendments, invoices, payment statements, fee disclosures, account notices, and documents explaining platform migrations or material configuration changes.
Preserve the operational record. Identify ordinary-course auction reports, revenue reports, configuration histories, demand-partner lists, account identifiers, and metric definitions. Record where a field was renamed or calculated differently over time.
Build a dated chronology. Align platform changes with shifts in impressions, fill, auction participation, reported fees, and net publisher revenue. A chronology makes alternative explanations visible instead of assuming every movement came from the challenged conduct.
Reconcile money to activity. Where the data permits, connect inventory and auction records to invoices and net payments. Record unexplained gaps rather than backfilling them with estimates.
Document limitations. Note missing periods, expired logs, acquired properties, changed account IDs, inconsistent currencies, and reports that cannot be reproduced. A known limitation is more useful than false precision.
Control access. Keep the working set limited to the people who need it, and follow counsel’s directions for preservation, privilege, privacy, security, and collection scope.

Do not delete, rewrite, or normalize potentially relevant originals after counsel identifies a preservation obligation. At the same time, do not collect extra user-level information merely because it might be available. An indiscriminate collection can create privacy and security exposure without helping establish publisher-level fees or revenue. Preserve what is relevant, document what each field means, and let counsel define the defensible scope.

SEO, content, and audience teams also have a role. Keep acquisition performance separate from monetization performance in your reporting:

Acquisition: visits or sessions from organic search, AI-search referrals, direct traffic, social platforms, and other channels.
Inventory: ad opportunities, eligible impressions, ad load, and fill-related measures available in your systems.
Monetization: auction outcomes, disclosed fees, and net publisher revenue, with the governing metric definitions attached.

Traffic can improve while monetization weakens, or monetization can improve while traffic falls. A single blended revenue-per-session figure hides that distinction. Separating the layers helps you evaluate content performance accurately now and gives legal and financial reviewers a cleaner record if they later need to isolate alleged ad-tech harm.

Key takeaways for publisher teams

The Sept. 30 decision kept principal Google ad-tech claims alive and preserved key expert testimony; it did not award damages.
Google cannot relitigate certain findings from the separate Virginia case, including unlawful tying of its publisher ad server to AdX, but publisher-specific injury and damages still require proof.
The estimates of roughly $901 million for Gannett, $600 million for Daily Mail, and $1.72 billion for the publisher class are plaintiffs’ expert estimates, not payouts.
The result varies by claimant and legal theory. Several claims were resolved for Google, while claims involving the AdX publisher class and Mikula Web Solutions continue.
Your defensible next step is a counsel-led review of eligibility, systems, contracts, fees, and retained data—not an assumed recovery or an emergency platform migration.

Within your next reporting cycle, produce a one-page ad-stack dependency map and assign owners for the supporting contracts, reports, and payment records. Have counsel decide whether a deeper eligibility or preservation review is warranted. That gives you a decision-ready file without pretending the litigation has already produced money for publishers.

References

Search Engine Land — Publishers’ Google ad-tech antitrust claims clear a major legal hurdle

October 2, 2026

Google Ads Automation and Localization Without Losing Control

If you manage Google Ads, your website is becoming part of the campaign-building system. An offer published on a page may become a promotion asset, while an existing Search campaign may become the template for a new language and market.

That can remove hours of repetitive setup. It can also scale an expired discount, awkward translation or unsuitable budget before anyone notices. The right response is not to reject automation. It is to put a clear approval boundary between what Google can generate and what your business is prepared to promise and spend.

Separate the two automations before setting policy

Automated promotions and campaign localization solve different problems. They also fail differently. Treating them as one generic AI feature makes it harder to assign the right reviewer and control.

Workflow	What Google creates	Initial scope	Primary control
Automated promotions	A promotion asset based on an eligible offer found on your website	Search and Performance Max campaigns with linked location assets and no promotion asset already attached	The account-level Automated Promotions setting, followed by a review of assets that serve
AI campaign localization	A new, independent campaign with localized ads, assets and keywords	Eligible U.S. English Search campaigns translated into supported languages and markets during the beta	Language, landing-page and commercial review before the localized campaign goes live

The promotion workflow extracts a commercial claim that already exists. The localization workflow transforms an existing campaign for a different audience. The first can misstate an offer; the second can reproduce a sound campaign in a market where its language, intent or economics no longer fit.

A useful account policy is simple: automation may identify, translate and assemble; a named owner must still authorize the promise, the audience and the spend.

Audit your website before automated promotions serve

A review team inspects a website page for expired dates, mismatched prices, unavailable products, and broken links before automation.

Starting Oct. 12, eligible advertisers may be enrolled automatically. That changes the default risk. Doing nothing is no longer necessarily the same as declining the feature.

Your first decision is whether the account should participate at all. Keep it enabled when public offers are current, clearly qualified and consistently honored online and in stores. Disable it when promotions require case-by-case approval, depend on complex eligibility rules or frequently remain visible after they expire.

Open the account’s automated asset settings and find Automated Promotions. Record whether it is on or off and who approved that choice.
Inventory public pages that mention discounts, coupon codes, bundles, free items or limited offers. Include store pages when location assets connect campaigns to physical locations.
Make each offer understandable without surrounding marketing copy. State what qualifies, what the customer receives and, where applicable, when and where the offer is valid.
Reconcile the page with the real transaction. Pricing, eligibility and brand wording should agree with the checkout flow, sales process and in-store terms.
After an automated promotion begins serving, inspect it in the Assets section. An asset that has not received impressions will not appear there, so an empty view does not prove that the account is opted out.

That last distinction matters. The setting tells you whether Google has permission to create automated promotions. The Assets view tells you what has actually accumulated impressions. Check both rather than using one as a proxy for the other.

If you opt out, use the explicit account-level control. Do not rely on incomplete pages, ambiguous offer wording or the presence of a manually managed asset as an informal safeguard. Automated Promotions can be turned off in automated asset settings, which gives the account team an auditable decision instead of an accidental outcome.

Launch localization as a new market, not a translation task

The localization beta can turn one eligible Search campaign into a separate campaign for another language and location. The original campaign remains unchanged. That independence is useful, but it does not make the new campaign commercially ready.

Choose a parent campaign worth reproducing. Fix known targeting, messaging or landing-page problems before translation, or the new campaign will begin with the same structural weaknesses.
Select the exact target language and location. A language label is not a market strategy: Spanish for Spain and Spanish for Latin America and the Caribbean are available as distinct variants in the beta.
Give the AI explicit language rules. Tell it which brand names, product names and technical terms must remain unchanged, and specify whether the voice should be formal or conversational.
Review every campaign component, not just the headlines. The workflow can localize headlines, descriptions, sitelinks, callouts and keywords.
Choose the landing-page method deliberately. You can install a Google-provided JavaScript snippet that dynamically translates page text for visitors from localized ads, or update the campaign URLs to point to pages you already maintain in the target language.
Require a human language and market review. Use the original, localized version and English back-translation shown side by side to check meaning, then ask a fluent reviewer to assess naturalness, search intent, cultural fit and brand terminology.
Reset the economics. Budgets and bids are copied from the original campaign without automatic currency conversion or exchange-rate adjustment. Do not approve launch merely because those fields are populated.

The landing-page choice deserves particular care. Dynamic translation is a practical route when the underlying offer and customer journey are genuinely the same. A maintained local page is the stronger option when prices, availability, delivery terms, legal wording or conversion steps differ by market. In either case, review the page as the visitor will see it after clicking the localized ad.

Images also need a separate check. When an image contains text, the workflow can remove the original wording and use the translation as supplemental text assets. Do not assume the output will simply be the same image with perfectly replaced lettering. Preview the complete creative combination and confirm that the visual still makes sense without its original embedded message.

The beta supports U.S. English Search campaigns localized into Dutch, French, Canadian French, German, Italian, Polish, Brazilian Portuguese, European Portuguese, Spanish for Spain and Spanish for Latin America and the Caribbean. Google plans to add languages by the end of 2026 and later extend localization to Performance Max. Treat that as a roadmap, not as a capability your current launch can depend on.

Use one release gate for assets, language and money

Three reviewers check advertising assets, localized language elements, and budget tokens at a single campaign release gate.

The most reliable control is a short release record shared by the website owner, campaign manager and market reviewer. It should force a yes-or-no decision on the places where automation cannot judge your business obligations.

Commercial truth: Is the promoted price or benefit currently available, and will every customer who meets the stated conditions receive it?
Qualification: Are exclusions, dates and location restrictions consistent across the ad asset, landing page, checkout or sales process, and physical store where relevant?
Language: Has a fluent reviewer approved the customer-facing wording rather than relying only on the English back-translation?
Search intent: Do the localized keywords represent how people in that market look for the offer, not merely a literal rendering of the parent keywords?
Landing experience: Does the visitor remain in the intended language through the meaningful conversion steps?
Economics: Have the copied budget and bids been reviewed for the target market instead of accepted as inherited defaults?
Ownership: Is one person responsible for pausing the asset or campaign when an offer, page or market condition changes?

Use event-based reviews rather than a vague instruction to monitor regularly. Reopen the record when an offer starts or ends, a price or landing page changes, an automated asset first receives impressions, a new localized campaign is generated, or its budget and bids are changed.

After launch, judge the localized campaign on its own market economics. It is an independent campaign, so the parent campaign’s historical success is context, not proof. For automated promotions, compare the served asset with the live offer page and the transaction customers actually receive. The purpose of monitoring is not just to catch strange wording; it is to catch a broken commercial promise.

Key takeaways

Check the account-level Automated Promotions setting before Oct. 12; eligible advertisers may be enrolled without making an affirmative choice.
Treat every public offer page as potential campaign input, especially when Search or Performance Max campaigns use linked location assets.
Do not use an empty Assets view as proof that automation is disabled; unserved assets do not appear there.
Review localized campaigns as independent market launches, including keywords, creative, landing pages, language quality and cultural fit.
Replace copied budgets and bids with a deliberate market decision because the localization workflow does not perform currency or exchange-rate adjustments.

Your next step is small and concrete: open one eligible account, document its automation setting, then choose one live offer and one possible target market to run through the release gate. That will expose missing ownership and inconsistent inputs before automation exposes them to customers.

References

October 2, 2026

How to Control Paid Search Placement and Ad Presentation

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

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

Treat placement and presentation as separate control planes

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

Those questions require different actions:

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

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

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

Turn content exclusions into an enforceable brand policy

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

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

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

Build the exclusion list in six steps

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

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

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

Build sitelinks that survive changes in visual treatment

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

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

Make every sitelink understandable on its own

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

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

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

Diagnose performance shifts before changing the campaign

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

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

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

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

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

Key takeaways

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

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

References

September 28, 2026

Paid Search APIs: A Control Plan for PMax and Targeting

Your paid search stack has more levers, but a longer settings list is not a control strategy. Your immediate job is to decide which signals belong in reporting, which controls enforce real business constraints, and which customer data should never enter an upload pipeline without an eligibility check.

Handled carefully, the Microsoft Advertising and Google Ads APIs can help you trace intent to destinations, constrain Performance Max where the economics demand it, strengthen audience inputs, and identify bidding settings that limit auction access. The useful unit is not the endpoint. It is a closed loop: observe, diagnose, authorize, change, and verify.

Build a control plane before you automate campaign changes

A paid search integration should separate evidence from action. Reports, benchmarks, and recommendations tell you what may deserve attention. They do not automatically tell you which change is safe, profitable, or permitted.

Organize the integration into four stages:

Observe: retrieve delivery evidence, performance metrics, recommendations, and the current effective settings.
Diagnose: classify the issue as a message mismatch, destination mismatch, targeting problem, measurement defect, auction-access constraint, or genuine business restriction.
Authorize: apply an approval rule that matches the risk. A validated tracking-parameter correction is not the same decision as excluding an entire device category or changing a bidding target.
Execute and verify: write the smallest eligible change, retrieve the effective setting again, and record whether the platform accepted it.

Keep read jobs and campaign-mutation jobs separate where your architecture permits it. At minimum, every write operation should support a dry run that shows the current value, proposed value, object scope, and affected IDs before money-moving settings change.

Your change record should capture the platform, account, campaign or asset-group ID, scope, previous value, proposed value, reason, requester, approval status, execution result, and retrieval time. Add de-duplication in your own worker so a retry cannot apply the same logical operation twice. That record becomes essential when an automated campaign behaves differently and you need to distinguish a platform decision from a change your system made.

Turn search-term-to-page evidence into a repair queue

An analyst traces glowing search-signal streams to model landing pages and sorts mismatches into repair trays.

Microsoft Advertising’s Search Term Landing Page Report connects a search term, the delivered headline, the final URL, and performance metrics in the same reporting view. That closes an important diagnostic gap: you can inspect the promise a person saw and the destination that had to fulfill it.

Do not reduce this to a list of expensive search terms. Build a mismatch workflow that preserves the full path:

Store the raw evidence. Retain the search term, delivered headline, final URL, campaign identifiers, and associated metrics. Do not substitute the headline you expected to serve for the headline that was actually delivered.
Create a normalized destination key. Keep the raw URL for auditing, then create a second field that removes only parameters you have confirmed do not alter page content. A parameter that controls localization, product selection, or page state is not disposable tracking noise.
Score three separate relationships. Evaluate search term to headline, headline to landing page, and search term to landing page. A relevant headline can hide a poor destination, while an acceptable page can still be introduced by the wrong promise.
Join relevance to outcomes. A semantic mismatch deserves inspection, but performance data determines its operational priority. A high-volume routing defect and an isolated ambiguous query should not enter the same queue with the same urgency.
Assign the repair to the correct layer. Change the eligible ad messaging when the promise is wrong, adjust routing when the destination is wrong, and revise the page when it fails to answer the intent it legitimately targets.

Suppose a term clearly asks about pricing, the delivered headline promises pricing information, and the click reaches a generic homepage that never addresses price. The weak link is the destination. Rewriting the headline may reduce the visible contradiction, but it does not satisfy the underlying intent. Your queue should make that distinction explicit.

SEO, AEO, and GEO teams can use the same queue to prioritize clearer on-page answers. Paid query evidence can show that demand exists and reveal the language people use, but it does not prove that a page will rank organically or be cited by an AI system. Improve the visible answer first, then describe that content accurately with metadata and structured data. Schema cannot repair information the page does not contain.

Model PMax controls by platform, object, and scope

Performance Max is not one uniform control surface. Microsoft is adding campaign-level device exclusions, while Google Ads API v25.2 exposes URL configuration at the asset-group level and a draft-based migration path from Smart campaigns. Treating all three capabilities as a generic PMax setting will create faulty assumptions in your interface and automation.

Capability	Scope	What the API permits	How to use it safely
Microsoft Advertising device exclusions	Campaign	Exclude Computers, Smartphones, or Tablets from a PMax campaign	Use only after confirming that the device itself creates a durable business constraint, rather than masking a page, tracking, consent, or attribution defect
Google Ads PMax URL configuration	Asset group	Configure tracking templates, custom URL parameters, and final URL suffixes	Keep routing and measurement rules aligned with the asset group, and test the resolved URL before activation
Google Smart-to-PMax generation	Campaign draft workflow	Generate a PMax draft from an existing Smart campaign	Treat the generated object as a reviewable draft, not as authorization to launch it

Your internal model should include at least platform, control type, scope type, scope ID, requested value, effective value, and business rationale. The interface should state plainly whether a control applies to a campaign, an asset group, or a migration draft. Scope must not be inferred from a label such as PMax control.

Device exclusion is the highest-consequence control in this set because it removes eligible reach. Before excluding a device, verify that the apparent weakness is not caused by a slow or unusable landing experience, broken conversion tracking, a consent-flow difference, or cross-device attribution. If the problem can be repaired, fix it. If the device violates a stable operating rule, document that rule and exclude it at the campaign scope the Microsoft API actually supports.

Google’s asset-group URL controls solve a different problem. They let you attach tracking and URL information closer to the asset grouping that uses it. Validate the fully resolved destination, preserve parameters that affect content, and test that your analytics system receives the expected values. A syntactically accepted suffix can still produce a bad measurement or routing result when combined with the base URL.

A generated PMax draft also needs a deliberate comparison with the campaign it is replacing. Review destinations and tracking, conversion goals, geography, bidding and budget assumptions, creative assets, audience inputs, and exclusions before approval. Draft generation reduces construction work; it does not transfer accountability to the API.

Google Ads API v25.2 is a minor release without breaking changes, but integrations still need updated client libraries and code to use its additions. It is scheduled to remain supported until August 2027, so record the API version behind every capability flag and plan the next upgrade before support ends.

Separate audience usefulness from permission to use the data

Abstract customer-data tokens pass through separate usefulness and permission gates before entering a campaign system.

Microsoft’s API support for LinkedIn segment targeting can add professional audience information to programmatic campaign management. That can be useful for B2B offers, but a segment name is still a targeting hypothesis, not proof of buying intent.

For every segment, record the business question it represents, the campaign where it is eligible, and the result you expect it to influence. Your integration should also expose how the platform treats that audience object in the selected campaign context: as a reach restriction, observation layer, or automation input. Do not let a generic audience toggle hide that distinction.

Google Customer Match introduces a more consequential data-governance decision. Advertisers can add an IP address and interaction timestamp to customer data, but both values must be uploaded unhashed. These identifiers are not available for end users in the European Economic Area, United Kingdom, or Switzerland, so geographic eligibility has to be enforced before the export reaches Google.

Build that upload pipeline to fail closed:

Check eligibility at the record level. If your collection system cannot reliably establish that the user is outside the restricted regions, omit the IP-address field for that record.
Verify notice and consent before enabling the fields. The expanded matching options require appropriate collection disclosures and consent controls. Have the privacy or legal owner responsible for your markets approve the rule before activation.
Use the required file format. Customer Match files can contain eight columns, and Google requires specific English-language headers, including User IP address and User Interaction timestamp. Hashing these two fields anyway does not satisfy the specified upload format.
Limit exposure. Restrict access to the unhashed export, prevent raw values from appearing in debug logs, and remove temporary files according to your approved retention policy.
Log decisions rather than identifiers. Record the policy version, eligible and excluded row counts, upload result, and failure reason without copying IP addresses into the operational audit trail.

This is one place where a larger matchable audience is not automatically a better outcome. If the regional gate, collection record, or disclosure is uncertain, omit the new identifiers and use an already approved matching path. The downside of a smaller audience is preferable to transferring data you were not authorized to use.

Use benchmarks and bidding recommendations as questions, not commands

Google Ads API v25.2 can return competitive benchmark percentile tiers through BenchmarksService, including comparison with all advertisers and optional category filters. A percentile supplies market context. It is not a profitability target.

Store the comparator and category filter beside the percentile. Without them, a dashboard preserves the number but loses the population that gives it meaning. Also keep the advertiser’s own absolute outcome nearby. A relative position cannot tell you whether a campaign meets its allowable acquisition cost, margin requirement, lead-quality standard, or revenue target.

The same discipline applies to Google’s recommendations that flag Target CPA or Target ROAS settings that may be too restrictive for a campaign to enter auctions. The recommendation diagnoses possible auction-access friction. It does not establish that loosening the target will produce economically acceptable conversions.

Before acting on that recommendation, verify the conversion definition and tracking, calculate the CPA or ROAS boundary your economics can support, decide whether the actual problem is limited auction access or weak post-click performance, and define the acceptable change before editing the target. Store whether the recommendation was accepted, modified, or declined and why. Do not make this recommendation self-executing merely because the API makes it available.

Key takeaways

Separate API observation from mutation, and preserve a before-and-after record for every campaign write.
Evaluate search term, delivered headline, and final landing page as three connected relationships, not as independent report columns.
Represent PMax controls at their real scope: Microsoft device exclusions are campaign-level, while Google’s new URL controls are asset-group-level.
Generate a PMax draft to reduce setup work, then review it with the same standards as a manually assembled campaign.
Block restricted or uncertain Customer Match records before export; IP addresses and timestamps require an unhashed, region-aware pipeline.
Use benchmark percentiles and bidding recommendations to frame an investigation, not to replace your own economic constraints.

For your next integration release, keep the scope small and verifiable: add one reporting path that exposes query-to-page mismatches, one write guardrail that respects the platform’s actual control scope, and one hard eligibility gate around customer-data uploads. Expand automation only after those three paths produce auditable results.

References

September 25, 2026

Google Ad Tech Antitrust Oversight: A Publisher Action Plan

If you publish content and depend on programmatic advertising, the practical question is whether you can reach AdX demand without centering Google’s publisher ad server in your stack. A federal court has ordered that path to be opened. Whether it improves your revenue, control, or costs still has to be proved in your own environment.

Google’s ad tech business is not being broken apart. The remedy instead combines interoperability requirements, data sharing, restrictions on lock-in, and six years of court supervision. That gives you a reason to test alternatives, but not a reason to migrate blindly.

What the court changed in Google’s ad tech stack

Separate ad server and advertising exchange modules are connected by multiple open pathways beneath a balance scale.

U.S. District Judge Leonie Brinkema found that Google had monopolized the publisher ad-server and ad-exchange markets. The remedy focuses on loosening the connections between those two parts of the advertising supply chain.

Court-ordered change	Decision it may enable	What you need to verify
Rival publisher ad servers must be able to access AdX real-time bids	Keep or adopt a non-Google ad server while considering AdX demand	Supported inventory, bid timing, implementation requirements, reporting, and fees
Publishers using Google’s ad server cannot be required to use AdX	Evaluate the ad server and exchange as separate purchases	Whether contracts, defaults, incentives, or workflows still make separation costly
Practices that locked publishers into Google’s tools must end	Move components of the stack without replacing everything at once	Migration support, termination terms, data portability, and operational dependencies
Google must meet new data-sharing requirements	Compare auction behavior and performance with better information	Fields supplied, granularity, delivery cadence, retention, and export rights

The court declined to force a sale of AdX or another ad tech component because it considered structural remedies unnecessary and impractical. It concluded that behavioral restrictions could restore competition and stop a return to the conduct at issue. That is a meaningful distinction: the remedy changes how Google must operate, not who owns the infrastructure.

Google must also appoint an antitrust compliance monitor. The remedies remain in force for six years, rather than the 15 years sought by federal and state enforcers, and the monitor has less authority than the Justice Department requested. You should therefore treat this as a supervised window for competition, not a permanent guarantee that every market friction will disappear.

Key takeaways for publishers and advertising teams

Interoperability is the remedy, not the business outcome. Access to AdX bids can make another ad server more viable, but it does not guarantee higher yield, lower fees, or easier operations.
The most immediate opportunity is procurement leverage. You can ask vendors to price and document the ad server, exchange access, data access, and migration support separately.
A full-stack replacement should not be your first test. Start with a reversible inventory segment so that an integration problem cannot put all advertising revenue at risk.
Net performance matters more than the headline bid. Measure revenue after fees alongside fill, latency, reporting discrepancies, and staff time.
This is an ad tech remedy, not a search update. It does not by itself change organic rankings, indexing, structured data, AI citations, or eligibility for AI-generated search features.

Turn the remedy into a controlled testing plan

A publishing team compares two isolated ad delivery setups on a controlled testing bench.

The order creates optionality. Your job is to determine whether that optionality produces a better result for your inventory. Build the evaluation before a contract renewal or migration deadline leaves you with only one practical choice.

Record a baseline with stable definitions. Capture eligible impressions, bid participation, fill, gross revenue, net revenue after identifiable fees, page latency, reporting discrepancies, and operational hours. Keep the calculation method fixed so a vendor cannot appear better merely because it defines an impression or fee differently.
Map the dependencies around the publisher ad server. List exchange connections, direct campaigns, identity tools, consent signals, creative review, forecasting, billing, analytics exports, and any custom automation. A component can be contractually separable while remaining expensive to replace because several workflows depend on it.
Define success and failure before seeing results. Decide which metrics cannot deteriorate, which improvements would justify migration work, and which implementation costs count against the result. Include rollback triggers for material revenue loss, latency increases, missing consent signals, or inconsistent reporting.
Request the new access path in writing. Ask each vendor to describe exactly how AdX real-time bids are passed to a rival publisher ad server, what inventory is supported, which data accompanies the bid, and which limitations remain. A statement that access is available is not an implementation specification.
Run a reversible pilot. Use a defined inventory cohort that is large enough to evaluate but small enough to protect the wider business. Compare similar traffic and account for known changes in geography, device mix, content, and demand conditions. Do not move the entire stack on the strength of a sales demonstration.
Evaluate the operating cost as well as auction results. Count troubleshooting, reconciliation, manual trafficking, vendor coordination, and delayed reporting. A small revenue gain can disappear when the alternative requires substantially more staff time.
Carry verified findings into renewal negotiations. Separate requests for ad serving, exchange demand, data, support, and migration. Preserve export and termination rights so that a successful pilot can become a real choice rather than a temporary experiment.

If a proposed change affects termination rights, exclusivity, data ownership, or material revenue commitments, have qualified counsel review the relevant contract language. The operational goal is to preserve a safe test and a workable exit, not to interpret the antitrust judgment as modifying your individual agreement automatically.

Questions that expose whether access is genuinely usable

The useful question is not simply whether a rival ad server can receive AdX bids. You need to know whether it can do so on terms that support a reliable auction, accurate measurement, and a commercially sensible workflow.

Connectivity and auction behavior

How does the AdX real-time bid reach the rival publisher ad server, and which system makes the final auction decision?
Which inventory formats, account types, devices, and markets are supported?
What technical prerequisites, certifications, minimums, or configuration changes apply?
Which timestamps and identifiers are available for diagnosing bid timing, timeouts, and discrepancies?
What happens during an outage or degraded connection, and can the publisher configure a fallback?
Can the setup be piloted on selected inventory without changing the rest of the stack?

Data, fees, and contractual control

Which auction and reporting fields will be shared, at what level of detail, and how quickly?
Can the publisher export the data in a reusable format, and what retention limits apply?
Which fees are charged by the exchange, ad server, integration provider, or reseller?
Are support, migration, reconciliation, or data access billed separately?
Does any discount, default, or bundle make independent selection economically difficult even when it is technically permitted?
What notice, termination, data-return, and transition-assistance terms apply if the test fails?

Put the answers into the test plan and contract rather than leaving them in a presentation. The compliance monitor will oversee Google’s adherence to the final judgment, but that role does not replace your technical acceptance criteria, revenue controls, or vendor accountability.

Keep ad tech oversight separate from search and AI visibility

For SEO, AEO, and GEO teams, the central mistake would be to turn this antitrust remedy into a forecast about organic discovery. The requirements concern Google’s publisher ad server and ad exchange. They do not establish a change to crawling, indexing, ranking systems, AI answers, structured data processing, or citation selection.

Keep two roadmaps. The monetization roadmap should track vendor access, auction data, fees, pilots, and contract flexibility. The search visibility roadmap should continue to track technical accessibility, content quality, entity clarity, structured data, citations, and measurable search or AI referral behavior. A development can matter to the economics of publishing without changing how a page is discovered.

Advertisers on the demand side should be equally precise. Because the remedy targets publisher-side markets, do not assume that a campaign interface, targeting option, or buying workflow has changed. Ask agencies and technology providers to identify the exact supply-path, reporting, or fee change they are relying on before revising a media plan.

Your best next move is deliberately practical: create a one-page performance baseline, map every dependency on the current ad server, and send the implementation questions above to vendors before the next renewal discussion. Six years of oversight creates time to build alternatives, but only measured, contractually usable alternatives give you leverage.

References

Search Engine Land – Google faces six years of court oversight in ad tech antitrust case

September 17, 2026

Google Ads Control Reliability: What Settings Really Do

Your Google Ads campaign has almost stopped serving, but billing, policy status, conversion tracking, negative keywords, locations, devices, and schedules all look clean. This is where the interface can send you in the wrong direction: a visible setting may be active without carrying the authority you assume it has.

Before you raise the budget, remove targeting, or abandon automation, identify what the setting actually promises. Some controls block delivery. Others affect eligibility, establish a bidding constraint, or merely give the system context. The useful question isn’t just, “Is this control enabled?” It is, “What happens when this control conflicts with the auction?”

The control hierarchy: five settings, five different promises

A stream of glowing tokens passes through a barrier, filter, valve, junction, and signal beacon in an isometric delivery pipeline.

A reliable control is not necessarily one that produces the outcome you want. It is one whose behavior you understand well enough to predict what will happen when market conditions, automation, and your instructions disagree.

Control class	Google Ads examples	What it can reliably do	What it cannot promise
Hard restrictions	Negative keywords, brand exclusions, URL exclusions	Constrain whether specified traffic or assets can serve	A negative keyword does not block every query related to the same concept
Opt-outs	AI Max toggle and ad-group-level search-term matching controls	Disable a defined feature or behavior at a particular scope	A complete return to an older campaign state, especially when related controls or migrated features behave differently
Priority rules	Priority for an identical, eligible exact-match keyword	Put one eligible option ahead of another in the selection process	Eligibility, impressions, clicks, or traffic volume
Targets	Target CPA and target ROAS	Constrain the range in which automated bidding tries to operate	The requested conversion volume at any market price
Contextual signals	Performance Max search themes and the keywords, creative, and URLs used by AI Max	Inform expansion and help automation interpret your intent	A deterministic boundary around every query the campaign can enter

The details matter most at the edges. Negative keywords, brand exclusions, and URL exclusions are treated as firm boundaries, but a negative keyword is still a precise instruction about the text you entered. Casing and misspellings are handled, while synonyms and singular or plural forms are not automatically covered. If you add job as a negative, do not assume you have also excluded jobs, career, and employment.

At the other end of the hierarchy, search themes and other contextual signals help the system interpret a campaign. They are useful for direction, but they should not carry a must-not-serve requirement. If a query category would create unacceptable cost or brand exposure, use an applicable exclusion control and verify its coverage instead of relying on a theme or creative cue.

Matching guidelines in AI Brief do not fit neatly into either category. They are presented as guidance and boundaries with previews, but Google has not published a deterministic guarantee or an enforcement rate. Treat them as something to test in live query evidence, not as a substitute for a confirmed exclusion.

When delivery collapses, diagnose authority before changing bids

A campaign that has gone quiet invites broad, hurried edits. That makes the underlying problem harder to isolate and can release more spend than you intended. Use a fixed diagnostic sequence instead.

Mark the beginning of the decline. Identify when impressions, clicks, and conversions changed. You need a date to compare with configuration changes; a current-state screenshot cannot tell you what created the current state.
Check basic eligibility. Review billing, policy status, location and device targeting, schedules, negative conflicts, conversion configuration, and available budget. “Limited by budget” is an eligibility condition, so even a valid priority rule may not operate as you expect when the campaign is constrained.
Use the ad preview result as a symptom. A not-serving result confirms that the campaign is not entering or winning that opportunity. It does not, by itself, identify the responsible control.
Expand change history to the campaign’s full lifetime. A decisive bid-strategy or target change may sit outside a 30-day or 12-month view. A full-lifetime review exposed a consequential change that shorter windows had hidden.
Classify each relevant setting. Label it as a hard restriction, opt-out, priority rule, target, or contextual signal. Then write down the narrow promise it actually makes.
Compare bidding targets with attainable economics. Examine whether recent CPA, CPC, competition, and conversion volume still overlap the target. A target based on an older market can be reasonable when it is chosen and still become restrictive later.
Run one reversible test. Change the suspected constraint without simultaneously rewriting keywords, ads, locations, and budgets. Loosening or removing a bid target can unlock spend quickly, so confirm the campaign budget and conversion measurement before publishing the test.

This sequence separates three very different failures: the campaign is ineligible, the campaign is eligible but constrained by its target, or the campaign is serving outside the conceptual boundary you thought a matching control created. Each failure needs a different fix.

A target CPA is a traffic constraint, not a cost ceiling

Abstract bid vehicles approach a narrow checkpoint, where only some pass through toward opportunities of different sizes.

Target CPA is easy to misread because its name sounds like a preferred result. In practice, the target constrains the auctions automated bidding can justify. When the available market no longer overlaps that target, the system cannot simply pay substantially more for every desirable prospect and preserve the target at the same time. It can reduce participation instead.

Consider a referral-software campaign that recorded only six impressions during a month in which it had effectively gone dark. Its account showed a $200 target CPA and a $182 actual CPA, which looked superficially healthy. The full change history showed that Maximize Conversions with a $200 target CPA had been introduced in October 2024. That target was about 12% higher than the CPA achieved in the previous year, so it was not an obviously aggressive choice when it was set.

The market had moved. Competition had more than doubled, CPC had risen 51.96%, and CPA had moved from $138.53 to $316.76. The $200 target had become roughly 37% lower than the cost the campaign was encountering per lead. The automation preserved the constraint by finding very little traffic it considered compatible with that constraint.

This is why an actual CPA below target does not automatically prove that a target is healthy. Ask how much delivery produced the number. An apparently efficient CPA based on negligible impressions or conversion volume can coexist with a campaign that is economically unable to scale.

Check volume before celebrating efficiency. Read actual CPA beside impressions, clicks, and conversions, not as an isolated score.
Compare the target with recent conditions. The CPA that justified a decision a year ago may describe a market that no longer exists.
Look for movement in input costs. A major CPC increase can make the old acquisition target unattainable even when the landing page and conversion setup have not changed.
Align the date of the decline with change history. A target may begin as attainable and become restrictive gradually, so the visible delivery collapse can occur well after the original edit.

If the evidence points to an unrealistic target, test a less restrictive target as a controlled bidding change. Do not simultaneously increase the budget and broaden matching. A higher target can admit more expensive auctions, while a larger budget gives the campaign more money to enter them; changing both prevents you from knowing which lever changed performance and increases the financial exposure of the test.

Match types and opt-outs need boundary tests

Exact match should be read as a priority and relevance mechanism, not as a literal-text firewall. Its boundaries changed in stages: close variants became optional in 2012, mandatory for exact and phrase match in 2014, and broader through later changes involving word order, implied terms, and paraphrases. Same-meaning matching reached phrase match and broad match modifier in 2019. Phrase match absorbed broad match modifier behavior in February 2021, and advertisers could no longer create new broad match modifier keywords by late July 2021.

An identical, eligible exact-match keyword can receive first priority, but that is a queue position rather than a delivery guarantee. The keyword must still be eligible, the campaign must have budget, inventory must exist, and exceptions for advanced search experiences may apply. “We have the exact keyword” therefore does not answer “Why did we receive no impression?”

Use a separate boundary test for each kind of control:

For negative keywords, test the strings you actually excluded. Add important synonyms and singular or plural forms separately when the concept must be blocked. Do not rely on positive-keyword expansion rules to describe negative-keyword behavior.
Inspect long searches carefully. On a search longer than 16 words, a negative term appearing after the sixteenth word will not block the ad. A rare long query can therefore cross a boundary without the negative keyword being ignored or malfunctioning.
For exact match, inspect eligibility and the matched search term. Determine whether the exact keyword was eligible to receive priority before treating the outcome as a matching failure.
For AI Max opt-outs, verify related behavior after the toggle changes. Some controls housed within the feature stop applying when it is disabled. The migration of Dynamic Search Ads into AI Max also means that switching AI Max off should not be assumed to recreate every aspect of the older campaign state.
For contextual signals, evaluate direction rather than compliance. Search themes, creative, keywords, and URLs can steer expansion. Confirm the result in search-term evidence instead of treating those inputs as enforceable exclusions.

The practical distinction is simple: verify hard boundaries against prohibited traffic, evaluate priority rules only after confirming eligibility, judge targets by both cost and volume, and assess contextual signals by the traffic they influence. Applying one test to all four produces false confidence.

Key takeaways: build a control-reliability routine

Keep a small control register for each material campaign. It does not need another dashboard. A shared account note or worksheet is enough if it records the setting, its scope, its authority class, the expected effect, the evidence used to verify it, the owner, and the safe rollback.

Start with authority, not the label. Decide whether a setting blocks, opts out, prioritizes, constrains, or guides before predicting its effect.
Use full-lifetime change history when delivery has no visible cause. The current configuration may be the accumulated effect of a decision hidden beyond the default date range.
Judge bid targets against recent attainable economics and meaningful volume. An actual CPA below target means little when the campaign barely enters auctions.
Test query controls at their real boundaries. Check variants, scope, eligibility, and long-query behavior rather than assuming that a control covers the surrounding concept.
Change one consequential lever at a time. Record the expected effect and rollback first, and keep the budget within an amount you are prepared to expose while the test runs.

Open the weakest-delivering campaign first. Expand its change history, classify its active controls, and choose the smallest reversible test that can distinguish an eligibility problem from an unrealistic target or a misunderstood matching boundary. Once you can state exactly what each control is allowed to decide, the account becomes much easier to manage without guessing.

References

Search Engine Land — How to tell which Google Ads controls actually control anything

September 17, 2026

Google Ads Automation: How to Keep Advertiser Control
Your Google Ads campaign can hit its reported target and still make a decision you would never approve. It can enter a competitor bidding war, learn from queries you already know are irrelevant, favor sales with weak margins, or expand into inventory you did not intend to buy.

You do not need to rebuild every campaign around manual bidding or revive an account full of single-keyword ad groups. You need a control system: clear business objectives, enough consolidated data for automation to learn, explicit boundaries on where it may explore, and a verification loop that catches strategically wrong behavior before it becomes expensive.

Key takeaways
- Automate execution inside boundaries you define. Google Ads can optimize an objective, but it cannot infer every commercial constraint behind that objective.
- Consolidate campaigns when fragmentation deprives Smart Bidding of conversion data. Split them only when the parts genuinely require different economics, budgets, policies, or market strategies.
- As a working benchmark rather than a universal platform rule, look for at least 30 monthly conversions per campaign, with 60 or more providing a stronger foundation for consistent automated bidding.
- Configure negative keywords, brand controls, network settings, and reporting before enabling wider expansion. Do not pay an algorithm to relearn exclusions your business already knows.
- Inspect search terms, match sources, networks, brand exposure, conversion quality, and profitability from the start. A strong top-line ROAS does not prove that the underlying traffic is acceptable.
- After a material change, respect conversion lag. Google has advised waiting one to two conversion cycles before drawing conclusions, unless a hard budget or policy boundary is already being breached.
Define what automation is allowed to decide

Advertiser control no longer means making every auction decision yourself. It means retaining ownership of the decisions that shape those auctions.

Google Ads can observe signals, predict the likelihood of a conversion, adjust bids, and expand targeting. It cannot automatically know that a particular competitor must be avoided, that returned orders erase the apparent profit from a product category, or that your sales team cannot handle another wave of low-value leads. Those are business facts, not auction facts.

The distinction matters because the platform’s definition of success is not automatically the advertiser’s definition. Google benefits when advertisers spend money. You benefit when additional spend produces acceptable incremental business outcomes. Those interests can overlap without being identical.

Write an automation contract for each campaign

Before changing a bidding strategy or enabling AI-driven expansion, write down the following decisions in plain language:
1. Business objective: Name the result the campaign is supposed to produce. Do not substitute ad position, traffic volume, or spend for a business result.
2. Economic target: Record the CPA, ROAS, margin, or other threshold the business actually uses. If different products have different economics, state how those differences will be represented.
3. Permitted expansion: Specify whether the system may explore broad queries, competitor searches, Search Partners, new geographic areas, or additional channels.
4. Prohibited behavior: List the queries, brands, locations, offers, audiences, and traffic sources that are unacceptable even if their reported conversion performance appears strong.
5. Conversion definition: Identify which recorded actions represent real value. Separate primary outcomes from actions that are useful for observation but should not steer bidding.
6. Evidence required: Name the reports you will inspect to verify search terms, match sources, networks, conversion quality, and economic performance.
7. Intervention rule: Define the conditions that require a pause, exclusion, target adjustment, or deeper review. Use thresholds approved by your business rather than inventing them after spend accelerates.
This contract prevents a common mistake: evaluating automation only by the metric it was instructed to optimize. If a campaign reaches target ROAS by entering strategically unwanted auctions, the bidding system may have completed its assignment perfectly. The assignment was incomplete.

Treat every platform recommendation as a hypothesis about execution. Ask which part of your contract it supports, which new permissions it requires, and where its effect will be visible. If you cannot answer those questions, investigate before applying it.

Consolidate learning without flattening business differences

The old response to uncertainty was often more structure: single-keyword ad groups, duplicated match types, traffic-sculpting negatives, and numerous narrowly defined campaigns. Much of that tactical granularity has become unnecessary under automated bidding and matching.

Excessive structure now creates a different risk. Every additional campaign divides the available conversion history. Automated bidding then has fewer observations from which to estimate performance, while each segment receives a smaller share of the account’s traffic and budget.

A useful working benchmark – not a guarantee and not a reason to ignore your own variance – is at least 30 conversions per campaign each month, ideally 60 or more, for Smart Bidding to operate consistently. Before creating a split, estimate how much recent conversion volume each resulting campaign would retain. If one side would fall well below that range, the business reason for separating it needs to outweigh the loss of learning density.

Use a business test for every proposed split

Create a separate campaign when at least one of these conditions is true:
- The segment needs a genuinely different CPA, ROAS, or profit target.
- Its budget must be protected or capped independently for a clear commercial reason.
- Its geography, availability, compliance requirements, or operating capacity differs from the rest of the account.
- Its brand, competitor, query, network, or channel policy must be different.
- The business intends to make a distinct investment decision about that segment and cannot obtain the necessary control through reporting, labels, or exclusions.
Do not create a campaign merely because a reporting dimension exists. Reporting taxonomy and bidding structure are different tools. You can often preserve a consolidated learning pool while using labels and reports to analyze meaningful groups.

Margin is a good example. An account divided into many narrow margin buckets, each carrying its own ROAS target, can look financially rigorous while fragmenting the data the bidding system needs. The resulting campaigns may be too small to achieve the targets that justified the structure.

Instead, use custom labels for information such as margin, sell-through rate, and return rate. Labels do not magically convert profit into a bidding signal, but they let you organize products, inspect performance, and make campaign decisions with context Google does not inherently possess. If you later separate a segment, you can do so because the data reveals a material economic difference, not because a spreadsheet had another row available.

Put guardrails in place before expansion starts

Automation should discover what you do not know. It should not spend your budget rediscovering what you already know.

This is especially important when broad matching or AI-driven expansion can reach searches outside your initial keyword set. Broad match defaults have long created a situation in which inexperienced advertisers can pay to teach the system lessons their businesses could have supplied in advance. If a query category is known to be irrelevant, exclude it before launch rather than waiting for wasted clicks to prove the point.

Configure the controls that correspond to the risk
1. Query risk: Add negative keywords for known irrelevant intent. Review whether exclusions need to apply at the campaign or account level based on how broadly the rule should operate.
2. Brand risk: Decide how your own brand, excluded brands, and competitor brands should be handled. AI Max provides brand inclusions and exclusions, but the advertiser still has to define the policy.
3. Network risk: Decide whether Search Partner Network traffic is permitted. Set the available network control deliberately, then evaluate actual network performance rather than relying on a general assumption about where AI Max will expand.
4. Economic risk: Make margin, returns, sell-through, and other meaningful product differences visible through your feed organization, labels, conversion values, reporting, or campaign design.
5. Measurement risk: Confirm that the conversions guiding bidding represent outcomes the business values. A campaign cannot optimize toward profit if the recorded objective rewards a weak proxy for it.
6. Visibility risk: Make sure the team knows where to inspect search terms, AI Max match type, match source, network delivery, and brand exposure before more traffic arrives.
Competitor traffic shows why these controls cannot be reduced to a performance metric. In one documented rollout, AI Max expanded traffic by targeting a much larger competitor. The reported performance looked good, but the advertiser had intentionally avoided those searches to prevent a bidding war. The system found an opportunity inside the data while violating a strategy that had never been encoded.

That is not an argument against AI Max. It is an argument for declaring competitor policy before enabling it and checking search terms from the first review. Strong aggregate results should increase your curiosity about where the gains came from, not end the investigation.

Be equally careful with conclusions drawn from a small number of campaigns. Early AI Max observations appeared to show a preference for Search Partner traffic, but additional data did not support that as a general rule. Use account-level findings to form a testable question. Do not turn them into a platform-wide belief until the evidence warrants it.

Verify patiently, then keep strategy human

Good oversight separates two jobs that are often confused. Verification asks whether the system is doing what you authorized. Evaluation asks whether the result is good enough to continue. Verification starts immediately; evaluation may need to wait for conversions to mature.

Inspect behavior in the right order

Use this sequence when reviewing an automated campaign:
1. Delivery: Check where spend occurred, including networks, locations, channels, and any other enabled expansion surface.
2. Matching: Inspect search terms, match type, and match source. Identify which traffic came from your explicit targeting and which came from automation.
3. Strategic fit: Look for prohibited brands, competitor auctions, irrelevant intent, or traffic that conflicts with your operating policy.
4. Conversion quality: Determine whether the reported conversions represent qualified leads, completed sales, or another outcome the business can actually use.
5. Economics: Review CPA or ROAS alongside the margin, returns, sell-through, capacity, and customer value information relevant to the decision.
This order keeps a blended efficiency metric from concealing an unacceptable mechanism. If the campaign reaches its ROAS target through traffic your business has explicitly rejected, you have enough evidence to tighten the boundary even before the long-term average settles.

Allow for conversion lag without tolerating a breach

After a platform update or material campaign change, immediate performance claims are unreliable when conversions take time to arrive. Google has advised advertisers in this context to wait one to two conversion cycles before assessing the effect.

That waiting period is not permission to ignore the account. Continue checking spend, query relevance, network delivery, and other hard boundaries. If automation exceeds an approved budget limit or enters prohibited traffic, intervene. If the guardrails hold but the efficiency metric fluctuates, let the relevant conversion window mature before declaring success or failure.

Avoid defensive target changes made only because other advertisers appear worried. Advertisers have raised target ROAS even when their campaigns were not budget-limited, a reaction that can reduce participation without solving an identified problem. A stricter target may be appropriate, but changing it can materially reduce volume. Require an account-specific reason and preserve a baseline against which the effect can be judged.

Keep a decision log, not just a change history

For every material adjustment, record:
- The date and exact setting changed.
- The business problem the change is meant to solve.
- The expected effect on traffic, conversions, CPA, ROAS, or profit.
- The relevant conversion lag or evaluation window.
- The reports that will confirm where the effect came from.
- The hard boundary that would justify intervening early.
- The final decision after enough data has accumulated.
When possible, avoid stacking several material changes into the same evaluation window. If you alter the target, budget, network access, negatives, and campaign structure together, even a clear performance movement may not tell you which decision caused it.

Apply the same skepticism to controls whose labels sound clearer than their mechanics. An emerging Performance Max control for channel importance may give Google greater tolerance around a CPA or ROAS target when a channel receives more importance. Do not assume that increasing importance simply buys more of a channel at unchanged economics. Document the intended outcome, monitor actual allocation and efficiency, and reverse the change if the observed tradeoff is unacceptable.

Finally, do not confuse prominence with profit. Paying whatever it takes to hold the top ad position was an expensive mistake in earlier paid search, and position-driven bidding can sacrifice economics for prestige. Automation does not change that principle. Your objective should describe the business outcome you want, not the visible status you hope to occupy.

Start with one automated campaign this week. Write its automation contract, remove any split that lacks a business reason, encode known exclusions, capture a baseline, and schedule the evaluation for the end of its relevant conversion window. You will have given the system room to find demand without giving it authority to redefine what your business considers a good customer, an acceptable auction, or a profitable result.

References
- Search Engine Land – Matt Van Wagner shares what’s changed, what disappeared and what PPC still gets wrong
- Search Engine Land – Google Ads AI needs guardrails, not blind trust ft Mike Ryan
September 15, 2026
Google Ads Controls: Smarter Bidding and Compliant Location Assets
When conversion volume falls or a Location asset stops appearing, the tempting response is to start changing settings. That can make the account harder to diagnose. A bid target, a conversion signal, and a location record control different parts of delivery.

You need to identify which control is failing before you touch it. The framework below will help you choose the right bidding objective, adjust targets without outrunning your data, recover from restricted delivery, and correct Location assets at their actual point of origin.

Key takeaways
- Use Maximize Conversions or Maximize Conversion Value when volume from the available budget is the priority. Use Target CPA or Target ROAS when efficiency is the binding constraint.
- Set an initial target near demonstrated performance, not at an aspirational number the campaign has never approached.
- For Target CPA, test reductions of roughly 10% to 20%, then wait one or two complete conversion cycles before judging the result.
- If a target suppresses delivery, inspect tracking, landing pages, and queries before moving down the bidding ladder.
- Correct business information and location images in Google Business Profile. Revised Location asset guidance did not introduce a new policy or a change in enforcement.
Separate the controls before diagnosing the campaign

A Google Ads campaign has several control layers. They interact, but they are not interchangeable:
- Auction control: The bidding strategy and any CPA or ROAS target determine what the system is being asked to prioritize.
- Measurement control: Primary conversion actions tell the bidding system which outcomes count as success.
- Asset control: Location information must come from an eligible, accurate business record and comply with both general advertising policies and Location asset requirements.
Write the failure in one sentence before changing anything. “We are getting conversions, but their cost exceeds what the business can support” is an efficiency problem. “Tracking looks healthy, but a previously attainable target is producing too little activity” may be a bidding restriction. “The address or opening hours are wrong” is an upstream business-information problem.

This distinction prevents compensating for one failure with an unrelated control. A looser CPA target cannot repair a bad phone number. A corrected address cannot fix optimization toward spam leads. More budget cannot make an unrealistic efficiency target attainable.

Match the bid strategy to the constraint that actually matters

Start with a plain business decision: do you need the greatest available conversion volume, or must every additional conversion stay within a defined efficiency range?

If you want the most conversions possible from a fixed budget, Maximize Conversions is the more direct instruction. If conversion values are meaningful and reliably measured, Maximize Conversion Value applies the same volume-first logic to value. Target CPA and Target ROAS are better suited to campaigns where efficiency is the constraint: leads must remain below an acceptable acquisition cost, or revenue must remain above an acceptable return threshold.

That choice matters more now because a target should not be treated as a protective ceiling that Google will always try to beat. Under the target behavior being observed, a $10 Target CPA can act as a result for the system to approach on average. A campaign that once delivered at $5 against that target may not preserve the same gap automatically. The benefit is greater predictability when you consider increasing the budget; the tradeoff is that historical overperformance may narrow.

Your initial target therefore needs to describe acceptable reality. If the campaign is producing conversions at a $30 CPA, begin reasonably close to $30. Setting $15 because that is where the business eventually wants to be can restrict delivery before the system has shown that the number is attainable.

For a new campaign without enough performance history, do not invent a target simply to make the setup look controlled. A maximize strategy can establish the data needed to choose a defensible target later. Control comes from using evidence to add the constraint, not from adding it at the earliest possible moment.

Campaign structure also affects whether one target can represent the underlying economics. Brand and non-brand traffic commonly convert at different costs. New-customer acquisition may justify a different cost when customer value differs. Separate campaigns when their economics require different targets; otherwise, a blended average can hide whether either group is performing as intended.

Tune targets at the speed of your conversion data

A target is a lever, not a dial to turn every morning. Frequent changes are especially dangerous when conversions take time to mature because the most recent rows in a report may not yet contain their eventual outcomes.
1. Validate the success signal. Confirm that primary conversions represent business outcomes worth buying. A store visit is not automatically equivalent to a purchase, and a cheap lead is not valuable when it is spam or has almost no chance of becoming a customer.
2. Record the baseline. Capture the current target, actual CPA or ROAS, conversion volume, spend, and the period required for conversions to mature.
3. Look for room to tighten. If actual CPA consistently meets or beats the target, particularly when the campaign is limited by budget, consider lowering Target CPA.
4. Make one controlled move. A practical Target CPA test is a reduction of about 10% to 20%. For Target ROAS, move deliberately toward stronger efficiency, but do not assume that the same percentage is a universal rule for a different metric.
5. Wait for mature evidence. Let the campaign run for one or two conversion cycles before deciding whether the adjustment worked.
6. Judge the whole result. Compare the target with actual performance, but also check conversion volume and quality. A lower CPA achieved by eliminating valuable demand is not the same result as a lower CPA at healthy volume.
Your review interval might be weekly, biweekly, or monthly. The right cadence depends on campaign volume and the length of the conversion cycle, not on how often the dashboard changes. Changing the target before conversions mature means acting on incomplete performance data.

The 10% to 20% range is a testing increment, not a promised improvement. Stop tightening when volume deteriorates, the campaign no longer produces enough evidence, or the resulting customers fail the quality test. The system can only optimize toward the outcomes you report.

When target bidding stops delivering

Use a diagnostic ladder instead of making several simultaneous changes:
1. Check conversion tracking and confirm that the designated primary actions still fire correctly and represent valuable outcomes.
2. Inspect landing pages and search queries for a demand, relevance, or experience problem that bidding cannot solve.
3. If those fundamentals are healthy, remove the CPA or ROAS target and move to Maximize Conversions. This tests whether the target itself is restricting the algorithm.
4. If Maximize Conversions still cannot generate enough activity, use Maximize Clicks to rebuild traffic and data before returning to conversion-focused bidding.
This sequence lets you move down the bidding ladder as campaign conditions change. Treat Maximize Clicks as a traffic-building stage, not proof of business success: clicks are useful only when they lead to measurable, qualified outcomes. Keep the budget within an amount you are prepared to spend while rebuilding that evidence.

Fix Location asset compliance at the data source

Location assets can add an address, phone number, opening hours, and ratings to an ad. They remain subject to Google’s standard advertising policies and its specific Location asset requirements.

Google revised the wording of those requirements in September to make them clearer and add troubleshooting help. That revision did not create a new Location asset policy or change enforcement. Do not rebuild a compliant setup merely because the help language changed. Investigate the actual data, regional availability, and policy status first.
1. Confirm the business record. Verify that the Google Business Profile supplying the location represents the location you intend to advertise.
2. Audit customer-facing details. Check the address, phone number, and opening hours against the business’s current information.
3. Make corrections upstream. Business information and location images are managed in Google Business Profile, not inside Google Ads. Repeated ad edits will not correct inaccurate profile data.
4. Check geographic availability. Google Business Profile is available only in supported countries and regions, so confirm support before treating setup failure as a campaign malfunction.
5. Review both policy layers. Check general advertising policies as well as the Location asset-specific requirements. Passing one does not eliminate the need to satisfy the other.
6. Keep bidding changes separate. If the asset and campaign have problems at the same time, correct the location record without also changing the bid target. You will be able to see which intervention affected which result.
At your next account review, label every campaign either Volume or Efficiency. Record its current target and actual result, set the next review date after the appropriate conversion cycle, and then audit the connected Google Business Profile separately. That small operating discipline gives every control one job and gives you evidence before the next change.

References
- Search Engine Land – Google’s target bidding shake-up: Why PPC marketers have been here before
- Search Engine Land – Google updates Location asset requirements without changing enforcement
September 9, 2026

Tag: Ad Control

Campaign-level frequency can hide account-level saturation

Choose between broader reach and managed repetition

Build a campaign group around one coherent job

Measure delivery changes, not just cleaner reporting

Key takeaways

References

Key takeaways

Separate brand identity from creative performance

Audit a mismatched business name before resubmitting it

Design a Performance Max test around one creative claim

Turn the experiment result into a bounded decision

Use a two-gate workflow for every brand change

References

The ruling preserved a path, not a payout

The economic dispute sits between inventory and demand

Do not mistake the damages estimates for recoverable amounts

Build a counsel-led evidence pack while the systems are identifiable

Key takeaways for publisher teams

References

Separate the two automations before setting policy

Audit your website before automated promotions serve

Launch localization as a new market, not a translation task

Use one release gate for assets, language and money

Key takeaways

References

Treat placement and presentation as separate control planes

Turn content exclusions into an enforceable brand policy

Build the exclusion list in six steps

Build sitelinks that survive changes in visual treatment

Make every sitelink understandable on its own

Diagnose performance shifts before changing the campaign

Key takeaways

References

Build a control plane before you automate campaign changes

Turn search-term-to-page evidence into a repair queue

Model PMax controls by platform, object, and scope

Separate audience usefulness from permission to use the data

Use benchmarks and bidding recommendations as questions, not commands

Key takeaways

References

What the court changed in Google’s ad tech stack

Key takeaways for publishers and advertising teams

Turn the remedy into a controlled testing plan

Questions that expose whether access is genuinely usable

Connectivity and auction behavior

Data, fees, and contractual control

Keep ad tech oversight separate from search and AI visibility

References

The control hierarchy: five settings, five different promises

When delivery collapses, diagnose authority before changing bids

A target CPA is a traffic constraint, not a cost ceiling

Match types and opt-outs need boundary tests

Key takeaways: build a control-reliability routine

References

Key takeaways

Define what automation is allowed to decide

Write an automation contract for each campaign

Consolidate learning without flattening business differences

Use a business test for every proposed split

Put guardrails in place before expansion starts

Configure the controls that correspond to the risk

Verify patiently, then keep strategy human

Inspect behavior in the right order

Allow for conversion lag without tolerating a breach

Keep a decision log, not just a change history

References

Separate the controls before diagnosing the campaign

Match the bid strategy to the constraint that actually matters

Tune targets at the speed of your conversion data

When target bidding stops delivering

Fix Location asset compliance at the data source

References