Static Round Value Detection
Every conversion value on this account is a round number. 10, 25, 50, 100, 500. Real e-commerce values include cents and odd amounts (47.99, 129.43, 312.18). Round-everywhere values almost always mean someone configured a static default in Google Ads and the tag is not actually passing the real order total. Smart Bidding sees fake revenue and optimizes against it.
Why It Matters
When a Google Ads conversion action is set to "Use the same value for every conversion," the team picks a single number and every conversion ships with that value. Round numbers are easy to pick. A "Lead" gets configured as 50 dollars. A "Purchase" gets configured as 100 dollars. The dashboards populate with neat totals (5,200 dollars in leads, 12,000 dollars in purchases) and the team feels like value-based bidding is working. It is not working. Target ROAS needs real value variance to distinguish high-value traffic from low-value traffic. A static value collapses that variance to zero. Every conversion looks identical to the optimizer. The campaign drifts toward count optimization while the dashboard pretends ROAS is being measured. When the same finding shows up in both the Google Ads settings export and the Performance report (every reported value is also round), the suspicion firms up. Real-world transactional value, even averaged across an account, rarely produces clean round numbers. If both sides are round, the dynamic value pipeline almost certainly does not exist on this account.
How To Fix It
- Confirm the business actually has transactional value variance to capture. E-commerce purchases, paid leads, SaaS signups: yes. Free newsletter signups, content downloads: probably no.
- For events with real value variance, switch each Google Ads action to "Use different values for each conversion" and wire the GTM tag to pass `{{DLV - ecommerce.value}}` from the dataLayer.
- For events without real value variance (a fixed-price lead), keep the static value but refresh it to match the rolling average reported by sales or the CRM.
- Verify in GTM Preview that the value field on a test conversion matches the order total in the commerce backend.
- Wait one reporting cycle and confirm the reported values now include realistic decimals and variance.
Example
Configured values: Purchase = 100.00, Lead = 50.00, Signup = 25.00
All multiples of 25. No decimals. Almost certainly static defaults.Every configured conversion value on this Google Ads account is a clean round multiple. Per Google's value-based-bidding documentation, Target ROAS and Maximize Conversion Value optimize against per-conversion value variance; uniformly round values typically indicate static defaults (configured under "Use the same value for every conversion") rather than real transactional value flowing from the site dataLayer. The result is value-based bidding that runs against a flat signal, which collapses to count optimization while the dashboard reports neat-looking but synthetic revenue totals. Fix: confirm whether each action has real per-transaction value variance, switch eligible actions to "Use different values for each conversion" with the value sourced via a Data Layer Variable, and refresh any genuine static defaults to match the current rolling average. 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