GA4 Conversion Tracking Mistakes That Inflate Your ROAS

A campaign shows 6.2x ROAS. The conversion column is healthy. Revenue is climbing. So the obvious conclusion is that the campaign is working.

But what if one purchase was counted twice? What if a $50 enquiry was assigned a $500 value? What if Google is optimising towards an action that your sales team doesn't even consider a qualified lead?

The problem isn't necessarily that GA4 is "wrong." The problem is that your tracking can be technically active while your conversion data is commercially misleading. And when that data feeds Google Ads, a tracking mistake doesn't just change a report. It can influence how you judge campaigns, allocate budget and measure return.

Here's what to check before you trust that ROAS.

How Can GA4 Conversion Tracking Inflate Your ROAS?

ROAS is based on a simple calculation:

ROAS = Conversion value ÷ Ad spend

The calculation itself isn't complicated. The problem is what gets counted as conversion value.

If GA4 records a purchase twice, assigns too much value to an action, or counts an event that doesn't represent genuine revenue, the calculation can still be mathematically correct while the business result is misleading.

One terminology point matters here. In GA4, important events are now called key events. When a key event is important for Google Ads measurement or bidding, it can be used to create a Google Ads conversion.

The current flow is:

Event → Key event → Conversion

So the question isn't simply whether your events are firing. It's whether the right events are being measured, valued and used for optimisation.

This post focuses specifically on conversion tracking and its effect on ROAS. If you want a wider first-pass check across your whole GA4 setup, Is Your GA4 Actually Set Up Correctly? A 15-Minute Self-Check covers that in about 15 minutes.

7 GA4 Conversion Tracking Mistakes That Can Inflate Your ROAS

When Your Conversion Count Is Wrong

1. The Same Purchase Is Being Counted More Than Once

This is one of the easiest ways to make revenue appear out of thin air. Imagine a customer places a $500 order. Your purchase event fires once when the order is completed, then fires again when the confirmation page reloads.

You still have one $500 sale. Your analytics may receive two purchase events. Now your reporting can potentially show $1,000 instead of $500.

Common causes include:

• A purchase tag firing more than once
• A confirmation page being refreshed
• Multiple tracking implementations recording the same purchase
• A plugin and Google Tag Manager both sending the purchase event
• Poorly configured event triggers

For ecommerce, transaction_id is particularly important because GA4 can use the same transaction ID to identify duplicate purchase events.

One order should represent one order. Your analytics shouldn't be more excited about the sale than your payment system is.

2. More Than One Tracking Setup Is Measuring the Same Outcome

You might have:

• GA4 purchase event
• Google Ads conversion tag
• Plugin-generated tracking
• Google Tag Manager implementation

all intended to measure the same purchase.

Using GA4 and Google Ads together isn't automatically a problem. The issue is overlapping implementations that aren't deliberately coordinated.

Before assuming your tracking is duplicated, map out:

If two or more systems are independently recording the same outcome, establish exactly how those signals are being handled.

When Your Conversion Value Is Wrong

3. You're Treating an Important Action Like It Has Revenue Value

Not every useful conversion represents revenue. A B2B business might track:

• Quote requests
• Phone calls
• Contact forms
• Demo requests
• Brochure downloads

Those actions can absolutely matter. The problem starts when your measurement treats every action as though it represents the same commercial outcome.

A brochure download isn't equivalent to a $5,000 sale. A low-intent form submission shouldn't automatically carry the same economic weight as a qualified lead that becomes a customer.

The important question is:

If I removed this conversion from my report, would I actually be removing business value?

If the answer is no, it probably shouldn't be doing the heavy lifting in your ROAS calculation.

4. Your Conversion Value Doesn't Match the Real Value

Suppose every lead is assigned a $500 value because that's your average customer value. But your actual leads aren't equal:

If every conversion is reported as $500, your platform isn't seeing reality. It's seeing the value you've instructed it to use.

For ecommerce, this can happen when the actual transaction value isn't passed correctly.

For lead generation, it can happen when a static value is used even though lead quality varies significantly.

For monetary events, check that the value being sent is numeric and that the associated currency is correct.

Your ROAS is only as meaningful as the value attached to the conversion.

5. Your Purchase Event Fires Before the Purchase Is Actually Final

A purchase event should represent an actual completed transaction. But depending on how your website is implemented, the event can fire at a point in the checkout process that doesn't perfectly correspond with money actually changing hands.

For instance,

Customer submits checkout → purchase event fires → payment fails

Your analytics may have recorded a purchase. Your bank account hasn't. This matters particularly for businesses using:

• Payment gateways
• External checkout pages
• Failed-payment flows
• Manual payment confirmation
• Delayed order approval
• Order cancellation processes

You need to establish exactly what event represents a completed commercial transaction for your business and make that the measurement point.

6. Refunds and Cancellations Never Make It Back Into Your Data

You make 100 sales. Analytics records the revenue. Then 10 customers cancel or receive refunds. If your measurement doesn't account for those reversals, your reported revenue can remain higher than the revenue your business actually kept.

That means you're comparing:

Reported revenue

against

Ad spend

instead of:

Revenue your business actually retained

against

Ad spend

So don't stop your tracking audit at:

"Did the purchase event fire?"

Also ask:

"What happens to that purchase in our data if the customer later gets a refund?"

When You're Optimising Towards the Wrong Thing

7. Google Ads Is Optimising Around the Wrong Conversion

Here's where a technically perfect setup can still produce a bad marketing signal. You might have several events marked as important in GA4. That doesn't mean Google Ads should optimize around all of them.

For example, your account might track:

• Page views
• Form starts
• Phone clicks
• Quote requests
• Qualified leads
• Purchases

All six can be useful for analysis. But if Google Ads is optimising around a low-value action instead of the outcome you actually want, the platform receives the wrong signal.

That's the distinction between:

"We're tracking it."

and:

"We want Google to optimize for it."

Your tracking can be technically flawless and still be strategically wrong.

Can a High ROAS Still Be Misleading?

A high ROAS isn't automatically a tracking problem. Your campaigns may genuinely be performing well. But if the number is being calculated from duplicated, incorrectly valued, or poorly chosen conversions, the result can look stronger than the business outcome behind it.

Differences between GA4 and Google Ads can also occur for legitimate reporting and attribution reasons. That's different from having incorrect conversion data.

If you're seeing different numbers across the two platforms, it's worth separating a genuine attribution difference from an actual tracking problem. Our breakdown of Why Your GA4 Numbers Don't Match Google Ads (And Which One to Trust) explains where those differences can come from and what you should actually investigate.

A reporting difference isn't automatically a tracking error. An unexplained business-value difference deserves investigation.

Audit Check: Does Your ROAS Survive a Reality Check?

Before trusting an unusually strong ROAS, check three things:

If your ROAS looks unusually good, start by reconciling these three things: conversions, conversion value and actual business outcomes.

How to Check Your GA4 Conversion Tracking in 10 Minutes

You don't need to rebuild your entire measurement setup to perform a useful first check.

1. Identify your important events. List the events currently being treated as key events or used as Google Ads conversions.
2. Identify what each one actually represents. Is it a purchase, qualified lead, button click or something else?
3. Trigger the conversion yourself. Complete the relevant action and confirm that the event fires.
4. Check whether it fires once. For purchases, verify the transaction ID and make sure refreshing a confirmation page doesn't create another transaction.
5. Check the value. If the event represents money, verify that the value matches the actual transaction.
6. Compare it with the real business outcome. For ecommerce, compare reported purchases and revenue with your store or payment system. For lead generation, compare reported leads with your CRM or qualified enquiries.
7. Check what Google Ads is actually optimising for. A key event can be useful for Analytics without necessarily being the conversion you want guiding ad optimisation.
8. Look for overlapping implementations. Map your GA4, Google Ads, GTM and plugin-based tracking.

If the numbers don't line up with your backend, don't stop at the GA4 report. Understanding where analytics data diverges from actual customer and sales records is essential, especially when you're using that data to judge campaign performance. See Why Your GA4 Data Doesn't Match Your CRM or Backend Sales for a deeper look at the problem.

Then ask:

If I removed every conversion that doesn't represent genuine business value, would my ROAS still look this good?

When Your ROAS Looks Too Good to Be True

The point isn't to assume that a high ROAS is wrong. It's to make sure you can explain why it's high.

If you want to go beyond conversion tracking and examine the wider GA4 setup, How to Audit GA4: The Complete Google Analytics 4 Audit Guide covers the broader measurement picture, including data collection, events, attribution and reporting.

How Swishiy's Google Ads Auditor Can Help

Conversion tracking problems become harder to investigate when you're looking at several campaigns, conversion actions and months of Google Ads data at once.

That's where Swishiy's Google Ads Auditor comes in, giving you a closer look at what's actually happening across the account.

The tool analyses the last 90 days of Google Ads data and looks at areas including conversion tracking, search terms, brand vs non-brand performance and wasted spend. It works in read-only mode, so it doesn't make changes to your account.

When you're trying to determine whether unusual campaign performance is coming from the campaigns themselves or from the data behind them, Swishiy's Google Ads Auditor gives you a practical starting point for identifying areas that deserve a closer look.

Marketing Truth Check

Final Thoughts

A conversion isn't valuable because GA4 counted it. It's valuable because it represents something your business actually cares about.

That's why conversion tracking deserves more than a quick "tag is firing" check. The real audit is whether the data travelling from your website into GA4 and Google Ads still represents what happened to your money, your customers and your sales.

Before you optimise for a great ROAS, make sure you've earned the right to believe it.

If you're ready to take a closer look at your marketing performance, explore Swishiy to discover the tools and resources designed to help you make better decisions from your data.