Category: Google Ads

Third-Party Endorsements in Google Search Ads: What to Do
If you buy Google Search ads, the immediate question is whether you can get a publisher quote into your own ad. For now, there is no disclosed setup path, eligibility rule, or request process. Rebuilding a campaign around this feature would be premature.

You can still prepare intelligently. The useful work is to organize the independent evidence behind your brand, decide how you would measure an endorsement if one appeared, and avoid confusing an experimental ad treatment with an advertiser-controlled asset.

What the endorsement test actually changes

The experimental format places a short statement from an external publisher directly beneath the advertiser’s description. The treatment can include the publisher’s name, logo, and favicon, visually separating the statement from the copy supplied by the advertiser.

One observed ad displayed the line “Best for Frequent Travelers” and attributed it to PCMag. That example matters because it shows the kind of claim involved: a concise editorial judgment about whom a product suits, rather than a generic customer rating or another promotional sentence written by the advertiser.

This distinction changes how you should evaluate the feature. Your headline and description present your own proposition. A recognizable external endorsement could add a different kind of evidence at the moment someone is deciding which result deserves a click. It may make the ad resemble an editorial recommendation more closely, but that possible effect has not yet been established through disclosed performance data.

Google has confirmed only that it is running a “small experiment” involving third-party endorsement content. Several operational questions remain unanswered:
- Which advertisers, products, queries, or publishers are eligible.
- Whether an advertiser can opt in or opt out.
- Whether an advertiser can request, select, approve, or reject an endorsement.
- How Google finds the content and decides which statement to display.
- How old, changed, disputed, or removed publisher content would be handled.
- Whether the experiment is connected to review-extension concepts, publisher partnerships, or broader trust-and-safety systems.
Until those questions are answered, treat the endorsement as a possible search-result treatment, not as a new asset type you can add to a campaign. There is no documented basis for changing bids, budgets, campaign structure, or creative solely to obtain it.

Prepare your brand without trying to game the experiment

You cannot configure an undisclosed feature, but you can make your external reputation easier to understand and manage. Start with an endorsement inventory. A simple worksheet should contain the publisher, URL, covered brand or product, exact wording, publication date, current status, and the person responsible for checking it.
1. Record exact claims, not flattering paraphrases. “Best for frequent travelers” is materially different from “best travel product.” Preserve the original wording and context internally so your team does not turn a narrow judgment into a broader claim.
2. Classify the evidence correctly. Keep editorial endorsements separate from customer reviews, testimonials, awards, certifications, affiliate roundups, and paid placements. They may all support trust, but they are not interchangeable.
3. Check the product and audience match. An endorsement for one plan, model, or use case should not be treated as validation for an entire company. Map each statement to the exact landing page and offer it describes.
4. Make brand and product names consistent. If a product has several informal names across your site, campaign, and public coverage, document which names refer to the same thing. Clear naming helps your own team avoid attaching the wrong evidence to an ad or landing page.
5. Create a correction route. Assign an owner who can contact a publisher when a factual detail is outdated or inaccurate. You may not be able to control what Google displays, but you can keep the underlying public information accurate.
Do not copy publisher quotations or logos into your creative merely because Google displayed them in an experiment. A platform-generated treatment does not automatically give an advertiser permission to reuse editorial language or branding elsewhere. Keep the inventory as an evidence and monitoring tool unless your organization has the appropriate permission for direct reuse.

It is also too early to commission coverage for the purpose of triggering this format. You do not know whether Google considers a particular publisher, whether paid or affiliate relationships affect selection, or whether advertisers will ever receive controls. Earn credible coverage because the coverage itself helps buyers evaluate you, not because you expect it to become an ad decoration.

Measure an appearance without inventing causality

If an endorsement appears beneath one of your ads, a screenshot proves that the treatment rendered. It does not prove that the treatment improved performance. Queries, competitors, auction conditions, audience mix, devices, and campaign changes can all affect the same metrics.
1. Capture the context. Save the screenshot along with the query, date, time, country, device type, displayed endorsement, publisher, ad copy, and destination URL.
2. Annotate your reporting. Record when the first appearance was observed and note any simultaneous changes to bids, budgets, targeting, creative, landing pages, offers, or conversion tracking.
3. Look for repeated exposure. Do not make a budget decision after one observation. Establish whether the treatment appears repeatedly and whether its wording stays consistent.
4. Use business metrics in sequence. Examine click-through rate first, then conversion rate and the cost or return metric your campaign actually uses. A higher click-through rate with lower post-click quality is not automatically an improvement.
5. Use the closest valid comparison. Compare similar queries, ads, audiences, and periods where possible. If Google does not provide an exposure field or experiment control, label any apparent difference as directional rather than causal.
Avoid rewriting your description to imitate the endorsement. Repetition can waste limited ad space, and a line that looks independent loses its meaning when the advertiser makes the same claim about itself. Your copy should explain the offer; the external statement, if shown, should remain clearly external.

Keep paid search, SEO, AEO, GEO, and schema in their proper lanes

Third-party validation can support a broader visibility strategy, but this experiment does not establish a technical connection between Search ads and organic or AI-generated results. The selection process and its relationship to other Google systems remain undisclosed.
- For paid search: the observed endorsement is an experimental element displayed with an ad. It is not currently a documented advertiser asset.
- For SEO: there is no disclosed evidence that appearing in this treatment changes organic rankings.
- For AEO and GEO: independent coverage can give people and answer systems public material with which to understand a brand, but this ad experiment does not prove that the same selection mechanism powers AI answers or citations.
- For structured data: there is no disclosed evidence that JSON-LD or another schema type triggers the endorsement.
Your safest cross-channel strategy is therefore straightforward: keep product facts precise, use consistent entity names, maintain the pages that substantiate your claims, and organize legitimate independent coverage. Those actions make your brand easier to verify even if this particular ad format never expands.

Use a simple decision rule. If an activity makes your public evidence clearer, more accurate, or more useful to a prospective buyer, it is worth considering on its own merits. If its only purpose is to trigger an undocumented ad feature, defer it until Google publishes eligibility rules and advertiser controls.

Key takeaways
- Google is testing publisher quotations, names, logos, and favicons beneath some Search ad descriptions.
- The confirmed example is part of a small experiment, not a generally available ad feature.
- No public setup path, eligibility rule, opt-in mechanism, selection method, or performance reporting has been disclosed.
- An endorsement inventory can help you manage external claims without assuming that you can submit them to Google.
- If the treatment appears, document the exposure and assess the entire path from click to conversion before changing spend.
- Do not treat SEO, AEO, GEO, or schema work as a shortcut into the experiment without evidence of a connection.
Build the inventory now, add a place for endorsement observations to your campaign log, and leave campaign economics unchanged until repeated data or official controls give you something reliable to act on.

References
- Search Engine Land — Google tests third-party endorsements in Search ads
January 30, 2026

Google Ads API v23: A Practical Upgrade Plan for 2026

Your Google Ads integration may be stable, but that does not make the v23 decision automatic. You need to know whether upgrading will close a real operational gap: opaque Performance Max reporting, difficult invoice reconciliation, date-only scheduling, fragmented store data or an audience workflow that still depends on manual interpretation.

Google Ads API v23 brings those changes into the same release, while also beginning a faster API release cycle for 2026. The practical response is not to adopt every feature at once. It is to connect each capability to a decision, migrate the safest read paths first and put tighter controls around anything that can change targeting, schedules or spend.

Choose the upgrade scope from the decisions you need to improve

Start with the workflow that consumes the data, not the endpoint that exposes it. A feature has upgrade value only when someone can name the decision it will improve, the current workaround it will replace and the failure you need to prevent.

v23 capability	Decision or workflow it can improve	First acceptance test
Performance Max breakdown by ad network type	Explaining where campaign results are occurring	Segmented values reconcile with the unsplit control query for every additive metric you publish
Campaign-level invoice details, regulatory fees and adjustments	Billing reconciliation and client cost allocation	Every amount remains traceable to its original charge type instead of being forced into media spend
Campaign start and end date-times	Precise launch, promotion and shutdown scheduling	A controlled write-read test preserves the intended date, time and governing timezone convention
PerStoreView location details	Store-level reporting and local performance analysis	The account and location scope agrees with the corresponding Stores report
LIFE_EVENT_USER_INTEREST	Life-event dimensions in audience insight workflows	The new dimension survives extraction, storage and review without being collapsed into a generic interest label
Surface-specific Demand Gen conversion-rate forecasts	Planning separately for placements such as Gmail and Shorts	Surface remains part of the forecast key through the planning layer
Free-text descriptions converted into structured audience attributes	Drafting audience definitions from a strategist’s brief	The generated attributes are visible, validated and approved before downstream use
Additional Shopping competitive and conversion-date metrics	Competitive analysis and conversion reporting	Every metric carries its date basis and aggregation rule into the dashboard

This map also exposes ownership. Performance Max and Shopping changes usually begin with analytics engineering. Invoice changes require a finance or billing consumer. Date-time scheduling belongs to the team that owns campaign mutations. Audience generation needs both a technical owner and the person accountable for targeting decisions.

A low-risk migration sequence starts on the read side. Capture representative outputs from your existing integration, upgrade the required client libraries and code in an isolated path, add one v23 capability, and compare its result with your control data. Move write operations only after your storage, validation and monitoring layers understand the new values.

List every query, scheduled job, report, billing export and campaign writer affected by the upgrade.
Record the account scope, selectors, reporting window and downstream consumer for each path.
Capture baseline responses and the totals currently shown to users.
Upgrade the client dependency and generated types without changing business logic in the same step.
Add one v23 capability behind a separately testable query or writer.
Define a reconciliation rule, an owner and a rollback condition before releasing it.
Keep the old output available until the new consumer passes both data and operational checks.

Rebuild reporting around the new data grain

An analyst examines an opaque campaign object as it passes through a prism and separates into distinct reporting components.

The reporting additions are useful because they expose distinctions that were previously difficult to retrieve. They can also break a pipeline that assumes one row per campaign, one meaning for a date or one reporting grain across every metric.

Performance Max network breakdowns need a new row key

Google Ads API v23 adds an ad-network-type breakdown for Performance Max reporting. Once that segment enters a result, a campaign can occupy more than one row. Any transformation keyed only by campaign can overwrite rows, duplicate joined values or accidentally recombine the split before an analyst sees it.

Add the network dimension to the unique key at ingestion. Then run a paired query: one result at the original campaign grain and one with the network split. Reconcile metrics that your reporting contract treats as additive. For ratios and calculated metrics, recompute from their underlying components where your data model supports that; do not sum percentages merely because they arrived in separate rows.

Label the output narrowly. A network breakdown provides a more useful view of distribution, but it should not be presented as complete Performance Max transparency. That wording matters because analysts will otherwise infer visibility into decisions the field does not actually expose.

Shopping conversion-date metrics need an explicit time basis

Expanded Shopping reporting includes new competitive and conversion metrics organized by conversion date. A conversion-date series answers a different question from a series organized around the ad interaction. If your warehouse stores both under an undifferentiated date column, a dashboard can produce a plausible trend with the wrong meaning.

Give every affected metric a semantic contract. At minimum, record its metric name, date basis, source grain and permitted aggregation behavior. Carry the date basis into the BI model and display label. If you show conversion-date and interaction-date views together, identify them explicitly instead of blending them into one unlabeled total.

Competitive metrics deserve the same discipline. Do not assume a newly available value can be summed across products, campaigns or dates. Preserve the returned grain first, then implement only the aggregation behavior your reporting definition supports.

Use PerStoreView as a controlled local-data migration

PerStoreView exposes store location details aligned with the Stores report. That alignment gives you a practical acceptance test. Select a known account and location scope, retrieve both views, and compare the location set and identifying details before replacing an existing store feed.

Preserve the identifiers exposed by the API instead of matching stores only by display name. Names can be formatted inconsistently in downstream systems, while a durable identifier gives you a defensible join. Keep store attributes separate from campaign measures as well; duplicating a location attribute across performance rows does not make it an additive metric.

Your exception report should show missing locations, duplicate mappings and conflicting attributes. Do not hide those cases inside an inner join. A clean-looking dashboard that silently drops an unmatched store is harder to repair than a visible migration exception.

Keep billing detail and scheduling precision from creating new errors

Two v23 features move beyond analytical convenience. More detailed invoices affect financial reconciliation, while precise campaign date-times affect when ads can run. Both deserve stronger controls than a new reporting column.

Model invoice charges by type before calculating totals

InvoiceService can now return campaign-specific costs, regulatory fees and adjustments. Those amounts may contribute to the same billing reconciliation, but they do not mean the same thing. Putting all of them into an internal field named spend destroys the distinction that makes the new detail valuable.

Retain the raw response, then normalize each amount into a typed financial record. Your internal model should distinguish campaign cost, regulatory fee and adjustment, preserve the campaign association when supplied, and record the sign convention used by your system. Never change the raw value to make a reconciliation pass.

Reconcile typed amounts to the billing total your finance workflow expects.
Flag an adjustment whose sign cannot be interpreted confidently instead of silently treating it as a cost.
Keep fees visible as fees in client and internal reports.
Surface campaign references that cannot be mapped to your internal campaign table.
Make repeated ingestion idempotent so rerunning a billing job does not duplicate a charge.

Release the richer invoice feed beside the existing reconciliation for at least one normal billing run in your own workflow. The purpose is not merely to reach the same final number. Finance should be able to explain which campaign costs, fees and adjustments produced it.

Treat date-time scheduling as a write-path migration

Campaigns can use precise start and end date-times rather than date-only boundaries. That is an operational change, not just a more detailed field. A database column, serializer or form built around dates can strip the time and still produce a syntactically valid value with the wrong schedule.

Trace the value from the user’s input through storage, request construction and the returned campaign state. Confirm the timezone or normalization convention required by the API and your client library rather than guessing. Keep the user’s intended local time available for audit even if your integration also stores a normalized representation.

Test a same-day start and end.
Test a boundary near midnight.
Test a date affected by a daylight-saving transition when the campaign’s market uses one.
Test that an end earlier than the start is stopped by your own validation.
Read the campaign back after writing and compare the returned schedule with the submitted intent.
Verify that legacy date-only jobs do not overwrite the newer time values on their next run.

Do not move this writer into production while the timezone or end-boundary behavior remains ambiguous. An incorrect boundary can allow spend outside the intended promotion window or stop a campaign while it should still be active. Use a controlled, low-risk campaign for the final lifecycle check and require an explicit rollback path.

Put human review between AI assistance and campaign changes

A campaign manager reviews AI-generated adjustment modules before allowing one to pass through an approval gate into an advertising system.

Google Ads API v23 expands AI-assisted audience and planning workflows in three different ways: a new life-event dimension, free-text audience generation and surface-specific Demand Gen forecasting. They should not be merged into one opaque automation step. Each produces a different kind of planning input and needs a different validation rule.

Preserve LIFE_EVENT_USER_INTEREST as its own dimension

The new LIFE_EVENT_USER_INTEREST audience dimension gives Insights workflows a structured way to work with life-event interests. Store the dimension type separately from its returned value. Mapping it immediately into a generic interest bucket removes the distinction before a strategist can use it.

Add explicit handling for unknown or newly returned values. A resilient integration should retain a value it does not recognize, route it for review and continue processing the rest of the response. Hard-coded mappings that discard an unfamiliar value make API evolution look like missing audience demand.

Handle generated audience attributes as a proposal

Generative audience tooling can translate a free-text audience description into structured attributes. That can reduce manual setup, but the structured result is still the consequential output. The input may sound reasonable while the generated attribute set is broader, narrower or simply different from what the strategist intended.

Make generation a reviewable draft. Store the original description, the complete structured result, the version of your internal mapping logic, the reviewer decision and the eventual change applied downstream. Show the strategist a diff between the current audience definition and the proposed one. Empty attributes, unsupported values and unexpectedly broad additions should block automatic application.

This audit trail is also how you make the feature debuggable. If campaign behavior later raises a question, you can distinguish the user’s brief, the generated interpretation and the approved configuration instead of treating them as one decision.

Keep Demand Gen forecasts separated by surface

Demand Gen conversion-rate forecasts can now vary across surfaces such as Gmail and Shorts. Include surface in the storage key, API-to-warehouse mapping and planning view. Otherwise, one surface can overwrite another or an early average can erase the difference the feature was designed to expose.

Use each forecast as a planning input, not a guaranteed outcome. Retrieve the forecast without automatically changing budget or targeting, show the surface-level values to the planner, record the decision they support and compare eventual performance using the same surface distinction where your measurement data permits it.

Key takeaways for your v23 upgrade sequence

Adopt v23 by workflow value, not by feature count. Tie every capability to a named decision and consumer.
Move read-only reporting first. Baseline, dual-run and reconcile before replacing an existing output.
Add the new dimension to your data key. Network, store, surface and date-basis distinctions must survive ingestion.
Keep financial meanings separate. Campaign costs, regulatory fees and adjustments should remain typed and traceable.
Test scheduling end to end. Database precision, serialization, timezone handling and legacy writers can all alter the intended date-time.
Keep AI-generated audience attributes behind validation and human approval.
Build reusable migration checks now. A faster 2026 release cadence makes a repeatable test harness more valuable than a one-off v23 patch.

Your next step is to create one migration ticket for each capability you intend to use. Give it an owner, affected consumer, baseline sample, reconciliation rule, failure alert and rollback condition. Start with the highest-value read-only gap. Move invoice and scheduling changes only when the teams responsible for billing and campaign operations have approved the acceptance tests.

That approach lets you capture v23’s useful reporting and planning gains without turning the upgrade into an uncontrolled rewrite. It also leaves you with a migration pattern you can reuse as the Google Ads API release pace increases.

References

CrushPress.AI – Boost Your Google Ads in 2026 with v23 API Insights

January 29, 2026

Google Performance Max Ad Previews: A Practical QA Guide

You’ve refreshed a Performance Max asset group and need a clear answer before approving it: will the creative still look deliberate when it appears across different placements? Until now, getting that answer could take more navigation than the review itself.

The one-click preview makes the mechanical part faster. Its real value, however, depends on what you do after opening it. With a fixed review sequence, you can turn a convenient interface shortcut into a reliable quality-control step.

Where the one-click PMax preview lives

Google Ads has shortened the path between the asset list and the rendered ad. From the Asset Groups table, clicking an image or video now opens previews for different Performance Max placements without requiring you to leave the page.

That is a workflow change, not a new campaign strategy. The preview does not, by itself, add targeting control, supply performance evidence, or explain why PMax gives one asset more delivery than another. It puts the creative closer to the surface so you can inspect it with less friction.

The time saving matters most when you manage a large asset library or replace creative frequently. Instead of treating previews as a separate destination that you visit only when something looks wrong, you can use the Asset Groups table as a review queue: open an asset, inspect the available presentations, record the decision, and move to the next one.

Do not assume that opening one image validates the entire asset group. A preview answers a narrow question about the creative in front of you. If several images or videos changed, each changed asset needs its own review.

A repeatable workflow for reviewing PMax creative

Hands arranging abstract ad-preview cards through visual checks for first impression, cropping, contrast, and consistency across devices.

Random clicking is quick but unreliable. Use the same sequence every time so that a busy reviewer does not approve the first attractive rendering and miss a problem elsewhere.

Define the scope before opening previews. Identify which asset groups changed and whether the change involved an image, a video, the surrounding message, or several elements. If the message changed, include older assets in the review because a previously acceptable visual may no longer fit the new offer.
Set the blocking criteria. Decide what requires revision before approval: an unclear focal point, unreadable embedded text, a hidden logo, a conflicting offer, an awkward crop, or a mismatch with the destination. This keeps personal taste from becoming the approval standard.
Open each image and video from the Asset Groups table. Review every placement presentation the interface makes available. Do not stop after the first version simply because it looks acceptable.
Inspect in a fixed order. Check composition first, legibility second, brand and product recognition third, and message consistency last. A fixed order reduces the chance that a strong headline distracts you from a weak crop.
Record an asset-level decision. Use simple statuses such as Pass, Revise, and Block. Include the asset identifier, the placement or rendering where the issue appeared, the reason for the decision, the required change, and the person responsible for it.
Reopen the preview after revision. A corrected source asset can solve one problem while creating another presentation issue. Approval should apply to the revised rendering, not to the intention behind the revision.

This process also makes team reviews easier to resolve. “The creative feels off” gives a designer little direction. “The product is no longer recognizable in the narrow rendering” identifies the visible failure and the condition the next version must satisfy.

What to inspect across the available placements

Image composition and legibility

An image can be strong as a standalone file and weak once placed inside an ad layout. Review the displayed creative as a user would encounter it, not as the designer saw it on a full-size canvas.

Focal point: Confirm that the product, person, or action remains immediately understandable in each displayed presentation.
Embedded text: Check whether words inside the image remain readable. If the message depends on enlarging the preview, it is not doing its job in the ad.
Logo and product recognition: Make sure the identifying elements are visible without crowding the composition.
Edges: Look for important details that sit too close to the boundary or appear cut off in a displayed rendering.
Visual hierarchy: The main subject should win attention before decorative elements, badges, or background details.

A useful test is to ignore the surrounding copy for a moment. If you cannot tell what the image is trying to communicate, the text is being asked to rescue the creative.

Video clarity and continuity

Review a video as a sequence, not merely as a valid uploaded file. The opening should establish enough context for the viewer to understand what follows. Watch on-screen text, scene changes, product visibility, logos, and the ending. Important information should not become hard to read or appear crowded by the displayed layout.

Then compare the video’s promise with the rest of the ad. A polished video can still fail review if it promotes a different product, audience, offer, or next step from the copy presented with it.

Asset pairing and destination consistency

PMax creative should be reviewed both as individual assets and as an assembled message. When copy appears with the selected image or video, read the combination from beginning to end.

Confirm that the visual and copy refer to the same product, service, or action.
Remove accidental repetition when an image already contains the same wording shown beside it.
Check that a specific offer in the creative agrees with the current campaign message.
Make sure the requested action is a sensible next step for the user.
Compare the approved ad message with the destination page separately. The preview can show the ad side of the experience, but it cannot perform that destination review for you.

This is where the preview earns more than a quick visual check. Assets that look acceptable in isolation can become confusing when presented together. Reviewing the assembled message helps you catch that problem before treating it as a performance mystery.

What a PMax preview can and cannot prove

Split illustration showing a controlled ad preview beside the same creative appearing in varied real-world screen contexts.

The most important distinction is between visual evidence and performance evidence. A preview lets you examine what is displayed in the preview. It does not tell you whether that presentation will receive meaningful delivery or produce better campaign results.

Decision	What the preview establishes	What you should do
Visual approval	Whether the displayed examples meet your creative standard.	Inspect every available placement presentation for each asset in scope.
Actual delivery	It does not guarantee which asset combination will receive impressions.	Use campaign reporting to evaluate delivery after the ads run.
Performance	It does not show which asset will generate stronger results.	Base performance decisions on relevant campaign data, not appearance alone.
Destination consistency	It shows the ad side of the message, not the full landing-page experience.	Compare the creative, offer, and requested action with the destination manually.
Root cause	It can expose a visible flaw but cannot prove that the flaw caused a performance change.	Treat the preview as diagnostic evidence and investigate other campaign factors before assigning cause.

This boundary prevents two common errors. First, an attractive preview is not proof that an ad will perform well. Second, weak results do not automatically prove that the crop, image, or video is responsible. Use previews to remove visible defects; use delivery and outcome data to make performance calls.

The update also does not eliminate the broader transparency limits associated with Performance Max. It makes creative inspection easier, but it should not be mistaken for a complete view of the system’s selection and delivery decisions.

Key takeaways

You can open placement previews by clicking an image or video directly in the Performance Max Asset Groups table.
Review every changed asset and every presentation available to you; one acceptable rendering does not validate the whole asset group.
Check composition, legibility, brand recognition, message consistency, and destination alignment in the same order every time.
Record Pass, Revise, or Block at the asset level, with the visible reason and required correction.
Use previews for creative quality assurance, not as proof of delivery, performance, or causation.

For your next creative refresh, make preview review a release gate: no changed image or video leaves QA without a recorded pass or revision. The interface saves the clicks. A consistent checklist turns those saved clicks into fewer preventable creative mistakes.

References

Search Engine Land – Google adds one-click ad previews to PMax

January 28, 2026

Paid Search Readiness: Fix the Account or Build Demand?

Your paid search campaigns can look efficient and still refuse to grow. That does not automatically mean bids are too low or automation is too timid. You may have a readiness problem inside the account, or you may have reached the amount of demand currently available to capture.

Those constraints need different fixes. Better tracking, bidding and landing-page controls can repair an account that is not ready to scale. Demand generation is the answer when a healthy account has already captured most of its worthwhile opportunity. Diagnose that distinction before you increase budgets or enable Google AI Max.

Diagnose the constraint before you pay to expand it

Paid search converts expressed intent. It can reach someone who searches for a problem, product, category or brand, but additional budget cannot manufacture an unlimited supply of eligible searches. At the same time, an underspending campaign is not automatically demand-constrained. Weak measurement, low rank, restrictive targeting, poor relevance or an unsuitable offer can produce the same symptom.

Read the account in a fixed order: measurement first, existing auction opportunity second, relevance and rank third, and market demand last. If you reverse that order, you can mistake a repairable campaign problem for a small market.

What you see	Likely constraint	What to do next
Primary conversions are duplicated, inflated or disconnected from qualified outcomes	Measurement readiness	Repair the conversion signal before changing bids, budgets or targeting
Profitable, high-intent campaigns lose impression share because of budget	Capture budget	Protect and fund proven demand before paying for expansion
Campaigns have room in their budgets, but rank, relevance or landing-page performance is weak	Campaign execution	Improve the ads, structure, offer and landing path before broadening reach
Broadening queries adds traffic but degrades lead quality or unit economics	Relevance or market fit	Find where intent breaks instead of treating more reach as progress
Tracking is trusted, proven demand is funded, relevance is healthy and eligible traffic remains limited	Demand ceiling	Create demand outside paid search and build a deliberate route back into capture campaigns

Budget loss deserves particular attention. If your best keywords are already missing impressions because their campaigns are capped, an expansion layer can compete with the demand you already know how to convert. The safer sequence is to fund proven keywords before giving AI Max room to experiment.

Do not use account-wide averages for this diagnosis. Brand, non-brand, competitor, Shopping and remarketing activity can have different constraints. A strong branded campaign can hide weak generic acquisition, while a broad campaign can consume budget without proving that it created incremental demand. Classify campaigns separately, then decide where money should move.

Pass the AI Max readiness gate

AI Max is an expansion mechanism, not an account repair tool. It uses signals beyond conventional keyword targeting to decide when an ad may be relevant. That gives the system more freedom, which means weaknesses in your conversion data, bidding or page controls can spread farther and consume budget faster.

Make the conversion signal worth optimizing

Accurate conversion tracking is the first gate because automated bidding treats your selected outcomes as its definition of success. If a low-quality form submission, duplicated purchase or easy micro-conversion is marked as primary, the system can optimize efficiently toward the wrong result.

List every primary conversion action and identify the business outcome it represents.
Check whether one customer action can trigger more than one primary conversion.
Separate diagnostic events, such as page views or button clicks, from outcomes you are willing to buy.
For lead generation, compare platform conversions with qualified leads or later pipeline stages rather than form volume alone.
For value-based bidding, confirm that the values distinguish more valuable outcomes instead of assigning arbitrary numbers to every action.
Resolve unexplained jumps, missing imports and tracking changes before using the affected period as a baseline.

This is also where demand-generation measurement and search optimization must stay separate. Reach, video engagement and content consumption can help you understand whether a message is landing, but they should not become primary paid-search conversions unless they are genuinely the outcomes you want bidding to purchase.

Align automated bidding with the economic goal

A sensible AI Max test needs a conversion-focused automated bid strategy. Target CPA can fit a campaign where conversions have broadly similar value and you know an acceptable acquisition cost. Maximize Conversion Value fits only when the submitted values are trustworthy enough to guide trade-offs. The strategy name matters less than whether its objective matches the result your business actually values.

Where you already know viable unit economics, a target can give the system a clearer boundary than an unconstrained maximize strategy. Do not change the bid strategy, conversion definition and targeting expansion at the same moment. If performance moves, you will not know which change caused it.

Check data volume, broad match history and budget pressure

A practical screening heuristic is to start with a campaign producing at least 30 conversions per month, with greater confidence around 100 or more. These are test-selection heuristics, not guaranteed performance thresholds or formal Google minimums. If your campaign sits below the lower figure, consolidation or a conventional campaign improvement is usually a more informative next move than giving automation a larger search space.

Past broad match performance is another readiness signal because AI Max effectively broadens the system beyond exact keyword control. A campaign that has already converted relevant broad-match traffic at acceptable economics gives you evidence that the account can tolerate looser matching. If broad match has failed, determine whether query relevance, ad-group structure, creative, landing pages or conversion quality caused the failure before adding another expansion layer.

Your first test candidate should therefore meet five conditions: trusted primary conversions, conversion-focused bidding, enough recent conversion volume to evaluate, positive broad match history, and no meaningful budget loss on the proven demand you need to protect.

Control landing pages and generated assets before launch

URL expansion lets Google select a page it considers relevant when AI Max triggers an ad. That can improve message-to-page matching on a well-organized commercial site. It can also send paid traffic to policy pages, thin informational content, outdated offers or the wrong geographic page.

Build exclusions before you enable the feature. Remove pages that cannot complete the intended conversion, locations the campaign does not serve, obsolete products, internal search results and any page whose claims or offer conflict with the ad. If you rely on dedicated local landing pages, confirm that expansion cannot replace them with a page for another market.

Apply the same discipline to automatically created assets. Generated messaging can broaden coverage, but irrelevant sitelinks or incompatible callouts can weaken an otherwise suitable ad. Review the source pages the system can draw from, remove obsolete copy, and define brand or compliance boundaries before the test begins.

One distinction prevents a common strategic error: AI Max is not required for ads to appear in AI Overviews. Broad match keywords can already make an ad eligible there. Enable AI Max because you have a controlled case for incremental conversions, not because you assume it is an admission ticket to AI-generated search experiences.

Build demand and capture as one connected system

Once measurement is reliable, valuable auction opportunity is funded and campaign execution is healthy, the remaining ceiling may sit above paid search. Search and Shopping eventually stop scaling when they are expected only to capture demand and too little activity is creating new interest for them to capture.

Demand generation is not simply buying broad reach. Its job is to make more suitable buyers recognize a problem, understand a category or remember a brand, then give that changed intent somewhere useful to go. If the demand message and the search experience are planned by different teams, the handoff often breaks between those two moments.

Define the demand message in one sentence: the problem the buyer should notice, the outcome worth pursuing and the category or solution that makes the outcome possible.
Map the searches that message could reasonably produce. Separate brand terms, category terms, problem-led terms and product terms rather than assuming every exposed person will search for your brand.
Create a capture route for each valuable intent. The route should include an eligible campaign, relevant ad or product presentation, and a landing page that continues the same promise.
Keep the language continuous. If demand creative teaches one category concept but paid search and the landing page use unrelated terminology, the buyer has to translate your message for you.
Feed search-term language back into demand creative. Queries reveal how people describe the problem after interest forms, which can expose gaps between your internal vocabulary and the buyer’s words.
Report brand and non-brand search separately. A blended total can make demand creation look efficient simply because existing branded demand converts cheaply.

Measure the handoff without giving one channel all the credit

Measure delivery, demand signals and commercial outcomes as different layers. Delivery tells you whether the intended audience had a chance to receive the message. Directional demand signals can include changes in branded searches, direct visits, returning visitors or relevant category searches. Commercial outcomes include qualified leads, purchases, revenue or another verified business result.

A rise in branded search after a demand campaign is useful evidence, but timing alone does not prove causation. Seasonality, publicity, competitor activity and other media can move the same signal. Use a credible control or holdout where your scale permits it, and keep the claim directional where it does not.

Attribution settings can also obscure the handoff. A search click near the end of a journey may receive credit for a conversion even when another channel created the interest. That does not make search unimportant; it means capture efficiency and demand creation answer different questions. Judge paid search on whether it captured intent economically, and judge demand activity on whether it increased the supply or quality of that intent.

Test AI Max as an expansion layer, not a rescue plan

Start with a non-brand campaign. Brand traffic can make expansion look more efficient than it is, and AI Max performance around brand queries has been inconsistent. Choose one proven, conversion-rich ad group instead of switching on account-wide automation. Ad-group-level activation through Google Ads Editor makes that controlled starting scope practical.

Write the hypothesis. State what incremental opportunity you expect AI Max to find and which conversion outcome must improve.
Record the baseline. Capture conversion volume, conversion value, CPA or return, query mix, landing-page mix and downstream lead quality for the selected ad group.
Choose the candidate. Use a non-brand ad group with successful broad match behavior, sufficient conversion volume and no unresolved tracking issue.
Set the boundaries. Finalize URL exclusions, geographic controls, brand restrictions, negative concepts and asset-review rules before launch.
Hold unrelated changes. Avoid simultaneous restructuring, conversion-action changes or major landing-page rewrites unless a safety, compliance or budget issue requires intervention.
Monitor what expanded. Look beyond the topline result to the queries, pages, locations and assets receiving the additional spend.
Judge incrementality and quality. More platform-reported conversions are not enough if they replace branded conversions, lower lead quality or move spend away from better existing demand.

Define stop conditions before the test starts. Pause or narrow the rollout if it sends traffic to incompatible pages, shifts substantial budget away from proven demand, produces irrelevant query themes, or increases nominal conversions while qualified outcomes deteriorate. Predefined conditions stop the team from rationalizing weak traffic after money has already been spent.

A successful result is not simply that AI Max spent more. It is that the selected ad group found additional, relevant conversions or conversion value within the economics you set, without hiding losses in brand mix, lead quality or landing-page selection. If it passes, expand one controlled unit at a time. If it fails, the query and page data should tell you whether to repair relevance, tighten controls or return budget to demand creation.

Key takeaways

Paid search readiness starts with trusted conversion tracking, aligned automated bidding, sufficient data and funded high-intent demand.
An underspending campaign does not prove that demand is exhausted; measurement, rank, relevance and targeting must be ruled out first.
For an initial AI Max test, 30 monthly conversions is a practical screening heuristic, while 100 or more provides a stronger data base; neither is a guaranteed Google threshold.
Positive broad match history is an important readiness signal because AI Max expands beyond tight keyword control.
AI Max is not required for ad eligibility in AI Overviews; test it for incremental conversion opportunity, not access.
When a healthy search account reaches its capture ceiling, connect demand messages to likely queries, eligible campaigns and matching landing pages.

Open your last stable reporting window and classify each campaign as measurement-constrained, budget-constrained, execution-constrained or demand-constrained. Fix the first three before expanding automation. If the remaining limit is demand, build the message-to-query-to-landing-page handoff and let paid search capture the intent it creates. Only then give AI Max a small, controlled opportunity to prove that it can add something genuinely incremental.

References

January 27, 2026

Google Ads Workflow Bugs: A Practical Recovery Playbook
A Google Ads control disappears, a Performance Max edit refuses to save, or the interface leaves you unsure whether a change went through. Your first impulse may be to keep clicking. That can turn a platform problem into an account-management problem: duplicated work, undocumented decisions, or assets left in the wrong state.

The safer response is a short incident workflow. Confirm what failed, preserve the intended change, choose the narrowest viable workaround, and verify the result from the account itself. This playbook gives you that process for two especially disruptive failures: inaccessible account notes and blocked Performance Max asset-group edits.

Triage the failure before you touch the campaign again

Not every broken-looking screen represents the same kind of failure. Google Ads workflow bugs generally demand different responses depending on whether the interface has hidden a control, rejected a write, or left the saved state uncertain.
- Missing control: A function you normally use is absent, but the underlying capability may still be available through another part of the interface. In affected accounts, the Add note option has disappeared intermittently from its usual popup.
- Rejected write: The control is visible, but the platform will not accept the change. Performance Max asset-group edits have been blocked by the message "An error occurred. Please try again later. Value is required", even when the required fields appear complete.
- Uncertain persistence: You submitted a change but cannot tell whether the account retained it. Treat the change as unverified until you reopen the relevant object and read the saved values back.
Start with a read-only check. Confirm the account, campaign, asset group, date range, and screen you are viewing. Refresh once, reopen the object, and try a fresh browser session if that is available to you. Record the exact error or missing control. Do not broaden the edit merely to see whether a different version will save; changing extra fields creates more variables and makes a rollback harder.

Scope matters. If Add note is missing only from one popup but the Notes panel still works, you have a navigation failure with a usable route around it. If every attempted Performance Max asset-group edit receives the same validation error, you have a blocked write path. If another asset group saves normally, narrow the investigation to the failing object and its intended values before assuming the whole account is affected.

For the blocked Performance Max behavior, Google acknowledged the issue without providing a repair timeline. That makes waiting an operational decision, not a troubleshooting step. Base it on the urgency of the campaign change.

Key takeaways
- Classify the problem as a missing control, rejected write, or unverified save before choosing a workaround.
- Capture the intended before-and-after state before retrying through another interface.
- For missing account notes, try an existing note in the visible date range, then open Notes from the More menu.
- For blocked Performance Max asset-group edits, use Google Ads Editor as the alternate editing route and upload the necessary change.
- A successful click or upload is not the finish line. Reopen the object, confirm the stored values, and document the verification.
Use the narrowest workaround that preserves control

A workaround should restore one blocked capability without quietly expanding the scope of your change. Before using one, write down the current state, the exact state you want, and the reason for the change. That gives you a comparison point if the alternate route behaves differently from the web interface.

When Add note is missing

The notes failure is intermittent, so a missing button does not necessarily mean account notes are unavailable everywhere. Work through the available routes in this order:
1. Record the date range currently displayed. The first workaround depends on whether an existing note is visible inside that range.
2. Click an existing note. In some affected accounts, opening an existing note reveals the option to add another one. This route cannot help when the visible date range contains no note.
3. Open the More menu and select the Notes panel. The Notes panel has continued to expose note creation in some cases even when the usual popup does not.
4. If neither route works, put the annotation in your controlled external change log immediately. Include enough context to backfill the account note later without relying on memory.
5. When note creation becomes available again, enter the account note and mark the external record as backfilled. Do not silently delete the incident record; it explains why the annotation was entered through a delayed workflow.
An external log is a continuity measure, not an equivalent replacement for an account note. It may have different visibility, retention, and access controls. Use the system your team already governs, and make the affected Google Ads account and change easy to identify.

When a Performance Max asset group will not save

A validation message can tempt you to refill fields, remove assets, or rebuild the asset group. If the required values already appear present, preserve your intended edit before trying anything else. Repeatedly reconstructing the change in the same failing interface adds effort without establishing that the write path works.
1. Copy the intended values into your incident record. Identify the account, campaign, asset group, fields being changed, and business reason.
2. Capture the exact error and the state visible after the failed save. Do not mark the edit as applied.
3. Move only the necessary edit to Google Ads Editor. Google Ads Editor has provided a working route for making and uploading affected asset-group changes.
4. Review the pending change before upload. Check that you are editing the intended asset group and that unrelated fields are not included.
5. Upload the change, then reopen the relevant asset group and compare the stored values with your intended-state record.
6. Document the verification separately from the upload. If the values do not match, stop and investigate rather than submitting the same edit repeatedly.
This alternate route matters most when an asset is outdated or a correction is time-sensitive. For a discretionary refresh or test, deferring the change may be safer if your team cannot confidently review and verify an Editor upload. The urgency of the business change should determine whether you route around the bug; the mere existence of a workaround should not.

Protect the audit trail while the interface is unreliable

Account notes are part of the account’s operational memory. When access to them fails, tracing optimizations and diagnosing later performance shifts becomes harder. The documentation gap is therefore part of the incident, not a minor inconvenience beside it.

Keep two records distinct. The change record explains what you intended to alter in the campaign. The incident record explains why the normal Google Ads workflow could not be used. A single note such as "Google Ads was broken" cannot answer either question well enough during a later review.

A useful incident record contains:
- Location: Google Ads account, campaign, asset group or reporting view, and the relevant date range.
- Intended change: The before state, after state, and business reason.
- Failure: Missing control or exact validation message, affected interface, and what happened after the attempted save.
- Scope check: Whether the behavior appeared limited to one object, one account, or the route you were using.
- Workaround: Existing-note route, Notes panel, Google Ads Editor, external annotation, or a deliberate decision to defer.
- Verification: What you reopened, which values or note you confirmed, and who performed the check.
- Ownership: Who will backfill a delayed note, recheck a deferred change, or close the incident.
Use explicit statuses so nobody has to infer progress from a chat thread. Four states are enough: planned, submitted, verified, and documented. A failed web save remains planned. An Editor upload is submitted. It becomes verified only after a read-back confirms the correct asset group values. It becomes documented when the change and the workflow incident are recorded in the places your team uses.

This distinction also prevents duplicate work during handoffs. If one operator sees "submitted" rather than "verified," the next action is inspection, not another upload. If the record says "documented externally; account note pending," the next action is a controlled backfill when Notes becomes available.

Verify the account state, not the success message

The reliable endpoint of a Google Ads change is observable account state. A button click, lack of an error, or completed upload tells you that an action was attempted. It does not replace checking what the platform retained.
1. Reopen the exact object. Navigate back to the relevant account, campaign, and asset group rather than relying on the editing screen’s last visible state.
2. Read back every changed field. Compare it with the intended-state record. Do not verify one headline and assume the rest of the asset group followed.
3. Confirm note placement. If you restored an account note, use the relevant date range and make sure the annotation is visible where another operator would look for it.
4. Check recent affected work. After encountering the Performance Max error, revisit recent asset-group changes to confirm that they actually saved.
5. Close the loop. Record the verified state, resolve any temporary external-note task, and tell the next operator which editing route is currently dependable.
Build these steps into the workflow before the next failure. Save the incident fields as a reusable template, give alternate-route uploads an explicit reviewer when your normal controls require one, and make read-back verification mandatory after any error or workaround. A resilient Google Ads operation does not assume the interface will always behave; it makes a broken interface visible, bounded, and recoverable.

References
- CrushPress.AI – Frustration Grows: Google Ads Bug Hinders Note Accessibility
- CrushPress.AI – Google Ads Glitch Halts Performance Max Edits: What to Do
January 23, 2026
Agentic AI: Transforming PPC with Smart Automation

I’ve watched automation quietly transform PPC management over the years with rules, scripts, and API-driven workflows in Google Ads.

Like many other marketers, I’m already very comfortable with automated bidding, data-driven optimization, and a suite of other AI-powered enhancements. But there’s a new shift on the horizon that’s set to redefine how we manage and optimize PPC campaigns.

This time, I’m talking about AI agents and vibe coding. These innovations are ushering in a more autonomous mode of working where AI takes the lead in execution, allowing marketers like me to focus on strategy and creativity.

This evolution promises unprecedented efficiency and flexibility, redefining effective PPC management.

Agentic AI: Google Ads’ Game-Changing Feature

In November 2025, Google rolled out its Agentic Ads Advisor, powered by advanced Gemini models. This tool helps advertisers like me uncover insights and boost campaign performance effortlessly.

Google positions Ads Advisor as an AI partner that enhances campaign management by understanding business contexts, simplifying tasks, and learning from interactions to deliver better outcomes.

However, the pressing question remains: What functionalities should an agentic AI tool embody?

It should function as an autonomous agent, surfacing information as needed but also operating independently. It should identify opportunities for enhancing campaign setups, assets, ad copy, and more.

An ideal agentic AI wouldn’t just make recommendations but also implement essential changes on its own.

Integrating Agentic AI in PPC Workflows

Agentic AI should ideally make decisions autonomously without needing constant human input, thereby managing, adjusting, and optimizing campaigns as they run.

Beyond just advice or reporting, its real value lies in managing bidding, ad placements, and creative testing in real-time, based on live data, seasonality, and user behavior trends.

With agentic AI handling more operational tasks, I can direct my efforts toward strategic decision-making.

The competitive edge will increasingly rely on strategy rather than tools, focusing on marketing fundamentals like positioning, value propositions, and brand awareness.

Read more: Agentic PPC: What Performance Marketing Could Look Like in 2030

Why Agentic AI is Key for Advanced PPC Marketers

Agentic AI appeals to experienced PPC marketers like myself because it scales campaigns without compromising strategic control, proving to be a true game-changer.

With real-time optimization, data-driven creativity, and reduced human error, it redefines my role by allowing more time for strategy rather than execution.

Despite its capabilities, informed oversight is essential to ensure alignment with broader marketing objectives, highlighting the need for ongoing professional engagement.

Agentic AI isn’t replacing PPC professionals. Instead, it extends our capabilities, reduces manual effort, and facilitates better outcomes with minimal friction.

Vibe Coding: Creating Your Marketing Toolbox

In tandem with agentic AI, vibe coding is redefining how I work with AI-powered platforms, allowing me to create personalized, intuitive marketing tools and campaigns.

Tools like Cursor and AI Studio have enabled me to articulate and realize specific needs seamlessly, even without being a developer.

Incorporating vibe coding led me to build an SEO schema markup generator, an SEO audit tool, and a marketing idea generator, proving its practical value in my professional life.

The possibilities expand when combining vibe coding with agentic AI, empowering marketers to engineer their AI agents tailored for PPC work.

With this combination, I integrated these tools effectively within my marketing workflows, enhancing performance and strategy development at scale.

Explore further: How Vibe Coding is Changing Search Marketing Workflows

The Future: Navigating PPC with Agentic AI and Vibe Coding

Agentic AI and vibe coding present immense opportunities to streamline PPC operations, enhance performance, and maintain competitiveness in a fast-evolving landscape.

The future is about leveraging these technologies for more autonomous, data-driven, and personalized marketing strategies that benefit both internal teams and customers alike.

As a PPC professional, it is crucial to embrace these advancements, ensuring adaptability and continued relevance in an AI-powered future.

Follow experts like Alfred Simon, Mike Rhodes, and Ales Sturala to see practical applications of these innovative technologies in real-world scenarios.

Inspired by this post on Search Engine Land.

January 23, 2026

Google Antitrust Data and Ad Remedies: What to Prepare

If you manage paid search, organic visibility, or a search product, the dangerous mistake is to model Google’s antitrust remedies as one switch. Access to an index, access to interaction data, syndication of results, and syndication of ads create different opportunities, controls, and failure modes.

Start with timing. Google sought to pause parts of the remedy while its appeal was pending, while the challenged search and ad syndication provisions could operate for five years. A remedy can appear in a judgment without being available in a partner product. Before changing a contract, budget, privacy policy, or technical integration, verify the operative order, effective date, and implementation terms with the relevant partner and legal counsel.

The remedies split into four operational layers

The phrase “data sharing” hides several systems that should not share one forecast. The court’s Section IV framework reaches index information, search-interaction data, core results, and ads. Each layer answers a different competitive problem and creates a different kind of exposure.

Remedy layer	What could be shared or syndicated	What it means operationally
Web index data	URLs in Google’s index, a DocID-to-URL map, and metadata such as crawl frequency	A qualifying rival could reduce the work needed to discover and prioritize pages. This does not create a public index dashboard for every publisher or SEO.
Search-interaction data	Search logs used by Glue and RankEmbed, including detailed interaction information	A recipient would gain potentially valuable signals, but would also need controls for authorized use, privacy, retention, security, and downstream access.
Core search syndication	Google’s core results and search features for qualifying competitors for five years	A third-party surface could display Google-derived results without independently reproducing the same index and ranking stack.
Ad syndication	Google search ads under court-constrained commercial terms, with query and pricing information involved in operating the relationship	A competitor could add monetization more quickly, while advertisers would face another distribution path whose traffic quality and controls must be evaluated.

The first important distinction is sharing versus publishing. A requirement to serve qualified competitors is not a promise that advertisers, agencies, site owners, or the public will receive raw Google data. Unless your company satisfies the applicable qualification requirements and signs the necessary terms, assume you have no direct access.

The second distinction is syndication versus source-code transfer. Google is not warning only about someone receiving auction software. Its position is that repeated observation at large scale could reveal targeting logic, relevance factors, and auction behavior. When you assess an integration, separate three things: data expressly delivered under contract, information visible during normal operation, and patterns a high-volume participant might infer.

The third distinction is direct distribution versus a distribution chain. The judgment permits competitors to sub-syndicate Google ads to third parties. That makes the identity, incentives, and controls of downstream participants part of the product. A direct partner’s security review is not enough if several other businesses can receive the inventory or related data.

Do not translate a requirement for terms no less favorable than existing agreements into one public price. Google’s current arrangements are customized around traffic quality and technical configuration. Applying comparable economics to materially different partners could produce unpredictable volume or poor pricing. Evaluate the effective cost and quality of each route, not the legal phrase in isolation.

The alleged harms are testable mechanisms, not settled outcomes

Two transparent search and advertising pipelines are examined side by side with sensors, ranking modules, distribution junctions, and privacy filters in a digital laboratory.

Google is the party seeking to pause these obligations, so its claims should be treated as arguments from an interested participant. They still identify concrete failure mechanisms worth testing. The disciplined response is to build controls around those mechanisms without assuming that every predicted harm will occur.

Index access could change discovery and spam incentives

A complete URL map could let a competitor avoid much of the work involved in discovering the web. Crawl-frequency metadata could reveal which areas Google revisits most often. Google also argues that exposing spam-related scores or signals could help bad actors learn what its systems detect and then adjust their tactics.

Those mechanisms do not prove that an authorized recipient will publish more spam, and they do not mean SEOs will receive a usable ranking score. Do not rewrite content around rumored fields or secondhand interpretations of a dataset. Establish a pre-change baseline instead: indexed landing pages, organic impressions, crawl activity, referring surfaces, conversions, and obvious spam anomalies. Match the comparison period to your site’s publishing cycle and seasonality.

If visibility changes later, identify the result’s provenance before diagnosing a ranking change. A competitor may have crawled the URL independently, received it through syndication, or generated an answer from another system. Those paths can produce a similar screen for the user while requiring completely different corrective actions from you.

Ad fraud risk rises when the traffic chain becomes opaque

Large-scale ad delivery can expose more behavioral patterns than a small integration. Google argues that repeated queries could help outsiders infer aspects of targeting, relevance, and auction operation. Sub-syndication adds another problem: the company with the direct agreement may have less incentive or ability to police every downstream placement.

One abuse pattern described by Google involved adding the names of wealthier countries to queries while routing lower-cost international traffic to ads. The resulting click-fraud losses were allegedly measured in tens of millions within a couple of months. That example does not establish that new syndicators will behave the same way. It does show why query integrity, geography, placement identity, and conversion quality belong in the same fraud review.

Do not label every conversion decline as fraud. We would require at least two independent anomalies before escalating: a click-volume change outside the campaign’s normal range, a mismatch between click and conversion geography, systematic additions to query text, an unexplained shift in partner volume, or a sharp deterioration in post-click outcomes. Preserve the raw evidence, isolate the suspect route, and use the contractual dispute process before making a broad account change.

Nominally favorable pricing can still produce weak economics

A partner can receive apparently favorable terms and still send traffic that performs poorly. Price per click, revenue share, and conversion rate describe different parts of the transaction. Unpredictable query volume can also turn an acceptable test into an uncontrolled budget event.

Compare syndicated routes using business outcomes after conversion lag, invalid-traffic adjustments, refunds, and downstream fees. Keep each new route in its own reporting line. If it is mixed into an established campaign, aggregate performance can hide a low-quality partner until substantial spend has already moved.

Access to interaction data does not create permission to reuse it

The search logs at issue include detailed user interactions. Google says compelled sharing could create privacy, misuse, and leakage risks even when contracts restrict recipients. Detailed data is not necessarily directly identifiable, but that distinction cannot be assumed without a data dictionary and a review of the actual fields.

Before connecting any newly available search dataset to analytics, a CRM, an advertising profile, or an AI training pipeline, document its permitted purpose, level of aggregation, retention period, deletion process, security controls, audit rights, and downstream-transfer rules. New access is not user consent. If the legal basis or contractual permission is unclear, keep the data outside production systems until privacy and legal reviewers approve the intended use.

Build a readiness plan without betting on the appeal

Hands organize blank contract materials, API modules, data controls, a sandbox model, monitoring lights, and contingency paths on a conference table.

You do not need to predict the final legal outcome to prepare. Most of the useful work is reversible: clarify ownership, record the baseline, define acceptance gates, and make new traffic or data separable from existing operations.

Create a remedy register. For each obligation, record its legal status, effective date, duration, eligible recipient, covered data or inventory, downstream rights, internal owner, and the evidence supporting each entry. Use separate labels for ordered, operative, and commercially available; they are not synonyms.
Map your current chain. For ads, connect each campaign to its network, direct partner, known sub-partners, placement or referrer data, billing path, and conversion pipeline. For organic and AI visibility, connect each URL to the crawler, index, display surface, referral, citation, and measured outcome. Mark every unknown rather than filling it with an assumption.
Capture a baseline before exposure changes. Preserve traffic quality, conversion lag, click and conversion geography, query themes where available, invalid-traffic adjustments, indexed URLs, crawl patterns, organic conversions, and referring surfaces. Use enough history to represent your normal seasonality.
Set a contractual gate. Require clear rules for data purpose, retention, deletion, audits, incident notice, sub-syndication, query transformations, invalid traffic, refunds, and the ability to pause distribution. A promise of comparable terms is not a substitute for these controls.
Isolate every new test. Give new syndicated inventory a separate campaign or reporting segment, distinct tracking, and a budget limited to what the business can afford to lose during validation. Do not blend it into a core acquisition channel until traffic quality and reconciliation have been demonstrated.
Plan around states, not dates. Model a continued stay with no operational access, a constrained implementation with direct qualified partners, and a broader implementation that includes downstream syndication. Attach a measurable trigger to each action, such as an operative order, published qualification rules, a signed agreement, or a technically verified feed.
Prepare an incident path. Name the person who can pause spend or disconnect data, identify which logs must be preserved, define who reviews suspected fraud or privacy exposure, and document the notification and refund process. Rehearse that path before a high-volume integration starts.

Questions paid media teams should ask before buying inventory

A new inventory offer should not move into campaign setup until the provider can answer these questions in writing:

Is the provider a direct Google syndication partner, a sub-syndicator, or another downstream participant?
Which domains, apps, result pages, and additional partners can display the ads?
Can the provider report traffic, costs, invalid-click adjustments, and conversions at the same level at which you can pause or dispute traffic?
Can query text be modified, expanded, or combined with geographic terms before the ad request is made?
How are click geography, user location, and conversion geography validated and reconciled?
How do traffic quality and technical configuration affect pricing, and what happens if volume differs materially from the forecast?
Which party investigates fraud, how quickly can delivery be stopped, and when are credits or refunds available?

If a provider cannot identify the inventory chain or explain its dispute and refund rules, the safe decision is not to spend through that route yet. A small isolated test is appropriate only when the loss is bounded and the business can measure the result independently.

What SEO, AEO, and GEO teams should measure differently

Search syndication makes provenance more important than surface appearance. A URL displayed by a competitor may have arrived from that competitor’s crawler or through Google-derived results. An AI answer may then cite, summarize, or ignore that result through another decision process.

Classify visibility as independently crawled, independently indexed, syndicated, or cited by a generative system. Do not collapse those states into one rank-tracking field.
Track display visibility and referral traffic separately. A syndicated result could appear without a distinctive crawl from the service that displays it, while a crawl does not prove the URL was shown to users.
Do not assume inclusion in Google’s index guarantees inclusion in a competing result set or citation in an AI answer. Discovery, indexing, ranking, syndication, and generative citation remain separate decisions.
When a snippet or answer is wrong, capture the query, URL, surface, wording, and time. Determine whether the error came from the upstream result, a downstream transformation, or the generative layer before changing the page.
Treat any new index map or interaction dataset as governed data. Verify provenance, contractual rights, freshness, permitted use, and deletion requirements before incorporating it into an SEO tool or model.
Keep canonical URLs, crawl directives, structured data, and core entity facts consistent. These controls will not determine every downstream use, but they give independent and syndicated systems a stable representation to work from.

Do not apply noindex, change canonical targets, or block crawlers merely in response to a rumored implementation. Those changes can remove legitimate visibility. Confirm the actual behavior first, then use a reversible test on a limited set of non-critical URLs if a platform-specific control needs validation.

Key takeaways

Google’s antitrust remedies involve four distinct layers: web index data, search-interaction data, core result syndication, and ad syndication.
Qualified access is not public access, and syndication is not the same as receiving Google’s source code.
Google’s warnings about spam, privacy, fraud, reverse engineering, and pricing are contested claims, but each describes a mechanism you can monitor and control.
Advertisers should require visibility into the complete distribution chain, isolate new inventory, and reconcile clicks with geography and business outcomes.
SEO, AEO, and GEO teams should distinguish independent crawling, indexing, syndication, and generative citation before diagnosing a visibility change.
No budget, contract, data-use, or technical decision should rely on the remedy headline alone; verify the operative order and implementation terms.

Your next move should be a remedy register and a clean performance baseline, not a speculative budget reallocation or content rewrite. When an operative requirement or real partner offer appears, insist that the data and traffic chain be put on paper. That gives you evidence for a fast decision without making the business depend on the outcome of an appeal.

References

January 22, 2026

Google Demand Gen Commerce Updates: A Practical Playbook

You may be looking at Demand Gen because paid social is getting harder to scale, or because YouTube creates attention that your conversion reports struggle to explain. Google’s commerce updates give you three new levers, but each solves a different problem.

The practical question isn’t whether to adopt every new feature. It is whether shoppable connected TV, dynamic travel offers, or branded-search attribution closes a specific gap in your customer journey. Start there, and you can test the updates without turning a product announcement into an open-ended budget request.

What changed, and what each update actually does

The three additions sit under the same Demand Gen umbrella, but they are not interchangeable:

Shoppable CTV lets viewers browse and purchase products from YouTube ads on connected TVs. It changes the response path by bringing product actions into an environment that has traditionally been treated as upper-funnel video.
Travel Feeds let advertisers connect Hotel Center feeds to dynamic video ads containing current pricing, ratings, and availability. They change how hotel offers are assembled and kept relevant.
Attributed Branded Searches provide visibility into campaign-driven brand search activity on Google and YouTube. This changes what you can measure, but activation requires help from a Google representative.

The first two features change what a prospective customer can see or do. The third adds an attribution signal. That distinction matters: a new measurement report does not improve the buying experience, and a shoppable ad does not by itself prove that the resulting sales were incremental.

Match the feature to the constraint in your funnel

Three connected scenes show television shopping, adaptive travel offers, and a search-to-purchase path overcoming different journey obstacles.

Use shoppable CTV when the missing link is product action

Shoppable CTV is most relevant when viewers understand your product from video but have no natural next step from the television screen. The testable idea is simple: can adding a product interaction to that viewing experience produce more conversions without weakening return on investment?

Do not begin by moving a large video budget. Begin with a product set that makes the test interpretable. Favor products that are easy to recognize visually, have a clear use case, and are supported by dependable price and availability data. The item presented in the ad should also be easy to find at the destination. A viewer who meets a different product, price, or offer after acting on the ad has not experienced a media failure; they have experienced a broken handoff.

Make the product and its main benefit understandable at television viewing distance. Do not rely on dense copy or small interface details to explain the offer.
Check the full path from the video impression to the product action and final destination. Look for changes in item identity, price, availability, or promotional language.
Judge the test primarily on conversions, conversion value, CPA, or ROI, according to your business model. Video engagement can diagnose creative response, but it should not replace the commercial outcome.
Document what adding CTV is expected to change. If the hypothesis is merely that the campaign will reach more people, the test is too vague to justify a performance conclusion.

Use Travel Feeds when changing offers make creative stale

Travel Feeds address a different source of friction. Hotel pricing and availability can change faster than a team can rebuild conventional video assets. Connecting Hotel Center allows those offer details, along with property ratings, to populate dynamic video ads.

The feed becomes part of the advertising experience, so feed quality is campaign quality. Before increasing spend, sample the properties and offers being promoted. Compare the price, rating, and availability presented in the ad journey with what a traveler encounters when moving toward a booking. Decide how your team will identify unavailable properties, inconsistent prices, and destinations that no longer match the promoted offer.

Audit Hotel Center data before evaluating the creative. Incorrect or incomplete offer data can make capable media look ineffective.
Review a representative mix of properties rather than checking only the most visible or highest-volume listing.
Assign ownership for feed corrections. A media buyer who can identify a mismatch but cannot route it to the person responsible for hotel data will repeatedly diagnose the same problem.
Keep the booking outcome as the primary metric. Dynamic assembly reduces creative and offer friction; it does not remove the need to evaluate booking quality and campaign economics.

Use Attributed Branded Searches when last-click reports hide influence

Demand Gen can affect what people search for after seeing an ad, even when the eventual search or conversion does not look like a direct response to the original impression. Attributed Branded Searches are designed to expose that brand-search activity across Google and YouTube.

That makes the metric useful, but not equivalent to revenue. A rise in attributed brand searches can indicate that the campaign created interest. It cannot, on its own, tell you whether those searches produced profitable, incremental customers. Read it beside conversions, conversion value, CPA, ROI, and any customer-quality measure your business already trusts.

Because a Google representative must activate the feature, treat access as a pre-launch dependency rather than an item to chase after the campaign ends. Ask the representative to confirm eligibility, the activation date, the metric definition, the reporting location, the applicable attribution window, and any limitations that could affect interpretation. Record those answers with the campaign brief so nobody later compares two reports built on different rules.

Build the measurement plan before you move budget

A desk with connected devices, interaction tokens, measurement checkpoints, and budget tokens waiting behind a transparent gate.

The updates make Demand Gen more measurable, but more metrics do not automatically create a clean test. You still need a decision framework that separates commercial outcomes from diagnostic signals.

Write one falsifiable hypothesis. For example: adding TV screens will increase conversions while maintaining ROI, or feed-driven hotel video will increase bookings without exceeding the campaign’s CPA constraint. Avoid a bundle such as improving awareness, engagement, sales, and efficiency at once.
Select one primary outcome and one guardrail. The outcome might be purchases, bookings, conversion value, or another completed business action. The guardrail might be CPA or ROI. Branded search and video engagement should remain supporting signals unless they are genuinely the business objective.
Lock the comparison rules. Use consistent conversion actions, value rules, attribution settings, and reporting periods when comparing Demand Gen with an existing campaign or channel. If those controls cannot be aligned, label the comparison as directional rather than causal.
Record operational diagnostics. For commerce, inspect product continuity and availability. For travel, inspect Hotel Center data and the offer-to-booking path. For brand measurement, confirm that Attributed Branded Searches were active during the period being evaluated.
Define the next decision before results arrive. State what would justify a limited scale-up, what would trigger a feed or landing-path repair, and what would cause the test to stop. You do not need to invent universal thresholds; use the economics your account must already meet.

Once the campaign is running, interpret combinations of signals instead of celebrating one favorable number:

Signal pattern	What it may mean	What to do next
Conversions rise while ROI holds or improves	The commerce path may be creating useful additional demand at acceptable efficiency.	Verify order or booking quality, repeat the result, and scale gradually.
Attributed brand searches rise but conversions remain flat	The campaign may be generating interest that the offer, destination, or conversion path is not capturing.	Do not declare a revenue win. Inspect search destinations, landing experiences, offer consistency, and conversion tracking.
Video engagement improves but commercial outcomes weaken	The creative may attract attention without qualifying the right buyer or making the next action clear.	Rework the product promise and handoff before adding budget.
Travel ads show inconsistent offers or weak delivery	Hotel Center data or campaign configuration may be obscuring the media result.	Resolve feed accuracy and eligibility questions before concluding that the channel failed.

Use Google’s performance figures as test inputs, not forecasts

Google reports that Demand Gen campaigns featuring TV screens generated 7% more conversions at the same ROI. LG Electronics also reported a 24% higher conversion rate than paid social while reaching high-value customers at a 91% lower CPA. Those figures make a reasonable case for testing the channel, but they are vendor-reported results rather than a guaranteed outcome for your account.

The LG comparison is especially easy to misuse. Without matching details for audience, geography, campaign period, conversion action, creative, and attribution model, a 91% CPA difference cannot become your forecast. Even the phrase “paid social” can conceal campaigns with different objectives and levels of maturity.

Use the 7% figure to support the question, “Is a controlled CTV test worth running?” Do not insert it automatically into a revenue plan.
Use the LG result as evidence that Demand Gen can compete with paid social under some conditions, not that it will always outperform it.
Put the comparator beside every benchmark in your internal presentation. A percentage without its baseline, campaign objective, and measurement rules is not an operating target.
Let your account’s conversion quality and unit economics decide whether to scale. A lower reported CPA is not valuable if it produces lower-value customers or bookings that do not hold.

Key takeaways

Shoppable CTV is a commerce-path update: use it when YouTube viewing creates product interest but the television experience lacks a clear response mechanism.
Travel Feeds are an offer-assembly update: audit Hotel Center data because price, rating, and availability accuracy directly affect what the traveler sees.
Attributed Branded Searches are a measurement update: activate the feature through a Google representative before launch and interpret it beside commercial outcomes.
Google’s 7% conversion figure and LG Electronics’ paid-social comparison can justify a test, but neither should be treated as an account forecast.
The strongest rollout ties one feature to one constraint, one primary outcome, one efficiency guardrail, and a written scale-or-stop decision.

Before your next campaign-planning meeting, write a one-sentence hypothesis and the two numbers that will decide whether you scale or stop. Then introduce only the Demand Gen feature capable of moving that hypothesis. That keeps the update focused on a business decision instead of letting it become a reason to spend first and explain the result later.

References

CrushPress.AI – Google’s Demand Gen: Unlock Shoppable and Measurable Ads

January 22, 2026

Google Campaign Mix Experiments: A Practical Testing Guide

You need to decide whether the next dollar belongs in Search, Performance Max, Shopping, Demand Gen, Video, or App. Looking at campaign-level ROAS alone will not answer that question. Changing one part of the account can alter what the other campaigns capture, so the decision has to be evaluated at the portfolio level.

Google Campaign Mix Experiments gives you a way to compare complete campaign combinations rather than treating every campaign as an isolated unit. Used carefully, the beta can tell you whether a different mix produces a better business result. Used casually, it can produce a confident-looking answer to a badly framed question.

Start with the spending decision, not the campaign list

A useful mix experiment begins with a decision you could make after seeing the result. “Test Performance Max” is not a decision. “Determine whether moving budget from the current Search and Shopping mix into a Search and Performance Max mix improves conversion value at the same total budget” is.

Write your hypothesis in this form:

If we change [one portfolio variable] while holding [the important controls] constant, we expect [primary metric] to improve enough to justify [the account change].
Campaign mix experiment hypothesis template

The phrase “enough to justify” matters. A measurable difference is not automatically a commercially important difference. Before launch, define the smallest improvement that would cover the operational cost, additional complexity, or risk created by the proposed mix. That threshold is your materiality rule.

Choose one primary metric that matches the decision:

ROAS fits a revenue-efficiency decision when your conversion values are dependable.
CPA fits a cost-efficiency decision when the counted conversions have reasonably comparable business value.
Conversions fits a volume decision when generating more qualified actions is the main objective.
Conversion value fits a growth decision when total value matters more than efficiency alone.

Google supports reporting around ROAS, CPA, conversions, and conversion value. You can inspect all of them, but naming one primary metric in advance prevents a common analytical mistake: searching the results for whichever metric makes the preferred arm look best.

Key takeaways

Frame the experiment as a portfolio-level business decision, not a request to identify the best individual campaign.
Change one meaningful variable between arms and keep the other important conditions aligned.
Keep total budgets comparable unless total spend is explicitly the variable under test.
Avoid shared budgets and material account changes while the experiment is running.
Preselect the primary metric, confidence interval, materiality rule, and minimum duration before looking at outcomes.
Plan for at least six to eight weeks, but do not assume that duration alone guarantees a decisive result.

Build arms that isolate one portfolio variable

Two balanced experiment trays contain matching campaign modules with one controlled difference between them.

An experiment arm is one complete version of the campaign portfolio. The beta supports up to five arms, and the same campaign can appear in more than one arm. That flexibility is valuable because you can preserve the common parts of the account while changing only the element you need to evaluate.

More arms are not inherently better. Every additional arm creates another comparison and divides the available traffic. Use the fewest arms that can answer the decision. For many questions, a current-state control and one alternative are enough.

The framework covers Search, Performance Max, Shopping, Demand Gen, Video, and App campaigns. Hotels campaigns are excluded. That breadth lets you test a cross-channel plan, but it does not remove the need for a clean experimental contrast.

Decision	What changes between arms	What should stay aligned
Channel budget allocation	The distribution of budget among campaign types	Total portfolio budget, measurement, and other material settings
Consolidation versus fragmentation	The number or structure of campaigns	Total budget, business objective, and the intended audience or inventory scope
Bidding strategy	The bidding approach being evaluated	Campaign mix, budget treatment, targeting, and measurement
Targeting option	The selected targeting treatment	Budgets, bidding, creative treatment, and the rest of the portfolio
Feature adoption	The feature is used in one arm and not the other	Everything not required to enable that feature

Suppose you change campaign structure, bidding, targeting, and budget distribution in the same arm. A winning result tells you that the package performed differently, but not which change caused it. You also cannot tell whether one helpful change compensated for another harmful one. That may be acceptable when the package itself is the business decision, but it is a poor design when you need reusable knowledge.

Budget handling deserves particular care. If you want to test the mix, keep the total planned budget equal and change its internal allocation. If you want to test a higher total spend level, make total spend the sole intended difference. Do not quietly give the preferred arm both a different campaign combination and more money; the result will not distinguish the effect of mix from the effect of spend.

Traffic can be allocated among arms with splits starting at 1%, and reporting is adjusted to the smallest split so the comparison remains fair. Treat 1% as a configuration boundary, not a recommendation. A very small arm may receive too little information to resolve a commercially modest difference, especially when conversions are sparse. The better question is whether every arm can accumulate enough relevant outcomes during the planned window.

Protect the comparison for the full test window

A strong setup can still fail after launch. New promotions, tracking changes, creative replacements, altered conversion values, revised targets, and unplanned budget moves can all change the conditions under which the arms are being compared. If those interventions affect the arms differently, you no longer have the experiment you designed.

Plan to run a campaign mix experiment for at least six to eight weeks. This is a minimum operating window, not a promise of statistical certainty. An account with limited conversion volume or a small true difference may still produce a wide range of plausible outcomes after that period.

Before launch, complete a short preflight:

Validate measurement. Confirm that the conversions and values feeding the primary metric represent the business outcome you intend to optimize. Fix tracking before the experiment, not during it.
Check arm symmetry. Verify that the total budgets and non-tested settings are aligned wherever the hypothesis requires them to be.
Remove shared-budget dependencies. Google advises avoiding shared budgets during these experiments. A shared budget can redistribute spend across campaigns and obscure the portfolio treatment you meant to test.
List prohibited changes. Record which budgets, bidding settings, targets, campaign structures, features, and measurement rules must remain untouched.
Record unavoidable events. If a promotion, inventory interruption, landing-page failure, or other business event occurs, document when it began, which campaigns it affected, and whether it compromised comparability.
Set review dates. Monitor for broken delivery or measurement, but do not repeatedly judge the winner from early fluctuations.
Define stop conditions. Separate genuine operational failures, such as broken tracking, from ordinary underperformance. A disappointing early result is not by itself evidence that the experiment is invalid.

The instruction to avoid significant changes does not mean ignoring a serious problem. If tracking fails or an arm cannot deliver as designed, protect the business and correct the problem. Then decide whether the comparison remains interpretable or needs to be restarted. The mistake is pretending that a materially altered test still answers the original hypothesis.

Keep a change log even when no restart is needed. Record the date, affected arms, reason, and expected impact of every intervention. When the result arrives several weeks later, that log will help you distinguish a real portfolio effect from a mid-test account event.

Read the portfolio result before diagnosing campaigns

A large magnifying lens frames an interconnected campaign system while smaller lenses point toward its individual components.

The Experiment summary should answer the question you wrote before launch: did one complete mix improve the primary business metric enough to change your decision? Campaign-level reporting then helps you understand where the portfolio difference appeared. Reversing that order invites cherry-picking.

One campaign can improve while the portfolio remains flat or declines. Another campaign can look weaker while the total arm improves because the mix is capturing demand more efficiently as a whole. Campaign-level movement is diagnostic evidence; it is not a substitute for the arm-level result.

Google lets you view experiment reporting with 95%, 80%, or 70% confidence intervals. Choose the interval before reading the outcome. A more conservative interval demands stronger evidence and will generally produce a wider range. A lower interval accepts more uncertainty. Switching among them until a preferred arm appears convincing turns an analytical setting into a result-shopping tool.

Read the result through three separate lenses:

Direction: Which arm currently appears better on the primary metric?
Uncertainty: Does the interval leave room for a materially different conclusion, including a meaningful loss?
Materiality: Is the likely difference large enough to justify the budget move, structural complexity, or operational burden?

Do not collapse those questions into a single winner label. A positive point estimate with a broad interval can still be inconclusive. A statistically clear but commercially tiny improvement may not justify rebuilding the account. An interval that includes little or no difference does not prove that the arms are identical; it means this run did not resolve the difference precisely enough under the selected standard.

Use the metric in the context of its inputs. ROAS and conversion value depend on the quality of the values assigned to conversions. CPA can look healthier when the mix generates cheaper but less valuable actions. Conversion volume can increase while efficiency deteriorates. These are not reasons to abandon a primary metric. They are reasons to make sure it represents the decision before the test begins and to use the other metrics as context rather than alternate finish lines.

Turn the finding into a controlled account decision

The result should lead to one of three actions: adopt the alternative, retain the current mix, or collect more evidence. Write the rule before launch so the post-test discussion is about evidence and tradeoffs rather than stakeholder preference.

Adopt: The alternative improves the preselected primary metric, the uncertainty is acceptable under the chosen interval, and the effect exceeds your materiality threshold.
Retain: The alternative is worse, creates an unacceptable downside, or fails to produce enough benefit to cover its complexity and cost.
Collect more evidence: The plausible range includes outcomes that would lead to different business decisions. Treat this as unresolved, not as a tie and not as permission to select the preferred narrative.

If you adopt a winning mix, implement the treatment you actually tested. Adding new targeting, changing bids, moving the total budget, and restructuring campaigns during rollout creates a new package whose performance was never evaluated. Make the validated change first, observe it under normal account conditions, and treat later improvements as separate decisions.

If the result is inconclusive, do not automatically rerun the same design. First identify why the answer remained unclear. The true difference may be too small to matter, an arm may have received too little useful traffic, the primary outcome may be too sparse, or account changes may have weakened the comparison. Rerun only when you can improve the design or when resolving the decision is worth another full testing window.

A compact decision record makes the learning reusable. Save these fields with the result:

The business decision and one-sentence hypothesis
The campaigns and settings included in every arm
The single intended difference between arms
Total budget treatment and traffic allocation
The primary metric and materiality threshold
The preselected confidence interval
The planned and actual run dates
All material account or business events during the test
The arm-level result and relevant campaign-level diagnosis
The final decision, owner, and implementation boundary

Your best first use of Campaign Mix Experiments is the largest unresolved allocation decision that can still be isolated cleanly. Write the hypothesis, name the metric, and sketch the control and alternative on one page. If you cannot explain exactly what changes and what stays fixed, the experiment is not ready to launch.

References

CrushPress.AI – Unlock Ad Performance with Google’s Mix Experiments Beta

January 22, 2026

Maximize Ecommerce Success with Demand Gen & Performance Max

When Google introduced Demand Gen campaigns in 2023, I saw them as a promising way to boost engagement across platforms like YouTube, Discover, and Gmail.

Initially, they felt experimental, straddling the line between awareness and performance, but they’ve come a long way since.

Now, the creative flexibility and enhanced audience control make Demand Gen a go-to campaign type for my ecommerce clients.

This strategy allows me to scale revenue in a controlled manner, maintaining brand consistency while testing creative approaches to drive conversions.

I’ve found that Demand Gen delivers the best results when strategically paired with Performance Max and Search campaigns.

Advertising with Demand Gen is ideal if you crave more control.

One major drawback of Performance Max is its lack of transparency and manual control.

If precise targeting, placement, or creative control is essential, Demand Gen stands out as the better option.

Performance Max auto-generates ads from your uploads, relying on Google’s AI to mix and match for the best performance.

This makes it crucial to provide top-notch creative assets.

For example, a fitness brand might create separate asset groups for products like leggings, shorts, and vests.

While this helps target relevant audiences, the control isn’t exhaustive.

However, Demand Gen offers far superior flexibility.

It allows me to upload, preview, and tweak ad combinations before launch, adapting each creative to its unique placement.

For instance, I can customize YouTube ads for in-feed, in-stream, and Shorts placements.

This control is perfect for ecommerce brands focusing on creative precision, message testing, and maintaining a strong visual identity.

Dig deeper: The Google Ads Demand Gen playbook

Using Demand Gen alongside Performance Max can be incredibly effective if you leverage their roles within the customer journey. They enhance each other rather than compete.

Demand Gen builds awareness and sparks interest by reaching higher-funnel audiences before they actively start product searching.

Conversely, Performance Max focuses on converting lower-funnel users who are primed to purchase.

For example, a fitness retailer might utilize Demand Gen for lifestyle videos and discovery ads promoting their latest activewear.

When a potential customer begins to research or exhibit purchase intent, Performance Max engages with tailored Shopping and Search ads to finalize the sale.

I’ve set up feed-only Performance Max campaigns, providing only a product feed within the asset group.

This restricts Performance Max activities to Shopping placements, focusing it sharply on direct conversions.

Meanwhile, Demand Gen operates across platforms like YouTube, Gmail, Discover, and Shorts, covering the upper and mid-funnel with more visual, creative content focused on awareness.

This configuration minimizes overlap between campaign types while ensuring user engagement throughout the funnel, from brand discovery to purchase.

For larger accounts with flexible budgets, this dual structure drives holistic performance and clearer attribution.

In contrast, smaller accounts seeking efficiency should prioritize mastering high-intent campaigns before layering in Demand Gen once the core conversions are stable.

The diverse campaign types now offer advertisers more flexibility than ever, yet it requires understanding Google’s restructuring of video and discovery products.

Dig deeper: Why Demand Gen is the most underrated campaign type in Google Ads

Since July 2025, Google’s Video Action Campaigns (VACs) have been replaced by Demand Gen.

It streamlines Google’s visual placements into one campaign type, including YouTube in-stream, Shorts, in-feed, Gmail, and Discover.

This change is significant. VAC was successful for ecommerce, particularly for conversion-centric video. Its removal underscores Google’s encouragement to embrace Demand Gen.

The advantage is that Demand Gen provides stronger creative control and diverse testing options across YouTube placements.

If you previously ran VAC campaigns, they are now under Demand Gen. Ensure your top-performing assets and audiences have migrated correctly, then use the new controls to optimize performance.

Audience control is a significant benefit of Demand Gen, and it’s a reason why I consistently use it for ecommerce.

Demand Gen allows precise audience creation, letting me decide who sees the ads.

I can select placements, merge audience types, and allocate the budget strategically.

It’s the only Google Ads campaign type supporting lookalike audiences, valuable for brands focused on acquiring quality leads.

While Performance Max utilizes audience signals over fixed targeting, Demand Gen excels for control, testing, and segmentation strategies.

In mid-2025, Google rolled out an open beta for advertisers to opt out of specific Demand Gen channels manually.

This means I can now control ad display, excluding Discover or YouTube Shorts if they don’t align with my objectives or creative format.

This small but significant update offers more control, a feature often lacking in many of Google’s automated campaign types.

Dig deeper: Google Ads rolls out channel control for Demand Gen campaigns

In early 2025, Google introduced product feed integration for Demand Gen campaigns. This change allows me to link the Google Merchant Center feed, incorporating live product data directly into visual ads.

This development bridges performance and branding for ecommerce, enabling storytelling through creative visuals while displaying actual products.

For instance, a fashion retailer can showcase a new collection in a video advert while featuring shoppable product cards below.

This update positions Demand Gen as a hybrid between Shopping and Display, a much-anticipated capability among ecommerce advertisers.

Demand Gen typically demands a larger budget than other campaign types.

Google recommends starting at about £100 per day per campaign or 20 times your target CPA/tROAS, whichever is higher.

Practically, the £100-per-day baseline is a viable starting point for effective data collection and optimization. Lower budgets restrict data flow and slow progress.

Demand Gen complements your broader Google Ads strategy, rather than replacing Search or Performance Max.

It’s a premium, visually led campaign type that boosts awareness leading to conversions, particularly effective when you have accurate measurement, a clean product feed, and clearly defined audiences.

The table compares Demand Gen and Performance Max on key aspects that matter to advertisers.

Dig deeper: Google pushes Demand Gen deeper into performance marketing

Performance Max excels in scale but can be opaque.

Demand Gen offers the control advertisers have demanded—genuine creative testing, audience precision, and placement visibility.

For sustainable ecommerce growth, I recommend using both. Performance Max captures demand, while Demand Gen creates it.

Together, they form a comprehensive framework for scalable and sustainable growth.

Inspired by this post on Search Engine Land.

January 22, 2026

Category: Google Ads

What the endorsement test actually changes

Prepare your brand without trying to game the experiment

Measure an appearance without inventing causality

Keep paid search, SEO, AEO, GEO, and schema in their proper lanes

Key takeaways

References

Choose the upgrade scope from the decisions you need to improve

Rebuild reporting around the new data grain

Performance Max network breakdowns need a new row key

Shopping conversion-date metrics need an explicit time basis

Use PerStoreView as a controlled local-data migration

Keep billing detail and scheduling precision from creating new errors

Model invoice charges by type before calculating totals

Treat date-time scheduling as a write-path migration

Put human review between AI assistance and campaign changes

Preserve LIFE_EVENT_USER_INTEREST as its own dimension

Handle generated audience attributes as a proposal

Keep Demand Gen forecasts separated by surface

Key takeaways for your v23 upgrade sequence

References

Where the one-click PMax preview lives

A repeatable workflow for reviewing PMax creative

What to inspect across the available placements

Image composition and legibility

Video clarity and continuity

Asset pairing and destination consistency

What a PMax preview can and cannot prove

Key takeaways

References

Diagnose the constraint before you pay to expand it

Pass the AI Max readiness gate

Make the conversion signal worth optimizing

Align automated bidding with the economic goal

Check data volume, broad match history and budget pressure

Control landing pages and generated assets before launch

Build demand and capture as one connected system

Measure the handoff without giving one channel all the credit

Test AI Max as an expansion layer, not a rescue plan

Key takeaways

References

Triage the failure before you touch the campaign again

Key takeaways

Use the narrowest workaround that preserves control

When Add note is missing

When a Performance Max asset group will not save

Protect the audit trail while the interface is unreliable

Verify the account state, not the success message

References

Agentic AI: Google Ads’ Game-Changing Feature

Integrating Agentic AI in PPC Workflows

Why Agentic AI is Key for Advanced PPC Marketers

Vibe Coding: Creating Your Marketing Toolbox

The Future: Navigating PPC with Agentic AI and Vibe Coding

The remedies split into four operational layers

The alleged harms are testable mechanisms, not settled outcomes

Index access could change discovery and spam incentives

Ad fraud risk rises when the traffic chain becomes opaque

Nominally favorable pricing can still produce weak economics

Access to interaction data does not create permission to reuse it

Build a readiness plan without betting on the appeal

Questions paid media teams should ask before buying inventory

What SEO, AEO, and GEO teams should measure differently

Key takeaways

References

What changed, and what each update actually does

Match the feature to the constraint in your funnel

Use shoppable CTV when the missing link is product action

Use Travel Feeds when changing offers make creative stale

Use Attributed Branded Searches when last-click reports hide influence

Build the measurement plan before you move budget

Use Google’s performance figures as test inputs, not forecasts

Key takeaways

References

Start with the spending decision, not the campaign list

Key takeaways

Build arms that isolate one portfolio variable

Protect the comparison for the full test window

Read the portfolio result before diagnosing campaigns

Turn the finding into a controlled account decision