Suspiciously Perfect ROAS
One or more of your conversion actions reports a ROAS that lands on an exact round number (1.0, 2.0, 5.0, 10.0). Real revenue divided by real spend almost never produces a clean integer. This pattern is the signature of a static value being applied to every conversion instead of the actual transaction value.
Why It Matters
When a Google Ads conversion action is configured with a fixed value (say, $50 per lead), and the spend distribution lands such that the conversion count multiplied by 50 produces an exact ratio against cost, you get a suspiciously clean ROAS. This often appears on lead-gen accounts where the value is a placeholder, on accounts where ecommerce value was hardcoded during initial setup, or on B2B accounts assigning a flat deal value to every form fill. Fixed-value conversions are not always wrong. A lead-gen account that genuinely values every lead at the same dollar amount can run that way. The problem is that Target ROAS bidding will learn the value is constant and stop differentiating between high-quality and low-quality leads. Every form fill gets the same weight, so the bidder optimizes for volume, not quality. The account ends up with more leads from cheaper sources and worse close rates.
How To Fix It
- Confirm whether the flagged conversion actions are intentionally fixed-value. Open Tools and Settings, Conversions, and check the Value setting on each.
- If the business has dynamic value (true revenue, deal size, LTV proxy), wire it: source the value from the data layer or offline import.
- If fixed value is genuinely correct, document it so future audits do not re-flag it, and consider whether Maximize Conversions is a better bid strategy than Target ROAS for these actions.
- For lead-gen, evaluate Enhanced Conversions for Leads with offline conversion uploads so closed-won revenue replaces the static placeholder.
Example
Action: Demo Request. Conversions: 86. ROAS: exactly 5.00. Cause: value hardcoded at $5 per lead.One or more Google Ads conversion actions on this account reports ROAS at an exact round number such as 1.0, 5.0, or 10.0. Per Google Ads conversion tracking documentation, ROAS is calculated as conversion value divided by cost, and on accounts with genuine transaction-level revenue this ratio is essentially never an exact integer. The pattern indicates a fixed or placeholder value applied to every conversion rather than a dynamic value sourced from the actual transaction or deal. While intentional fixed values are valid for some lead-gen models, they prevent Target ROAS bidding from distinguishing high-quality from low-quality outcomes and tend to push the bidder toward cheaper, lower-converting traffic. Fix: confirm whether each flagged action is meant to be fixed-value, wire dynamic values from the data layer or via offline conversion uploads where applicable, and consider Enhanced Conversions for Leads to replace placeholder values with closed-won revenue. Source: support.google.com/google-ads/answer/13064107.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit