The PPC Clean-Up: How to Audit and Fix ‘Value Inflation’ in Google Ads
All Paid Media PPC News Social MediaAdvertising Video Advertising Columns Ask A PPC ExpertNEW PPC Pulse Webinar Google Local Services Ads Are Moving To PMax: What To Check First Prepare for Google's LSA move into Performance Max with a before-and-after audit checklist from CallRail. Digital Marketing All Digital Marketing Analytics & Data Ecommerce Lead Generation Content Marketing Social Platforms Google YouTube Reddit LinkedIn TikTokNEW WordPress Other CMS Platforms Webinar Google Local Services Ads Are Moving To PMax: What To Check First Prepare for Google's LSA move into Performance Max with a before-and-after audit checklist from CallRail. SEJ Live Webinars Rundowns PodcastNEW Ebooks All Resources Rundown Why Your Brand Drops Out of AI Answers Five articles on the signals behind citation fluctuation, where models source citations, and how to audit your content for AI visibility gap Advertising On SEJ Case Study: B2B SaaS Banner Ads Webinar AI Cites Your Brand. Now What? Turn AI Visibility Data Into Actions Turn your AI visibility reports into a prioritized AEO action plan with practical guidance from Ahrefs. Smart Bidding optimizes toward whatever value you feed it. Here's how to find inflated conversion data before it trains your tROAS on fiction. Sarah Stemen 6 hours ago ⋅ 12 min read Sarah Stemen Owner at Sarah Stemen, LLC Bio Follow Many paid ads accounts have a problem in the settings and with values. On the surface, nothing looks broken with the ad account. The campaigns run, keywords match intent, reporting appears healthy. But underneath all of that sits a corrupted value signal feeding Smart Bidding the wrong story and data. When advertisers notice the discrepancy, their immediate reaction is to blame the ad platform for over-reporting. In reality, the platform isn’t broken; it’s following the instructions it was given. When an account is running tCPA or tROAS on autopilot without validating the underlying conversion math, Smart Bidding optimizes toward phantom value rather than actual revenue. Over time, what tends to happen is that the paid ad account drifts into an inflated state. This presents as a wide gap between what ads are generating and what the business sees day to day. A good phrase for this is “value inflation,” and it is what happens when the dollar figure Smart Bidding is optimizing toward doesn’t reflect what the business actually collects in revenue. This isn’t the result of fraud or platform trickery. It’s almost always a self-inflicted tracking issue that can happen for several common reasons. And value inflation matters more now than it did five years ago because Smart Bidding doesn’t grade its own homework. tCPA and tROAS accept whatever value has been set as truth. If the numbers are inflated, the algorithm will aggressively pursue more inflated numbers, chasing ghost conversions, raising CPCs to win auctions for “high value” clicks that were never actually high value, and burning budget in the exact direction it was instructed to go. The account looks like it’s performing well on the surface. This is the audit to run before trusting a single tROAS target in an unverified account. Value inflation rarely shows up as one glaring error that is obvious. It’s usually three or four small distortions stacked on top of each other, each one nudging the algorithm a little further from reality. Individually, each of these looks like a rounding error in the ad account. Stacked together each one of the issues can inflate the reported account value by 20% to 40% without a single alarm going off in the interface, because Google Ads has no way of knowing the “conversion value” isn’t real. Google Ads and Microsoft Advertising just see a number, and its job of the bidding algorithm is to get more of the goal number. It is really easy when looking at platform data all day to end up confused: tCPA and tROAS are not wrongly reported. The bidding is doing exactly what it was instructed to do with the data provided in conversion settings. Target ROAS bidding works backward from a value target. The account will bid and spend more where the expected return-per-dollar clears the bar, spend less where it doesn’t. If half the “conversions” are inflated, the algorithm’s model of what a good customer looks like gets skewed toward whatever behavior generated those inflated values, not toward the best actual buyers. It will bid up placements, audiences, and search terms that produce noise, because noise is what is rewarded. Smart Bidding recalibrates continuously based on recent conversion data. Inflated values don’t just distort today’s bids but instead they train the model for weeks, sometimes months, depending on the conversion volume. By the time the CFO asks why CAC is climbing while the platform says ROAS is healthy, the algorithm has already built an entire bidding strategy around a fiction. Run this checklist in order. Each step either confirms the data is clean or points directly at the solution Open Goals > Conversions > Summary and pull every active conversion action with its category, count, value, and whether it’s marked primary or secondary. This helps determine two things: conversion actions marked primary that shouldn’t be influencing bids, and value-based goals sitting next to count-based goals with no differentiation between them. Confirm every conversion action is running data-driven attribution and not still defaulting to last-click on an older action that predates the account’s migration. Mixed attribution models across conversion actions in the same account will produce wildly different value patterns for what should be comparable conversions, and it’s one of the most common issues in inherited accounts that nobody thought to check after Google forced the DDA transition. Pull the Tag Diagnostics view in Google Tag Manager or Google Analytics 4’s DebugView and fire a real test conversion through the funnel. Watch for the same conversion event firing twice, once from a hard-coded gtag snippet still sitting in the page code and once from GTM, or a “confirmation page load” firing independently of the actual form submission event it’s supposed to represent. This single issue alone could be responsible for reported conversion volume. Pull the last 90 days of Google Ads-attributed conversion value and put it next to actual closed revenue or actual fulfilled orders from the CRM or order management system for the same window. Use GA4’s Advertising snapshot and a custom exploration comparing Google Ads-reported conversions against GA4’s own purchase or key event counts for the same campaigns and date range. A large, consistent gap between what Google Ads claims it drove and what GA4 recorded as an actual purchase event is a signal that value is getting inflated somewhere between the click and the conversion action firing, which is not a GA4 tracking problem to dismiss. Before updating a single setting and fixing the entire account, document and build the paper trail. It is important to be able to show, in numbers, exactly where the inflation is coming from. Finding the inflation is half the job. The other half is rebuilding the value structure so it doesn’t creep back in six months from now. Move every non-revenue action, which would be content downloads, video engagement, chat starts, or account signups, out of primary and into secondary or “observation” status. The bid strategy should only ever be optimizing toward actions that represent real, recognized value to the business. If a lead needs to be qualified before it’s worth anything, don’t let the raw lead volume drive bids on its own; that belongs in an offline conversion import once it’s qualified, weighted appropriately below. For OCT, import value at the stage that reflects reality, not the stage that looks best. If the close rate on sales-qualified leads is 20%, either import at a probability-weighted value or import the full value only once the deal is actually won, with a value adjustment made for deals that fall through later. Google Ads has just sunset new offline conversion imports through the legacy Ads API in favor of the Data Manager API, so if the OCT pipeline hasn’t been touched recently, this is the moment to rebuild it correctly rather than patch the old one. For e-commerce, confirm the dynamic value feed is passing net order value, which is post-discount, post-tax where applicable, and adjusted for returns via conversion adjustments and not gross cart value at checkout initiation.
Source: Search Engine Journal
This article has been carefully curated and reformatted for educational and informational purposes. Full credit goes to the original publisher.
📚 Visit more helpful articles on Joab Peters Blog
No comments