The short answer: when Google Ads reports zero conversions, the most common cause in a small business account is not that customers stopped enquiring. It is that the thing which counts enquiries stopped counting. The two look identical inside the advertising platform and completely different once you put the website’s own activity beside it. This is how the HighRegard application tells them apart, why it refuses to let anyone act on the wrong reading, and what to check yourself if you do not use it.
Why the platform cannot tell you
Google Ads learns from the conversion actions it is given. If the booking event stops firing because a form plugin was updated, a tag was removed in a redesign, or a consent banner began blocking the tag, the platform does not know the signal is broken. It knows only that conversions fell to zero. Smart Bidding then does what it is built to do: it chases whatever conversion signal remains, which may now be clicks on a phone number rather than bookings, and the cost per conversion it reports becomes a number about the wrong thing.
The owner sees a dashboard that says the campaigns have stopped working. The natural reaction is to cut spend. That is the moment the mistake becomes expensive, because the campaigns were probably fine.
What we look at instead
The application connects Google Ads, Search Console and Google Analytics 4 read-only and runs a short set of checks each time the data refreshes. None of them is clever on its own; the verdict comes from reading them together.
Did the signal stop while the activity continued? We compare the last seven days of platform conversions against the trailing four weeks, and do the same for sessions and for the site’s own lead events in GA4: form submissions, WhatsApp clicks, call clicks. If conversions fell to zero or near zero while sessions and lead events held within their normal range, the pattern is a stopped signal, not a stopped business.
Which conversion actions are steering the bidding? We count how many actions are marked primary and what kind they are. Six primary actions with a click-type action outranking the booking action is a hygiene fault that produces exactly this symptom over time.
Does the booking event still reach both places? A booking-type event that appears in GA4 but not in Google Ads points at the import; one that appears in neither points at the site.
Is the data itself fresh and complete? A provider that has not delivered facts for the last two days is stale, and the application says so before anything is scored. Stale is never silently served as current.
The verdict, and what it blocks
The checks combine into a tracking-health score and one of four verdicts: healthy, degraded, likely tracking failure, or not yet assessable. The score only counts checks that could actually run; a check that could not run because a source is not connected neither passes nor fails.
A verdict of likely tracking failure does two things. It puts a plain warning at the top of the overview, and it blocks every recommendation that depends on platform conversions: budget increases, exact-match expansions, schedule and location changes, incrementality tests. Those items stay visible so nobody wonders where they went, but they cannot be accepted or assigned until the tracking recommendation is done. Ranking them lower would not be enough; a low-ranked “increase budget” is still an invitation to act on a broken number.
If you want to check this yourself
Open GA4 and look at the event that represents an enquiry for the last four weeks. If it is still arriving at the usual rate while Google Ads shows conversions collapsing, do not touch the budgets. Make a test enquiry end to end and watch for it in GA4’s DebugView, then in the Google Ads conversions report the following day. The fault is nearly always in one of three places: the site (the event no longer fires), the consent layer (the tag is blocked before consent), or the import (GA4 sees it, Google Ads does not).
Fix that first. Only then does the question “are the campaigns working?” have an answer.
The application’s demo workspace is built around exactly this scenario, on synthetic data, so you can see the verdict, the blocked items and the checks without connecting anything. See the platform page or open the live demo.
Next step: if this raised questions about your own visibility, there are three honest ways to answer them. The free snapshot gives you three verified findings from your own site. The Website Revenue Audit (£295) gives you the full evidenced picture. And if you would rather not do the fixing yourself, the Repair Sprint (£795) implements the fixes for you. Or simply ask us directly.