Common Google Ads Target ROAS Mistakes
Common Google Ads Target ROAS mistakes usually start before the target is entered. Advertisers may report the wrong value, combine incompatible campaigns, ignore conversion delay, set a percentage above achievable demand, or celebrate a high ROAS while total value and margin fall. Other mistakes include changing the feed and target together and treating revenue as profit without checking the economics.
Review the value pipeline and the business decision first. The current Google Target ROAS guide explains platform behavior; this article focuses on the operating errors that make an otherwise valid setting misleading.
1. Treating revenue as profit without checking the model
Revenue is visible and easy to report, but product margin, shipping, returns, discounts, payment fees, and customer support can make two orders economically different. A 500% revenue ROAS may be weak for one product and excellent for another. Calling it profit ROAS without changing the value model creates false confidence.
Avoid it
Write what the value field includes and compare it with the business return requirement. If contribution value is needed, implement it only when the data pipeline can calculate it consistently. Until then, label revenue-based ROAS as revenue-based and include the margin limitation in the review.
2. Assigning arbitrary values to easy events
An advertiser may give a high fixed value to a form, add-to-cart, or phone click because the account needs more value data. Target ROAS then learns to find the event, not the closed sale or profitable order. The percentage can look stable while the sales team sees worse opportunities.
Avoid it
Use transaction values or defensible expected values. Keep shallow events secondary when they should only help observation. Import qualified or closed stages when the CRM process is reliable. Google’s conversion value best practices should be checked before using a value event for bidding.
3. Ignoring duplicate or missing values
Duplicate confirmation-page events inflate value. Missing transaction values make high-value orders look like zero-value conversions. Currency mismatches, returns, Analytics imports, offline uploads, and transaction-ID errors can all distort the input. Target ROAS cannot distinguish a tracking issue from a performance issue.
Avoid it
Trace real orders or opportunities end to end. Check primary status, counting, value, currency, consent, deduplication, and delay. Compare Ads with finance or the CRM over the same completed period and annotate any implementation change.
4. Setting the target from a desired number
The business may want a 1,000% return, but the current campaign may not have enough demand, margin, or conversion history to achieve it. A target far above recent value per cost can make bidding selective, reduce spend, and shrink total value. The account may then be called “efficient” because it barely enters auctions.
Avoid it
Calculate historical value per cost after excluding recent conversion delay. Compare it with the minimum return and growth needs. Use a target range and document what would justify moving toward the desired end state.
5. Treating the ROAS percentage as a guarantee
Target ROAS is an average objective across auctions and conversions, not a promise for each order or day. Some conversions will exceed the target and others will fall short. Daily numbers can move because of mix, reporting delay, seasonality, and auction conditions.
Avoid it
Review completed periods and include total value, volume, mix, margin, spend, and conversion delay. Explain variance before changing the target. Use the strategy report and current Target ROAS settings guide as context, not as a reason to expect a fixed daily percentage.
6. Putting unlike campaigns in one portfolio
A brand campaign, a high-margin product group, a low-margin product group, and a lead campaign may all report value but not share one business constraint. A portfolio can hide the weak member behind the strong member and make the aggregate target look healthy.
Avoid it
Pool campaigns only when conversion actions, values, currency, product or lead economics, targets, and budgets can be interpreted together. List the inclusion rule and owner. Keep distinct targets separate even if the campaign names are similar.
7. Changing target, budget, and feed at once
Changing a target at the same time as price, product availability, creative, landing page, budget, and value logic destroys the baseline. A strong result cannot be attributed to the target, and a weak result cannot be diagnosed.
Avoid it
Change one material variable, record the date and hypothesis, and wait through the conversion cycle. Fix an urgent tracking or product defect immediately but mark it as an interruption. Create a new baseline whenever the value definition changes.
8. Raising budget because the campaign is limited
“Limited by budget” may indicate lost opportunity, but additional spend can also buy low-margin products, irrelevant queries, or leads the team cannot serve. More budget magnifies the consequences of a bad value signal.
Avoid it
Inspect marginal traffic and quality before funding it. Define the incremental value and margin that would make the increase worthwhile. Raise budget in a controlled step and compare total value, incremental value, and business capacity. Check Google’s average daily budget documentation for spend behavior.
9. Splitting data too aggressively
Creating a separate Target ROAS for every product, region, device, and keyword can make each system unstable. A theoretical difference is not always a reason for a separate bidding decision. Thin data can be harder to read than a broader campaign with a common value model.
Avoid it
Separate only when the business needs a different target, budget, margin, or owner. Keep the structure proportional to the available volume. Review mix in reports before creating a new campaign.
10. Judging a new value model too soon
If value reporting or offline qualification recently changed, the old and new periods do not measure the same outcome. Recent clicks may still produce value, and sales stages may arrive days or weeks later. A quick target change can lock the account into a response to incomplete data.
Avoid it
Define the delay, wait for a comparable window, and label the transition. For a repeatable process, use how to optimize Google Ads Target ROAS and Google Ads Target ROAS checklist. The adz.so product overview can help review supported settings; it does not repair values, judge margin, or guarantee a target return.