Google Ads Conversions Dropped? Check Tracking Before Changing Bids

If Google Ads conversions suddenly drop, check whether the business is actually receiving fewer leads or orders before changing bids. A reporting problem and a performance problem can look very similar in the account. They need different fixes.

Start with three questions: are customers still converting, is the conversion event reaching Google Ads, and has enough time passed for the data to appear? Once you know where the gap is, you can make a more informed decision about the campaign.

Compare the same outcome across systems

Pull a small sample of confirmed leads or orders from your business system and compare it with the event you expect the advertising platform to record. Keep the date range, time zone and event definition consistent.

A submitted inquiry and a qualified lead are two different things. So are an order placed and a payment completed. If the reports measure different outcomes, matching the totals will not tell you whether tracking works.

Then check what changed. Was there a website release, a new checkout flow, a consent update or a change to the conversion import? Record the last confirmed successful event and the first confirmed failure. Include the affected conversion action and any device or browser pattern you can reproduce.

This gives the person fixing the issue something specific to investigate. “Conversions are down” is a starting point. “Orders are still coming in, but the purchase event stopped after Tuesday’s checkout release” is actionable.

Use a data exclusion only for a confirmed data issue

Google’s guidance describes data exclusions for conversion-data problems affecting conversion-based Smart Bidding in Search, Display, Shopping and Performance Max. An exclusion changes the data used for bidding. It does not fix conversion reporting.

The date range applies to clicks, so account for the conversion delay rather than simply entering the outage dates. In Google Ads, go to Tools, Adjustments, then Exclusions. Add the incident details, dates and affected campaigns and devices, and check the scope before saving and creating the exclusion.

I would have someone else review that selection before applying it. A mobile-only checkout issue does not automatically justify excluding data across the entire account. Write down why each campaign and device is included.

A genuine fall in demand needs a different investigation. Do not use an exclusion to remove a disappointing period simply because the numbers are below target.

Test the repair, including the paths that failed

Here is a hypothetical example. A retailer updates its checkout on Tuesday. Payments continue, but the purchase event stops reaching the advertising platform. The team reproduces the failure, fixes the implementation and completes a controlled test.

The test should confirm that the expected event arrives once, with the correct value and currency. Then repeat it across the relevant checkout paths. If the problem affected mobile, a successful desktop test is not enough to close it out.

Keep an owner and a short record of what was tested, what passed and what still needs attention. Use internal references instead of sharing customer details unnecessarily.

Google’s outage guidance says performance can still fluctuate after an exclusion. It advises against removing an applied exclusion and generally discourages backfilling; where backfill is needed for reporting after an exclusion, wait at least five days after applying it. Review the guidance with whoever manages your imports before making that change.

The campaign may still need a budget or bidding adjustment. Make that decision with a clear understanding of which data is reliable, what has been repaired and what remains uncertain.

If you need help finding the gap between business outcomes and platform reporting, MetaVari Media’s analytics and measurement services can help you work through it.