Tag: ROAS

I used to think bad data mainly meant bad reporting. Now, in Google Ads, I see it as something much more expensive: bad delivery. When conversion data is wrong, it does not just make a dashboard confusing. It can train campaigns to spend budget chasing the wrong people.

As automation takes over more of the ad-buying process, from creative generation to bidding, data has become one of the few inputs I can still control. It may also be the most important one, because automation can only optimize toward the signals I give it.

I keep coming back to one question: what is worse, a brilliant ad shown to the wrong audience or an average ad shown to the right one? The first burns budget on people I do not want. The second may not win every click, but when someone does engage, at least they are closer to the customer I actually need.

That is why I have to ask myself a harder question before launching any automated campaign: did I spend more time verifying the data than writing the ad copy?

The cost of bad data has changed

A few years ago, bad tracking was mostly a reporting problem.

If a tag fired twice, a conversion was mishandled, a value came through incorrectly, or offline conversions stopped working for a few weeks, the main result was a dashboard that did not add up. It was frustrating, but the damage was usually limited. Someone would eventually question the numbers in a monthly review, I would trace the issue, fix it, and the next report would look cleaner.

That same data now feeds the algorithm buying paid media. Smart Bidding does not wait for me to interpret a report or sit through a monthly review. It reads conversion data and acts on it before I may even notice that something is broken.

The same wrong number now creates a very different outcome. A bad number in a report requires an explanation in a meeting. A bad number in a conversion action used for bidding costs money immediately, because the algorithm does not know the signal is wrong.

It simply optimizes toward that signal the moment it sees it, and it does so efficiently.

Google does not understand my funnel or my business

Google may let me label conversion actions as “lead,” “opportunity,” or something similar, but those labels are mainly for organization. The platform does not truly understand where each conversion event sits in my funnel.

What it sees is a conversion event with a numeric value attached to it, usually a currency value. It does not inherently know that a newsletter signup might be worth $2 in eventual value, a lead might be worth $60, and an opportunity might be worth $400. To Google, those are conversion events. Without better signals, it has no real context that one may be worth 200 times another.

The algorithm is not optimizing for my business outcome by default. It is optimizing for the data I provide. If that data is wrong, the optimization will be wrong too.

For example, if every form submission fires the same conversion with the same default value, I give the system no clean way to separate low-intent inquiries from high-value prospects. The algorithm treats them the same. And because low-quality leads are often cheaper to acquire, it can quickly flood the account with them.

The cost per lead may drop from $40 to $25, and the dashboard may make performance look more than 35% better. But behind that cleaner metric, the pipeline can dry up as genuinely qualified inquiries quietly fall by half.

Dig deeper: Why better signals drive paid search performance

3 ways bad data quietly wrecks delivery

Bad data can show up in different ways, but I see three issues that are especially likely to derail campaign delivery.

1. Wrong event

If I optimize for a top-of-funnel action like a page view while the real conversion events happen further down the funnel, the algorithm learns to buy more of those cheap events. The problem is that the lower-funnel activity may never follow.

2. Wrong value

If I count every conversion equally, or assign every conversion the same placeholder value, I hide the real differences in business value. When actual value can vary by 10 times or more, the algorithm will often chase the easier, lower-value conversions because they are cheaper to acquire.

3. No data

This problem does not get discussed enough. A complete break in conversion data can damage a campaign faster than almost anything else.

On Day 1, the algorithm starts wondering where the conversions went. By Day 2, it begins assuming they may not be coming back. By Day 3, it can start making serious bidding changes. Within a week, many campaigns can throttle themselves down to almost nothing.

How I pick the right signal for Google

So how do I fix this? I start by choosing the signal that best represents business value, not just the easiest action to count.

Take a typical lead generation business. Some leads will never convert, while others may be worth 10 times as much as the rest.

If the form asks the right qualifying questions, I may already know which leads are which. But if I optimize for every submitted lead using a target CPA, I am telling Google that all leads are equally valuable.

Imagine an account spending $20,000 a month at a $40 target CPA and generating about 500 leads. Only 150 qualify, and maybe just 50 are genuinely high value. A basic lead may be worth $60, a qualified lead may be worth $200, and a high-value lead may be worth $600. That is a 10 times spread in value.

In that situation, I have several ways to improve the optimization signal.

Optimize for a qualified lead: I can create a new conversion action, such as “qualified lead,” and fire it only when a lead has real value. Then I can move the target CPA strategy to that conversion action, knowing the campaign will ignore leads with no value. The advantage is that I train the campaign on a more meaningful signal. The downside is that every qualified lead is still treated equally.

Assign conversion values and use target ROAS: I can add a currency value to the qualified lead based on the potential revenue it could generate if it becomes a sale. Then I can switch the campaign to target ROAS, allowing Google to optimize for return instead of simply counting leads. The tradeoff is that it may still buy larger numbers of lower-value leads if it can acquire them at the right price.

Optimize for a high-value lead: I can create a “high-value lead” conversion event that fires only for top-tier leads, with or without a conversion value. Then I can optimize with either target CPA or target ROAS, depending on whether I care more about acquisition cost or return. The advantage is stronger lead quality. The downside is that, depending on spend and volume, the data may be too limited to support this approach until the account scales.

These are only a few possible optimization signals, and they do not even go deeper into the funnel. I can apply the same thinking to lower-funnel milestones by creating separate conversion actions for events such as contacted lead, qualified contact, or high-value contact.

Targeting and measurement can be different

This sounds simple, but the conversion event I optimize for and the one I report on are not always the same. In many cases, they should not be the same. One trains the algorithm. The other tells me how that training is performing.

In the example above, a client or internal stakeholder may still want to see cost per lead. That is a valid metric. But the campaign may be optimizing for the Qualified Lead conversion, not the original lead submission.

I can keep the original lead conversion running purely as a reporting metric, so stakeholders still get their cost-per-lead view while the campaign bids on the qualified lead signal that actually reflects business value.

Same campaign. Two conversions. Two very different jobs.

That brings me back to the question I started with: did I spend more time verifying the data than writing the ad? In an automated account, data is no longer just measurement. Data is strategy.

---

Inspired by this post on Search Engine Land.

---