Questions we actually get asked

How many conversions does the campaign reliably deliver per week/month on Maximize Conversions? At low volume (roughly under 15–30 conversions in 30 days), switching to tCPA risks getting stuck in "Learning" for a long time without a clear payoff.

What's your actual (or expected) target CPA? A sensible minimum daily budget is usually estimated as a multiple of CPA — a common rule of thumb: your daily budget should cover at least 2–4 conversions at target CPA, or you'll accumulate stats too slowly.

Do both flags actually apply to the same time window? Sometimes one status is current and the other is a holdover from an earlier period that hasn't refreshed in the interface yet.

Are these "different conversion types" actually different in substance, or just different paths to the same outcome — for example, a sign-up form, a demo booking, and a phone call that all lead to the same kind of qualified lead?

How many actual changes have been made to the campaign over the last month? Flip-flopping between statuses is almost always a sign of frequent edits (bids, budget, target, conversion actions, structure), not the algorithm "behaving erratically" on its own.

What does Auction Insights show for your core keywords? Overlap rate, outranking share, and impression share relative to competitors give you an indirect read on how aggressively they're bidding — but Google doesn't reveal a competitor's actual CPA.

Is the goal (target CPA and conversion type) really identical across the campaigns you're considering merging? If the targets formally match but the campaigns actually serve different products or audiences, merging could blend inconsistent segments into a single optimization.

Does your business have clear year-over-year seasonality? Compare the current period not just to last month but to the same period last year, to tell a seasonal effect apart from a structural problem.

Is this clustering actually a problem, or just a reflection of real demand? If one segment (geo/device/audience) genuinely accounts for the bulk of paying demand in your niche, concentrating there may be correct algorithm behavior, not a distortion.

Check the campaign's status in the interface — an explicit "Bid strategy constrained by target" or "Limited by search volume" flag, paired with spend running well under budget, is a direct sign the problem is the target, not a lack of demand in the niche.

How long has the campaign been beating target? If it's not a one-off blip but a consistent pattern over several weeks, that's a strong signal of untapped potential, not just statistical noise.

What's the real median (and "tail") gap between click and conversion for this business? Check the Time Lag report in Google Ads (the day-by-day "click to conversion" distribution) — without this number, any judgment about a recent period will be premature.

Which direction did the window change — wider or narrower? Widening the window (say, from 30 to 60 days) usually adds previously uncounted conversions retroactively, causing a sudden jump in the historical numbers. Narrowing does the opposite — it retroactively removes conversions that used to count.

Is there enough total traffic/conversion volume to split it into two halves (test and control) and still get a statistically meaningful read from each? An experiment needs roughly twice the data to reach the same confidence level as a direct change.

A quick primer: how tCPA compares to other bidding strategies

The practical way to check this is through Report Editor (or a standard report) broken out by Conversion Action, using the "All Conv. Value" metric. Building a report segmented by specific conversion action and comparing count/value per action makes it easy to spot whether the same purchase is being double-counted across multiple conversion actions (say, between the native Google Ads tag and a GA4 import) — in that case, the account's total "All Conv. Value" will noticeably exceed real revenue, and the breakdown by conversion action will show that several different actions are, in effect, recording the same transactions.

What was the campaign's status during the seasonal peak? An explicit "Limited by budget" or "Bid strategy constrained by target" flag on those specific days points to the target or budget physically preventing the system from taking advantage of the demand spike.

How long, and how consistently, has actual ROAS been beating target? A one-off overshoot from a couple of big orders is different from sustained overperformance across several weeks in a row.

Is this really a one-off anomaly (a single large order) or a recurring, if infrequent, pattern (say, bulk orders once a month)? These are different situations with different fixes.

What's the real median gap between click and purchase for this business (the Time Lag report in Google Ads)? Without this number, evaluating "recent" periods will be systematically skewed on volume and distorted on ROAS.

Campaign structure. Is the volume and makeup of keywords/targeting comparable — number of keywords, match types, number of ad groups, audience signal coverage (for Performance Max)? A campaign with a narrow structure physically can't deliver the same volume as one with broad coverage, even with an identical target — this isn't an efficiency question, it's a question of the structure's scale.

Pull up the "Conv. value / cost" and "Value / conv." columns broken out by Conversion Action — if the average conversion value looks suspiciously identical (say, exactly the same number) across many transactions of clearly different size/composition, that's a clear sign a fixed default value is being used, not the real transaction amount.

Campaign structure. Are different product categories currently split into separate campaigns/groups, or is everything running through one shared structure (especially relevant for Shopping/Performance Max)? Without structural separation, it's technically impossible to assign different targets to different categories in the first place.

Is the moment of refund reflected in the passed conversion value at all? If value is passed once, when the order is placed, and never adjusted afterward, ROAS in Google Ads will be systematically overstated relative to the business's real revenue, by the full amount of refunds.

Campaign structure. How broad is the campaign's own keyword/targeting setup? If the structure is narrow from the start (few keywords, tight audience signals), the system physically has nowhere to expand beyond the narrow segment it's already found, regardless of the target.

Campaign structure. Is your keyword/targeting setup broad enough that, once the target constraint is loosened, the system actually has somewhere to expand in a controlled way, rather than jumping straight into a wide pool of low-quality traffic?

Campaign structure. Is the keyword/targeting coverage broad enough that the system could actually find additional volume if the constraint were lifted? If the structure is narrow, the "constrained by target" flag may technically be there, but the real headroom for growth may still be modest.

A quick primer: why a single transaction is a poor anchor for a repeat-purchase business

Is the value rule actually active and applied to the specific campaigns/audiences/locations/devices it was built for? Value rules need to be explicitly turned on at the campaign level, and a rule that's configured but not connected to the right campaigns simply won't fire.

A situation where broadening keywords doesn't drive volume growth usually means one of a few things: either the new keywords technically can't physically "capture" additional traffic (because real demand for them is already almost entirely covered by the existing keyword set), or the problem isn't with keywords at all — something else is masquerading as "limited by search volume." The official explanation of how match types work, and how broad match can already cover part of new terms before you explicitly add them, is in Google Ads Help's article on keyword match types.

Since 2017, Google Ads has allowed campaigns to spend up to twice the set daily budget on individual days, offsetting that within a monthly cap equal to the daily budget multiplied by the average number of days in a month (about 30.4) — this is an officially documented mechanism, not a billing anomaly or error. Details are in Google Ads Help's article on how daily budget spending works. It follows that a single day where spend noticeably exceeds the daily limit doesn't by itself indicate a systemic budget constraint — it may simply be normal offsetting for a cheaper prior day, within this permitted smoothing mechanism.

A "Limited by budget" status combined with a tight CPA/ROAS target creates a compound constraint, where fixing only one of the two factors may not deliver results: if you raise the budget but the system still won't enter pricier auctions because of the demanding target, the extra money simply won't get spent — impressions won't grow, even if "Limited by budget" formally clears afterward, because the real constraint has shifted to the target. An official breakdown of how bid strategy statuses relate to each other, and why budget and target can constrain a campaign at the same time, is in Google Ads Help's article on bid strategy statuses.

Impression Share (IS) is the share of impressions a campaign got out of the total number it was eligible for (that is, all the impressions its ads could theoretically have competed for in the auction). Google Ads breaks the unmet share down into two separate, independent components: Search Lost IS (budget) — the share of impressions missed specifically due to a budget shortfall, and Search Lost IS (rank) — the share missed due to an insufficiently high ad rank (usually tied to bids, the target, or ad/page quality). The official description of this metric and its formula is in Google Ads Help's article on Impression Share.

When both constraints are present at once, it's tempting to change both parameters at the same time, but that's a methodological mistake: if you change the budget and the target together and results improve, you won't be able to tell which change actually worked — and next time a similar situation comes up, you'll be guessing again instead of relying on something you've actually confirmed. The right approach is to determine priority through the numeric metrics (Search Lost IS budget vs. rank) and change one parameter at a time, with a pause to let things settle between changes. Google's official guidance on interpreting bid strategy constraint statuses, and how to weigh them against each other, is in Google Ads Help's article on bid strategy statuses.

This question is essentially the flip side of diagnosing the "Limited by search volume" status: there, we covered the general approach to telling apart "a small market" from "a narrowly configured campaign," and here it's worth building a concrete checklist of the typical setup mistakes that most often masquerade as "an objectively small niche." The most common technical causes: overly narrow keyword match types (exact match only, instead of broader coverage of semantic variations), an excessively long negative keyword list at the account or campaign level, overly narrow location targeting (say, targeting just a city instead of the whole region where potential buyers actually live), or narrow audience signals in Performance Max that effectively exclude part of the relevant audience. The official breakdown of match types and how narrow match settings shrink reach is in Google Ads Help's article on keyword match types.

This is a direct consequence of the fact that budget and market size are fundamentally different categories of constraint that don't compensate for each other. Budget determines how much money a campaign can spend per day; market size determines how many relevant searches exist at all for the campaign to potentially show against. If the volume of queries in a niche is physically small, no amount of budget will create queries that don't exist — the money simply won't get spent, because there's nothing more to show ads against. This is reflected directly in the logic of the Limited by search volume status, which Google assigns exactly when a campaign is already covering nearly all the available volume given its current keywords and targeting, regardless of budget size — and it's distinct from budget-related Impression Share metrics, which in this case stay low for reasons that have nothing to do with money.

The «Bid strategy constrained by target» status by itself doesn't say whether the target is realistic or not — it simply records the fact that the target is constraining volume. The problem is that a target can constrain volume in two fundamentally different ways: (1) it's genuinely demanding relative to the current state of the auction (a real, justified trade-off between efficiency and volume), or (2) it's artificially too low or too high because of an error in the calculation or the underlying data — in which case the "constraint" doesn't reflect a real business decision, but a technical problem.

This is a specific, common situation in real accounts: a campaign is losing impressions to both budget (Search Lost IS budget is high) and to an insufficiently high ad rank (Search Lost IS rank is high) at the same time. The typical mistake here is to try raising both the budget and bids/loosening the target at once, hoping to "fix everything in one shot." The problem with that approach is that you won't be able to tell which change actually cleared the constraint, and which just added unspent money on top of a problem that's still bottlenecked by rank.

A fragmented account structure — lots of small campaigns instead of consolidated, larger ones — can create the illusion of a budget constraint when the real problem is how budget is distributed between campaigns, not an absolute shortage of money. Each individual campaign has its own daily budget and its own set of statistics for the bid strategy to learn from; the official description of how long, and on how much data, the automated bid strategy learning cycle runs explains why fragmentation hurts specifically at this stage — if an account's total budget is split into many small pieces, each individual campaign can genuinely lack enough data to learn effectively (which lowers ranking quality and creates rank-lost, described in detail in Google Ads Help's article on Impression Share) while also bumping up against its own small budget ceiling (creating budget-lost) — even though merging those same campaigns into one larger structure would keep the total budget unchanged while noticeably improving results through consolidated learning and more flexible spend distribution within a single campaign.

Rank-lost impression share depends not just on your own bids, but on your relative position in the auction — that is, how competitive your bids and ad quality are compared to everyone else in the auction. That means a rise in Lost IS (rank) with absolutely nothing changed on your end is almost always explained by outside changes: either competitors raised their own bids or improved their ad quality, or the mix of auction participants themselves shifted (new competitors showed up), or both are happening at once. The official description of the Impression Share metric, and the logic behind why it reacts to relative rather than absolute position in the auction, is in Google Ads Help's article on Impression Share.

This is a strategic question, not a purely technical one: raising the budget solves the volume problem while keeping the current optimization logic in place, whereas changing the bid strategy itself (say, moving from Maximize Clicks to tCPA, or from manual management to an automated strategy) changes the underlying logic of how the money gets spent. An official overview of the available bid strategies and how they work is in Google Ads Help's article on automated bid strategies. The decision on what to change — budget or strategy — depends on which of two goals is the priority for the business: growing reach within current efficiency, or improving efficiency itself and then growing reach on that stronger foundation.

A campaign shifting from one type of constraint to another — say, from "Limited by budget" to "Bid strategy constrained by target" — usually happens as a direct consequence of clearing one constraint without accounting for the other: for example, the budget was raised, budget-lost dropped, but the target stayed the same and stayed tight, and now it's become the dominant factor limiting growth. An official overview of statuses and the logic behind how they form is in Google Ads Help's article on bid strategy statuses.

A sharp rise in a competitor's auction activity is almost always visible before you feel it in your own campaign's numbers — if you know where to look. Auction Insights shows impression share and overlap rate for every competitor in the same auctions as you, in real time, with history over your chosen period. A sharp jump in a specific competitor's impression share that coincides in time with a drop in your own impressions is direct, quantitative confirmation that this particular player is pulling auction share away from you, rather than a general market decline or a problem on your end.

An across-the-board, simultaneous drop in performance for every keyword in a campaign is an important diagnostic signal on its own: if the cause were local (say, individual keywords became less relevant, or ran into heightened competition specifically on those terms), the drop would be uneven. A synchronized, simultaneous drop across the whole campaign points to a shared, systemic cause operating at the campaign level all at once, rather than at the level of individual keywords. Combined with a "Bid strategy constrained by target" status, this is especially telling, since that status already indicates the target is an active limiting factor; the question is whether the target actually caused the drop, or whether the drop happened for another reason and simply coincided in time with an already-existing constraint status.

The standard recommendation for a target-based limitation is to loosen tCPA/tROAS, but that's not the only lever — and in situations where the business's economics genuinely won't allow a compromise on efficiency (say, unit economics are already running at breakeven, and any loosening of the target immediately turns things unprofitable), you need to look for volume growth other ways, without touching the target itself. The logic here is that a target constraint is really a constraint on the ability to win auctions at a given price; you can expand the volume available at that same price not just by raising your willingness to pay more, but by increasing how competitive your offer is relative to other participants in the same auction.

It helps to understand the underlying mechanics here: replacing text inside an existing RSA is an edit to a live ad, not the creation of a new one. The ad's overall accumulated stats (total clicks, conversions, history as a single Ad ID) don't reset. But every individual new asset (a new headline or description swapped in) starts from zero — it has no history and has to build its own data from scratch, regardless of how old the ad itself is. That's exactly why "how often to refresh" comes down not to whether you can refresh at all, but to how many assets you swap at once and how often, so you're not wiping out the statistical base wholesale.

Fact-check: The premise behind this question needs a correction before anything else. Google Ads officially does not assign a "Learning" status to an RSA as a single entity. Two independent sources confirm this:

The combinations report for RSAs is real and officially documented by Google — it's a separate tab inside the asset report showing the specific headline-and-description pairings that were actually assembled into an ad, along with the impression count for each combination. You can find it via "View asset details" on a specific RSA → the Combinations tab.

Here's the important thing to understand: a lack of correlation between Ad Strength and real performance isn't an anomaly — it's a documented property of the metric itself. Google officially describes Ad Strength as a score built on best practices, meant to help you make a good first impression — in other words, the metric isn't built from your ad's actual performance data. In 2024, a Google representative (Ginny Marvin) directly confirmed that Ad Strength isn't used in Ad Rank calculations — meaning an ad with a low rating can, technically, show and perform just as well as one rated "Excellent."

When multiple RSAs run in one ad group, the system has to decide, before each individual impression, which of your own ads to enter into the auction — and only then, which combination of assets to assemble inside it. That effectively turns multiple RSAs into parallel forecasting models competing for the same auctions inside your own account, rather than against outside competitors. The industry describes the direct consequence of this as impression fragmentation: instead of one ad quickly accumulating enough data to self-optimize, impressions get spread across multiple ads, each of which ends up under-supplied with data — and the whole ad group underperforms as a result, not because the copy is weak, but because none of the variants ever built up enough statistics.

The mechanics here are straightforward and backed by independent large-sample analysis. Fully pinning assets almost always drives an RSA to a "Poor" Ad Strength status, which in turn reduces impression volume for the fully pinned RSA compared to other ads in the same group that pin less aggressively. Every pinned position cuts into the number of combinations the system can assemble and test: pinning just two headlines has been shown to cut the system's testing potential by roughly 99.5% — a sharp, nonlinear effect even from a small number of pinned positions.

Google's official position on testing RSA copy is direct: ad-level metrics like CTR and conversions don't give you the full picture, since RSAs themselves help you qualify for more auctions — so results are better judged by incremental impressions, clicks, and conversions at the ad group and campaign level, rather than by the isolated metrics of one ad or one combination. This directly explains why testing every individual combination one by one isn't the path the RSA architecture is built for — the system tests combinations inside an ad on its own logic, not the logic of a manually controlled experiment.

The fact that an ad keeps running with some assets disapproved isn't a bug — it's a direct consequence of RSA architecture: each individual asset (headline or description) goes through its own policy review independently, rather than as one indivisible unit with the ad. This is confirmed by an officially documented parallel example: when campaign-level assets (shared headlines/descriptions that can be used across multiple RSAs) fail policy review, other approved creatives and campaign-level assets are used for serving instead — the system automatically substitutes the disapproved element with one that's working. The same logic is officially documented for text disclaimers as well: if a disclaimer asset is disapproved on policy review, the ad keeps showing — a different description line, or one pinned to the first position, is used in place of the disclaimer.

Fact-check: This question's framing relies on an outdated mechanism. The "Performance label" column (Low/Good/Best) in the RSA asset report has been officially deprecated by Google, since full performance statistics are now available for each asset — and that full statistics view is available for date ranges starting June 5, 2025. The same applies to the campaign-level asset report: the "Performance label" column was removed precisely because full performance figures are now available for each asset. So "how do I connect asset performance to the label" isn't quite the right question for RSAs anymore — the label itself no longer exists in this report; it's been replaced with raw metrics.

Here's the thing to understand: a headline's effectiveness isn't a property of the text itself — it's the outcome of that text's interaction with the context of a specific ad group, and that context is genuinely different across ad groups even when the headline text is identical. Google's official account-organization guidance is built on exactly this principle: for each ad group, it's recommended to pick a narrow theme and use keywords relevant to that theme, including at least one of those keywords in the ad's headline — since a user is more likely to find an ad relevant when it explicitly mentions the term they searched for. If the same headline is used in two ad groups with different semantics, it will, by definition, match one group's queries more precisely than the other's, simply because the surrounding keywords and real search queries differ.

There's a key officially documented property worth establishing up front, since it directly shapes what's even possible to measure. Google explicitly documents that the automatic text updates that happen when a customizer fires don't reset or fragment an ad's performance data — all the stats keep accumulating on the same ad, regardless of which specific dynamic value was shown at any given moment. That's convenient in that reporting doesn't "multiply," but it also means there's no way to see directly, in the interface, how a specific countdown value or price actually affected clicks and conversions — standard reports don't break results down by which version of the dynamic text rendered at the time of a given impression.

Dynamic Keyword Insertion (DKI) technically works on the same architecture as the ad customizers and countdown covered earlier: Google explicitly describes ad customizers as working the same way as keyword insertion or countdown timers — that is, adding dynamic content directly into the ad, with all stats continuing to accumulate on the same ad regardless of which specific text was inserted for any given impression. That directly creates the main reporting risk: if a DKI ad shows against dozens of different keywords in a group, all those visually different text versions ("Buy Nike sneakers," "Buy Adidas sneakers," "Buy New Balance sneakers") get rolled up into one single ad's reporting row — you simply can't see in a standard report which inserted phrase drove more clicks or conversions.

Fact-check: Worth flagging up front: Google doesn't have a separate, officially documented "creative fatigue" indicator specifically for RSAs in Search — unlike, say, the refresh guidance Google publishes for Demand Gen and Performance Max. So for RSAs, "knowing it's time to refresh" isn't a matter of reading a built-in interface signal — it comes from combining a few pieces of indirect evidence.

Before treating this as a bug — showing outside a set region is, in most cases, the expected behavior of the default setting, not a broken rule. The default location setting, "Presence or Interest," shows ads to people physically in your targeted location, regularly there, or simply showing interest in that location through their queries or behavior — even if they're actually somewhere else. Google's own example: target Paris, and the ad can reach someone physically in Paris and also someone elsewhere who's just interested in Paris bakeries.

The first official indicator for this split is Ad Strength at the asset group level: use the Ad Strength indicator to determine whether an asset group has enough assets to drive best performance, and make sure every asset type — text, image, video — is covered and meets quality guidelines. If Ad Strength is low, that's a direct pointer toward the creative side.

Before switching the feature off entirely, it helps to understand the mechanism and the middle-ground options available. Final URL expansion, on by default, lets Google replace your Final URL with a more relevant page on the same domain based on the user's search intent — meaning irrelevant landing pages are often a side effect of expansion running without exclusions, not a malfunction.

The core difference from classic keywords is built into the tool's purpose: search themes let you flag queries your customers use are searching for, but they're optional and additive — layered on top of the queries and placements PMax already predicts will perform well based on your assets, feeds, and landing pages. That's a fundamentally different logic from Search: a keyword there is a serving condition; a search theme here is a hint layered on top of a model that will keep searching on its own regardless.

The direct, officially documented cause is described in the context of retail campaigns, but the logic applies more broadly: asset groups ideally shouldn't overlap on targeted products — Asset Group 1 and Asset Group 2 shouldn't both target products A–Z; instead, one should own A–L and the other M–Z. If that overlap exists, both groups are literally competing for the same traffic inside one campaign — and since asset groups aren't independent campaigns with their own budget and strategy, they don't split that traffic evenly; they compete for it under the campaign's shared auction and optimization rules.

There's no dedicated "signal overlap between asset groups" report — worth stating plainly so you're not searching for a tool that doesn't exist. But overlap can be assessed indirectly through asset group reporting: it lets you review status, Ad Strength, conversions, conversion value, and audiences across each asset group in the campaign — an audience column exists, it just has to be cross-referenced between groups by hand rather than read off as a ready-made overlap metric.

The feeling of limited control isn't an accident or a gap — it's a direct consequence of the product's architecture. PMax runs on "keywordless targeting" — Google AI and machine learning find and serve ads to likely converters using signals from the campaign, site, and feeds, instead of manual keyword management. That's a fundamentally different model from Search, where the advertiser directly controls the serving condition through keywords.

The key fact that shapes this whole answer: placement exclusions for PMax only work at the account and MCC — there's no campaign-level setting yet. Unlike Display or Video campaigns, where exclusions can be managed per campaign, the only official path for PMax is setting exclusions account-wide, and they'll automatically apply to every PMax campaign in that account at once.

The fact that explains the limited effect is stated directly in official documentation: PMax negative keywords are applicable to Search and Shopping — adding negative keywords to a campaign or account helps avoid serving on matching queries specifically on those two surfaces. PMax, meanwhile, shows across a much wider set of channels: six Google channels — and negative keywords structurally do nothing on any of those channels except Search and Shopping.

Google's own troubleshooting checklist for a campaign that's "hit a ceiling" names several independent categories of cause, split between targeting and creative: check whether CPA/ROAS targets are too restrictive — that's a bidding/targeting issue, blocking auction participation; check whether there are enough creative assets of every type and size, aiming for an "Excellent" Ad Strength — a purely creative category; try adding or refreshing search themes — a semantics/targeting category; and audit whether account- and campaign-level exclusions are limiting reach — also targeting. In other words, Google's own advice is to work through independent checkpoints in sequence rather than guess at one overall cause.

Google's stance here is direct and unambiguous: consolidate campaigns where you can — that gives Google AI more data and performance history to sharpen its predictions — and only create separate campaigns when there's a real business reason: different goals, budgets, or CPA/ROAS targets. In other words, splitting by product category isn't a default best practice on its own — it's an exception that needs justifying, not a habit inherited from how a catalog happens to be organized.

Worth establishing the current scope of the tool first: demographic exclusions in PMax are currently limited to age and gender — an initial rollout aimed at the most critical demographic-exclusion needs. If expectations were broader (household income, parental status, for example), those simply aren't available for PMax yet.

Fact-check: Most likely, "excluded" here meant removing a segment from audience signals, not applying an actual exclusion tool — and those are fundamentally different actions. Audience signals are hints, not rules: PMax can serve outside your signals if it predicts a strong chance of conversion. Removing a segment from signals only stops suggesting it as desirable to the model — if the model, independently of signals, keeps finding converters in that segment, it will keep serving there, because a signal was never a blocking mechanism to begin with.

Fact-check: One nuance worth flagging up front: custom segments built through the general Audience Manager (the version used for Display, Gmail, Demand Gen, and Video campaigns) can't be applied directly to PMax as a standalone targeting object — the same page states this explicitly. What PMax actually offers is a custom-segment-style input built directly into its own audience signal builder, described on PMax's own audience signals page. The two are conceptually related but not literally the same feature, so it's worth not confusing "custom segments" in the general Audience Manager sense with the custom-segment input inside a PMax audience signal.

This is an officially recognized and documented scenario: PMax campaigns can maximize total sales and revenue from both new or existing; if new customers are the priority, the official recommendation is the new customer acquisition goal with New Customer Value mode, bidding first toward the most valuable prospects. Google is effectively acknowledging that, without a dedicated setting, PMax optimizes for total conversion value without distinguishing "new" from "already existing" customers — and that's exactly what creates the feeling of "cannibalization" of traffic that would have converted through another channel anyway.

Before writing YouTube off, it helps to understand that video advertising behaves differently from click-driven formats by nature: video is immersive, but unlike other formats, people don't always act on it in the moment; the action often comes later, after the viewing session ends. That's exactly why YouTube inventory has its own dedicated conversion metrics that don't overlap with the standard "Conversions" column.

Both channels are officially defined and appear as their own rows in the channel distribution table: the Discover channel covers ads shown in the Discover feed, and the Gmail channel covers ads shown in users' Gmail inboxes. You can see them directly, alongside Search, Display, YouTube, and Maps.

Google's own answer here is direct: PMax campaigns use AI automatically distribute budget across every Google channel to maximize conversions, prioritizing channels the system predicts will perform best; you can't directly control budget by channel, but you can influence it indirectly. This isn't an interface limitation. It's a direct result of how the product is built. PMax is designed as one model that decides, in each auction moment, where to send budget, rather than a set of independently manageable per-channel sub-budgets.

It's worth separating two different tools first. The Insights page and the channel performance report answer different questions. Insights is curated for you based on account performance and searches across Google related to what you advertise, and it updates daily.

The word "diluted" describes exactly what happens with blended reporting: looking only at aggregate campaign metrics (overall CTR, overall conversion rate) averages a strong Search result together with a weaker Display result into one number. Google's own recommendation is to look at each channel individually through the channel distribution table rather than judging by the blended average, since impressions, clicks, conversions, and cost are all available there broken out by channel.

Google built an official tool for exactly this decision: Shopping versus PMax experiments let you compare one of your existing Standard Shopping campaigns against a new or existing PMax campaign with similar settings, to see which one drives better results for your business. This is a purpose-built A/B test for exactly this question, not a judgment call made after the fact.

The key method here is comparing against the same period a year ago, not just the previous stretch within the current season, since that's exactly how Google's own tool for spotting seasonality is built: the year-over-year comparison checks the last 28 days of search volume against the same 28 days a year earlier, built specifically to separate a recurring market shift from something specific to your account. If a channel's rise or fall matches the same pattern from last year, that's seasonality. If there's no matching pattern from last year, it's more likely something new and specific to the current campaign.

First, it's worth establishing that video ads can grow impressions organically, without depending on a click, unlike Search, so impression growth and conversion growth are expected to diverge here more than in other channels. The "Ads using video" segment in the channel distribution table lets you view video performance separately from the rest of the inventory. That's the first step: confirm you're analyzing this specific segment, not the whole YouTube channel, which can include non-video formats too.

Worth flagging up front: Google's official tools for measuring true, causal incrementality (Conversion Lift, geo-based experiments) measure a campaign or geo region as a whole, not one channel isolated inside a single, already-running PMax campaign. There's no built-in way in the interface to cleanly "cut out" just Display or just YouTube from an overall PMax campaign and honestly measure its separate incremental value.

The mechanics here are fairly direct: without video assets, part of PMax's inventory is unavailable or only partially available, and adding video opens that inventory up fully and right away. Google's own documentation names adding video specifically as an example of an event that produces a visible shift: the time series chart pinpoint exactly when a channel-mix shift happens, for example right when video is added to a campaign. Google is essentially confirming this is an expected, documented pattern, not a side effect.

Google's own troubleshooting documentation names this pattern directly, calling it cross-channel dynamics: with last-click attribution, a channel can look like it has a low ROI when it's actually playing an important role earlier in the path to conversion, since last-click often fails to capture the full contribution of channels engaging users earlier in their journey. That's a direct official acknowledgment that a low channel ROAS under last-click attribution isn't always a diagnosis; it's often an artifact of the measurement method.

The gap between reported ROAS and real profit isn't a glitch. It's a direct consequence of what actually gets passed to Google Ads as "conversion value" by default. Official documentation states plainly that conversion value can reflect either revenue or profit; the advertiser defines which one gets optimized, and by default most setups pass revenue (the full order amount), not what's left after cost of goods, shipping, taxes, and returns.

The first, basic checkpoint is whether dynamic values are used at all. When setting up a conversion, you need to select "Use different values" for each conversion. Without that selection, the system uses one fixed value for every conversion regardless of the real order amount, and correctness around discounts or shipping doesn't matter at that point, since the value isn't tied to the transaction to begin with.

Before reacting, it's worth confirming the cause really is competitive, not internal. Auction insights lets you compare your performance against other advertisers in the same auctions and see whether new players have shown up, or whether existing competitors have grown their impression share. The report is available for Search, Shopping, and PMax campaigns.

It helps to know upfront that Smart Bidding already manages typical seasonality automatically. The dedicated tool, seasonality adjustments, is recommended only when you expect a major conversion rate change, since the system already handles ordinary seasonal events on its own. So if the current dip falls within a historically typical seasonal cycle, Smart Bidding is likely already adapting to it, and no additional action is needed.

The key thing to understand: CTR and ROAS measure fundamentally different things, and strength in one doesn't automatically carry over to the other. The official Quality Score component Expected CTR measures how likely a click when the ad shows for a given query, relative to competitors. That's a purely predictive measure of copy appeal and query relevance, and it doesn't factor in what happens after the click or the economics of the conversion at all.

The official tool for separating products by type (promotional versus core) is custom labels in the product feed. They let you group products by any business logic within listing groups, seasonality, margin, promo participation, and target or analyze each label independently, instead of relying only on standard attributes like category or brand.

Official documentation directly describes the mechanic behind this temporary drag on the account average. The length of the learning period depends on three factors: how many conversions the campaign, ad group, keywords, or products get, how long the conversion cycle is, and the bid strategy itself (Manual CPC isn't affected by this period at all). A strategy calibrates to objective over up to 3 weeks or 1 to 2 conversion cycles, meaning performance is genuinely unstable during that window not because anything is broken, but because the system is still collecting data.

Official Target CPA documentation directly names the site as a separate, non-advertising factor in results: actual CPA depends on factors outside our control, such as changes to your website or ads, or rising competition in auctions. Google itself officially separates causes into "advertising" ones (ads, bids, competition) and "site" ones, rather than attributing everything to campaign settings.

This effect comes from the same Smart Bidding adaptation logic that applies to any significant change in conditions. A sharp rise in conversion during a promotion, followed by a sharp drop once it ends, counts as a significant change for the bid strategy too, requiring calibration time of up to 3 weeks or 1 to 2 conversion cycles, depending on data volume and conversion cycle length. The problem is that during the promotion itself, the strategy adapted to unusually high conversion and more aggressive bids, and once the promotion ends, it has to "unwind" that adaptation, a process that also takes time, during which ROAS can look worse than the business's real underlying performance.

The mechanics of accounting for returns were already covered as a technical setup: conversion adjustments let you restate or retract after the fact. For estimating the actual scale of returns' impact on final ROAS, a separate capability matters: since uploading an adjustment requires an adjustment time, you can segment your conversion data and see how much time typically passes between the original conversion and its later correction. That's a direct way to gauge how "delayed" the effect of returns is on your reporting.

The official mechanism built specifically for this scenario is the conversion window. The setting is ideal for businesses selling products with a a longer buying cycle the standard 30-day window. Google is directly acknowledging that the default setting doesn't suit every business model, and provides a dedicated official tool for long cycles instead of forcing everyone into one standard.

Auction Insights shows which competitors you overlap with; a different competitor mix explains a gap on its own. The Search Terms report can reveal a subtler semantic difference within a group.

Smart Bidding, broad match because the wider set of queries gives the system more data to learn from.

Google defines landing page experience as content usefulness, navigation ease, link count, and match to ad expectations. Absent from that definition: price, reviews, form length, checkout convenience, payment options, trust. A page can score well and still convert poorly for reasons Google Ads doesn't measure.

Ad scheduling bid adjustments only for Maximize Clicks. Under other strategies, Smart Bidding optimizes automatically automatically.

Google confirms that previously, increasing the daily budget on a "Limited by budget" Target CPA or ROAS campaign could cause a decline. Starting August 17, 2026, campaigns should hold closer to target regardless of budget.

Genuine seasonality is gradual; a structural break typically shows a sharp drop on a specific date. Seasonality Adjustments are meant for a short, notable shift, not a decline spread across many weeks.

Most search ad traffic is, by definition, new visitors. The New vs. returning segment shows new customer counts and lifetime value separately. The new customer acquisition cost column shows what it costs to acquire a new customer.