How do I test lowering tROAS without risking a sharp spike in spend?
What to check before you touch anything
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?
Traffic type. Will lowering the target behave the same way on brand and non-brand traffic, on search and on Performance Max/Shopping? Different traffic types react differently to a looser target, and testing them all together in one blanket step is riskier than testing them separately.
Demand capacity. How large is the reserve of volume beyond the current target? If the market is large and the campaign is heavily target-constrained, even a small loosening can suddenly open the door to a lot of spend; if the market is small, the risk of a runaway spend spike is lower.
Competition. How competitive is the segment the campaign would likely expand into with a looser target? In a highly competitive environment, loosening the target can sharply raise cost per click before conversions catch up, growing spend faster than results.
What's the current daily budget, and does it naturally protect against a sharp spend spike on its own? A budget cap is a built-in risk limiter, and it's worth explicitly factoring that into how you plan the test.
Is there enough current data to correctly interpret the test's result at all, rather than reacting to random noise on a small sample?
How much efficiency has already been squeezed out of the current assets. Before scaling by loosening the target, it's worth understanding whether the campaign already has elements dragging the overall result down (consistently weak keywords, underperforming ads, or product groups) that just aren't visible yet against the backdrop of a high overall ROAS. As volume grows (which is exactly what happens when you lower tROAS), the system will inevitably lean more on these marginal assets — and if they're already weak, scaling won't just make them "dip a little," it could mean they contribute no revenue at all while still eating budget. Testing a lower target on a campaign with undiagnosed weak assets is riskier than testing on a campaign where you already know which elements deliver a stable (within) contribution and which are riding on a random (mix) effect.
Possible approaches
The standard, lowest-risk approach is to test the reduction through a Campaign Experiment on a slice of traffic — this caps the possible spend increase to the experiment's share rather than the whole campaign, and lets you compare the new and old setup under the same conditions.
If an experiment isn't available or practical, you can lower the target in small steps (10–15% at a time) with pauses to stabilize between them, watching spend and ROAS at each step, rather than jumping straight to your desired target value.
Google typically shows an estimate of the expected increase in spend and conversion value when you lower target ROAS — worth checking that estimate before testing, as a sense of the likely scale of the effect.
While testing a lowered target, it's smart to keep your daily budget as an explicit safety ceiling (don't remove the budget constraint at the same time as loosening the target) — that reduces the risk of runaway spend growth even with an aggressive target change.
If the campaign's structure includes segments with very different competitive intensity and traffic type, you can test the lower target first on a less risky, more predictable segment (say, proven keywords with a history of stable ROAS), before rolling the change out to the whole campaign.
Figuring out ahead of time which assets and keyword segments deliver a stable contribution to results, versus which are riding on one-off spikes, is labor-intensive to do by hand for every element of a campaign. Our tool (DataMind) shows the breakdown of asset and keyword performance into a stable (within) versus random (mix) contribution — so before you start scaling, you can see which elements are safe to grow and which could drag results down as volume increases without generating revenue.
Related Content
Check the campaign's status in the interface — is there an explicit "Limited by budget" or "Bid strategy constrained by target" flag alongside the overperformance? These are two different root causes producing the same symptom.
Check the campaign's status — an explicit "Bid strategy constrained by target" flag alongside underspent budget (no "Limited by budget" flag, but actual spend running well under the daily limit) is a direct sign that the target is what's holding volume back.
How sharp was the budget increase, and when did it happen? A gradual 10–20% raise and an abrupt 2–3x jump lead to very different behavior — the latter almost always resets part of the strategy's accumulated learning.
What exactly is being passed as "value" — the full order amount (revenue), or an amount already net of discounts, shipping, and taxes? Different systems (your website, your CRM, Google Ads) may define "value" differently, and it's worth cross-checking line by line on a handful of real orders.
How is ROAS being calculated for each product? tROAS optimizes toward conversion value (by default, usually the sale price/revenue), not automatically toward margin. A high-margin product with a lower price and/or lower conversion potential can post a lower "raw" revenue-based ROAS than a cheap, low-margin, high-turnover product — and the system will end up underrating the very product that's more valuable to the business, unless it's told about margin separately.
Does Google Ads actually receive information about whether a purchaser is new or returning? Without that signal, neither a separate goal nor separate reporting is technically possible.
What attribution model does each system use? Google Ads defaults to its own attribution model (usually data-driven), and GA4 may use a different model (or the same model with different cross-channel distribution rules) — the mismatch may be purely a methodology difference, not an error.
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 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.
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.
