How to Set Up Google Ads Target ROAS
Set up Google Ads Target ROAS by preparing reliable conversion values first, choosing a campaign or portfolio scope that shares one value model, calculating a realistic return target, and checking that budget and demand can support the decision. Target ROAS does not create value data; it uses the values Google Ads receives to prioritize auction opportunities.
Use this as a planning sequence before editing the bidding setting. For the deeper implementation and troubleshooting checks, read how to set up Google Ads Target ROAS correctly and the current Google Target ROAS guide.
1. Decide what conversion value means
Choose the value before choosing the target. For ecommerce, it may be order revenue, contribution margin, or another approved amount. For lead generation, it may be expected pipeline or a value imported after qualification. Write the currency and the rules for taxes, shipping, discounts, refunds, or close-rate weighting so the value is understandable outside the ad account.
Target ROAS can only optimize the value that is reported. If the account sends the same value for every order despite large differences in economics, the strategy cannot distinguish them. If a form submit is given a high arbitrary value, the campaign may find more forms without finding more revenue. Use the Google value-based bidding guide to check whether a value strategy fits the goal.
2. Verify conversion actions and values
Inspect the actions that will be included in the campaign’s optimization goal. Confirm that the tag or import fires at the real completion event, fires once, reports the correct transaction value and currency, and uses the intended primary or secondary setting. Check conversion windows, attribution, consent, transaction IDs, offline uploads, and Analytics imports.
Compare a recent period with the source of truth: an order system, finance report, CRM, or call platform. Look for duplicated purchases, missing values, unexplained currency changes, and values arriving after the click period. If the signal is not reliable, repair it before starting Target ROAS. Google’s conversion value best practices explain how to improve the foundation.
3. Choose standard or portfolio scope
Use a standard strategy when one campaign has a distinct budget, product mix, margin, or return requirement. Use a portfolio only when several campaigns can share the same conversion actions, value definition, target logic, and business constraint. A portfolio can pool useful data, but it can also hide a low-margin campaign inside an acceptable aggregate return.
List the campaigns that will be included and the rule for adding or removing one. Do not group campaigns only because they advertise the same company. A brand campaign and a non-brand product campaign may have different economics; two regions may have different sales capacity; two product groups may have different return rates.
4. Calculate a defensible initial target
Calculate historical conversion value divided by ad cost and multiply by 100. Use a completed conversion window that excludes the most recent period in which values may still be arriving. Include the actual product, geography, campaign, and customer mix that will be managed under the new target.
Then compare the observed return with the minimum acceptable business return. The initial target should be a realistic constraint, not the percentage the business hopes to reach eventually. A target set far above recent performance can restrict delivery and reduce total value. A lower target may open more auctions but can be unacceptable if the additional sales lose money.
Record the calculation, the period, exceptions such as promotions, and the decision owner. Google may show a recommended target based on recent results; use it as evidence to inspect, not as an automatic answer. The Target ROAS settings documentation describes the current implementation and target behavior.
5. Check budget and campaign readiness
Set an average daily budget that the business can sustain while the strategy learns. Confirm that the campaign has eligible demand, approved ads or feed items, working final URLs, and enough opportunity for value data to be useful. If a small number of orders can move the return percentage dramatically, treat the early period as provisional.
Review the feed, product availability, price, shipping, promotions, landing page, and conversion event for ecommerce. Review lead qualification, sales capacity, location, schedule, and response time for lead generation. A bidding setting cannot compensate for inventory that is unavailable or a form that sales cannot follow up.
6. Apply the setting and save the baseline
In the campaign or shared bid-strategy area, select Target ROAS or the current equivalent label shown by the account, choose the primary value goal, enter the target, and confirm the budget and scope. The exact controls depend on campaign type and account eligibility, so follow the interface and current Google documentation rather than copying a screenshot from another account.
Before saving, record the previous strategy, target, budget, included campaigns, conversion actions, value definition, and date. Note whether the change is a new launch, a transition from another value strategy, or a change to an existing target. This baseline makes the result explainable.
7. Plan the first review
Do not judge the target from the first day. Wait through the relevant conversion delay and compare completed periods. Review actual value per cost, total value, spend, conversion count, product or lead mix, margin, and lost opportunity. Check whether the target changed delivery as intended.
Avoid changing target, budget, feed, creative, landing page, and conversion values simultaneously. If a tracking correction is necessary, annotate the break and reset the comparison window. If actual return is below target, check delay, missing values, demand, feed, and target strictness before raising or lowering the percentage.
For a correctness-focused implementation review, see how to set up Google Ads Target ROAS correctly. The adz.so product overview is a truthful next step for reviewing supported account settings; it does not create conversion values or promise a particular ROAS.