How to Use Google Ads Target ROAS
Use Google Ads Target ROAS only when conversion values represent the business outcome you want bidding to pursue. Google’s Target ROAS guidance describes a Smart Bidding strategy that predicts conversion value at auction time and adjusts bids toward an average return-on-ad-spend goal. It does not make every order profitable, remove the need for budget control, or correct missing, duplicated, delayed, or placeholder values.
This guide is educational and does not change an account. Before enabling or changing Target ROAS, verify the conversion-value pipeline, currency, attribution, campaign scope, and historical maturity. For a structured account review, use the free Google Ads audit for agencies.
Define ROAS in business terms
ROAS is conversion value divided by advertising cost. Decide what “value” means before choosing a percentage:
- gross order revenue;
- net revenue after refunds and cancellations;
- contribution margin;
- predicted customer or lifetime value;
- another approved value that is consistently reported.
The value in Google Ads must be useful for relative bidding decisions. If all products have different margins but every purchase sends the same placeholder value, Target ROAS is not receiving the economic distinction the strategy requires.
Check whether value-based bidding fits
Target ROAS is for a value goal, not simply for getting more conversions. Compare it with Maximize conversion value, which pursues as much reported value as possible within a budget, and with Target CPA, which treats conversions around an average cost goal. Google’s bid-strategy overview maps those choices to different business objectives.
Target ROAS is more defensible when:
- transaction or lead values are sent consistently;
- values are comparable across the campaign or portfolio;
- the account can distinguish high- and low-value outcomes;
- attribution and conversion lag are understood;
- the target reflects the economics and available demand;
- the business can accept the possible volume tradeoff of a stricter target.
If the account cannot distinguish value reliably, repair the value source or use a simpler goal until the data is ready. A high target does not create high-value demand.
Audit conversion values before setup
Review the full path from ad interaction to the value used for bidding:
- event creation and deduplication;
- primary conversion and “include in Conversions” status;
- imported offline conversions and reporting delay;
- transaction currency, exchange-rate treatment, and account currency;
- refunds, cancellations, taxes, shipping, discounts, and margin;
- consent, lost events, repeat purchases, and customer-value rules;
- campaign, portfolio, manager-account, and product scope.
Google’s conversion-goal guidance explains that changing conversion goals or actions affects the signals used by value-based strategies. Record the current goal and the proposed change separately. Do not change the value definition and Target ROAS at the same time unless the change is required and the review plan captures both.
Separate platform value from business value
Create a reconciliation table:
| Layer | Question |
|---|---|
| Platform event | Was the conversion recorded once and in the intended action? |
| Reported value | What value and currency entered Google Ads? |
| Order or CRM record | Which transaction or qualified stage matched it? |
| Adjustments | Were refunds, cancellations, or later status changes applied? |
| Economics | Does the value represent revenue, margin, or approved proxy? |
| Bidding scope | Is this action included in the strategy’s value column? |
If a later business event changes the value, document the import timing and attribution effect before judging ROAS.
Choose an initial target from mature history
Use historical conversion value divided by cost as a reference, but exclude periods that are not comparable: tracking breaks, major offers, stockouts, unusual promotions, market changes, or immature recent data. Google’s current help guidance recommends reporting values across relevant campaigns for a period such as four weeks or three conversion cycles before moving to value-based bidding; use the current account documentation and the actual conversion cycle for the campaign.
Before setting a target, record:
- campaign or portfolio scope;
- mature date range and excluded lag period;
- conversion value, cost, and value distribution;
- traffic, budget, inventory, and fulfillment constraints;
- historical ROAS and the business-required return;
- target rationale, owner, approver, and review date.
Do not choose a target only because it is a round number or a recommendation. A target set far above historical performance can limit eligible traffic and value; a target set far below the business requirement can pursue volume that is uneconomic.
Configure scope and budget carefully
Decide whether the strategy applies to one campaign or a portfolio. Confirm that campaigns share a compatible conversion goal, value definition, market, and operating constraint. A portfolio can pool signal, but it can also hide a campaign-specific issue if the scope and business economics are not compatible.
Review:
- average daily budget and spend volatility;
- shared budgets and campaign priorities;
- product margin, stock, lead capacity, or sales response;
- target country, language, device, and customer mix;
- landing pages, offers, ads, feeds, and policy status;
- active experiments or other strategy changes.
Changing Target ROAS can affect traffic and total value as the system pursues the new average goal. Keep a record of the previous target and the reason for the change.
Monitor ROAS without using one number alone
Create a review view with:
| Dimension | What to inspect |
|---|---|
| Delivery | Spend, budget constraint, impressions, clicks, and eligible demand. |
| Value | Conversion value, value distribution, currency, and late adjustments. |
| Efficiency | ROAS versus target with conversion lag excluded or labeled. |
| Quality | Profit, refunds, cancellations, qualified pipeline, or repeat value. |
| Mix | Products, markets, devices, audiences, and query or placement changes. |
| Integrity | Duplicates, missing imports, goal changes, and tracking incidents. |
| Decision | Continue, adjust, isolate, or revert with a documented reason. |
Do not optimize the strategy to make the dashboard target look good while losing profitable volume. If value quality is uncertain, label the ROAS as platform-reported and review the downstream business result separately.
Handle target changes and seasonality
Avoid frequent, reactive target edits. A target change can alter auction participation, and conversions may arrive after the click or after an offline import. Make one controlled change where possible, keep the rest of the account stable, and define when the result will be reviewed.
Use a seasonality adjustment only for a specific, short-lived and predictable conversion-rate change—not for a recurring seasonal period the system should learn. Record the event, expected direction, dates, affected campaigns, and removal condition. Treat budget, inventory, price, page, and tracking changes as separate variables.
Google’s current documentation also notes 2026 label changes from “Maximize conversion value with a Target ROAS” to “Target ROAS.” Record the setting shown in the current interface and keep the underlying value-based objective clear in the change log.
Common Target ROAS mistakes
- sending gross values when the decision requires margin;
- sending the same value for products with different economics;
- including low-quality micro-conversions in the value column;
- evaluating recent data before conversion lag or imports mature;
- setting a target far above historical performance without a volume plan;
- changing value definitions, budget, page, and strategy simultaneously;
- treating platform ROAS as profit or qualified pipeline;
- ignoring stock, lead capacity, fulfillment, or refund constraints.
Fix the input or business contract before blaming the bidding strategy. Target ROAS can only optimize toward the value it receives.
Use a safe change checklist
Before approval, capture:
- business value definition and required return;
- conversion actions and values included in bidding;
- campaign or portfolio scope and exclusions;
- historical data range, lag, and target rationale;
- budget, inventory, lead capacity, and margin constraints;
- previous target, proposed target, owner, and approver;
- verification metrics, review date, and rollback condition.
An audit-first workflow can help surface tracking, structure, or reporting issues where its live checks cover them. It should not be described as setting Target ROAS or changing account bids unless that capability is explicitly live.
Practical next step
Start with one compatible campaign or portfolio. Reconcile reported value with the business source, choose a target from mature evidence, record the baseline, obtain approval, and review both value and quality after the relevant conversion cycles. If value is not trustworthy, fix measurement before enabling value-based bidding.
Use the free Google Ads audit for agencies to structure the pre-change review and keep the final bidding decision with the responsible account owner.