What should I do if ROAS drops sharply when I try to raise the budget on a tROAS campaign?
What to check before you touch anything
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.
Did ROAS actually drop in the same segments that used to drive the main results, or did it drop because the campaign started reaching new, less-converting segments (broader audience/keyword coverage following the bigger budget)? Different causes.
Did the budget increase overlap with the tail end of a learning period? If you raised the budget while the campaign hadn't yet exited "Learning" from a previous change, the effect of the budget increase compounds with that instability.
How much time has passed since the budget increase? A sharp ROAS dip in the first few days after a change is an expected part of the strategy's adjustment cycle, not necessarily a sign of a problem.
Could the drop reflect exhausting the "easy" pool of demand — meaning that at the old budget, the system was already efficiently capturing all the high-margin/high-converting traffic, and at the higher budget it now has to reach for lower-quality demand to spend the extra money?
How exactly did the keyword mix shift as the budget grew? There are two fundamentally different scenarios to distinguish here. First: the search terms themselves are converting worse within the existing keyword set (the same keywords and terms have simply gotten less effective — a traffic-quality or auction question). Second: the split between efficient and "junk" terms has shifted — your previously strong-performing keywords are still just as effective, but as the budget grew, the share of impressions going to low-quality/near-miss search terms grew too (terms that barely got any traffic before). These are two different problems: the first calls for a look at the traffic/offer itself; the second calls for negative keywords and tighter match types first, not a change to budget or target.
Possible approaches
If the drop follows a sharp rather than gradual budget increase, a sensible move is to go back to a more gradual pace of growth (steps of 15–20% with pauses to stabilize) rather than trying to hit your target volume all at once.
You can temporarily loosen the target (lower tROAS a bit) during the scale-up period, accepting a temporary dip in efficiency as the cost of expanding volume, then gradually bring the target back as things stabilize.
Google generally warns that a substantial budget change can trigger a new learning cycle — give the campaign the same settling-in period you'd give it after a target change before drawing conclusions.
If the breakdown by segment shows the drop is coming from reaching new, less-converting segments, consider a narrower expansion instead (don't raise the budget sharply for the whole campaign — grow it specifically where ROAS is still strong, and test new segments separately).
If ROAS still hasn't recovered after a reasonable waiting period, that may be a sign the campaign has already hit the ceiling of available quality demand at the old budget — in that case, it's more sensible to roll the budget back and look for growth elsewhere (new campaigns, channels, segments) rather than continuing to push for scale on this specific campaign.
If the breakdown shows the real issue is a shift in the mix (a growing share of impressions going to lower-quality search terms), the fix is targeted: tighten negative keywords and match types where that shift happened, rather than revisiting the whole campaign's budget or target.
Comparing the keyword mix "before" and "after" a budget increase by hand is a heavy lift — you'd need to line up spend, conversions, and ROAS for every search term across both periods and separately isolate what changed: the terms' own performance, or their share of the overall mix. Our tool (DataMind) does this automatically: it compares your keywords across both halves of the period and explicitly shows whether the ROAS drop is driven by the search terms themselves performing worse, or by a growing share of low-quality terms in the overall mix — so you know what to fix first, before touching budget or target at all.
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.
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 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.
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.
