A report can say leads went up and still be wrong. It can say leads went up because one visitor reloaded a page four times in a row, or it can hold steady while a form has been failing quietly for weeks. Both look like a normal week. Neither one raises a flag on the chart, because a chart only shows the number it was given, never whether that number was earned honestly. Our measurement page puts it plainly: a number you can't trust is worse than no number, whether it's too high or too low, and either way it comes down to a number nobody checked before trusting it.
Can a lead get counted twice?
Yes, and it happened on our own site before we caught it. We had a lead counted in Google Ads every time our own thank-you page loaded, not when the form was confirmed received. Reload that page, reopen it from a bookmark, hit the back button and then forward again, and Google Ads counted another lead for the exact same person. One real inquiry could look like three or four. That distinction matters because ad budgets get decided on this exact number, and a number inflated by reloads makes a campaign look better than it is. Anyone reading that report would think the ads were working better than they were, and might spend more money trying to explain a number that was never moving. It was just a page being reloaded. A lead should be counted once, at the moment the form is confirmed received, not once for every time a page loads. The page after the click is where this usually happens, because it's the page a person is most likely to reopen, screenshot, or revisit while they wait to hear back.
Can a lead get lost without anyone knowing?
Yes, and this direction is worse, because nothing in the report moves at all. On a site we run, the contact form showed the words "Message sent" every time somebody submitted it, while every one of those inquiries was failing behind the page. The key that connects the form to the email service had been switched off, and the page never knew it. It kept showing the same confirmation it always shows, for an inquiry that had already reached nobody. Nobody could say how long it had been happening, because there was no record anywhere that it was happening at all. The form reported zero problems and delivered zero inquiries, and a zero looks exactly like a quiet week.
A form that says "Message sent" is trusted precisely because it doesn't invite doubt. Nobody double-checks a confirmation screen. That trust is exactly what makes this kind of failure expensive: it can run for as long as nobody happens to call and ask why they never heard back.
The fix wasn't a smarter form. It was making sure the page could never say a message was sent unless it was: every entry is now saved to our own database first, before anything is sent anywhere, then sent to the email service second. If the email service is down, it tries again on its own. If an entry still fails, a person is alerted, instead of the form quietly claiming a message arrived that never did.
What is a conversion in Google Ads?
A conversion in Google Ads is whatever action the account was told to count, nothing more and nothing less. Google Analytics calls a similar thing a key event: its name for an action somebody marked as worth watching, like a form submitted or a page reached. A lead is neither of those exactly. A lead is a real person who asked for something, by phone, by form, or in person. The trouble starts when a conversion or a key event gets set up to count something that isn't a lead, a page load instead of a confirmed form, for instance, which is exactly what happened on our own site. Ask whoever manages your account, plainly, what a conversion in that account is counting. If the answer isn't a real inquiry, it's worth finding out what it is instead.
None of this is only a Google Ads problem. A lead might come from a search ad, a social post, an organic Google or Bing search, an AI answer, or a referral from a past customer, and every one of those sources needs the same honest count behind it. Google Ads just happens to be the clearest example, because the mistake shows up as a number you can actually point to.
Does it matter what my website is built on?
Yes. Counting a lead once, at the moment the form is confirmed received, and saving every entry before it's sent anywhere, both require control over what the form does behind the page. Template website builders such as Wix and Squarespace keep the form, and everything that happens after it, inside their own system. In our experience, that can be rigid enough that these checks are hard, and sometimes not possible, to put in place, depending on the plan and how the site was set up. That doesn't make them a bad choice. For plenty of businesses, a template builder is a sensible, fast way to get a site up.
If your site runs on one of these, ask whoever built it three questions: where is every form entry stored, what happens to an entry if the email never sends, and what exactly triggers a lead being counted. If nobody can answer those three plainly, that's the finding, whatever the site is built on.
Why both mistakes look the same on a report
An owner checking a weekly number cannot tell the difference between leads being up and one person reloading a page, and cannot tell the difference between leads being flat and a form quietly failing. Telling them apart means opening the actual record, not the summary chart, and counting what is there, one entry at a time. That is the same argument the follow-up system makes about inquiries themselves: the number that matters is never the one at the top of a dashboard, it's the one you get from checking each entry by hand.
Both directions cost real money. One makes you spend more pursuing an improvement that never happened, the other lets real inquiries disappear without a trace.
Counting honestly is a marketing operations job, not an accident of good software. A named person should own the lead count the same way a named person owns each new inquiry, and that person checks it against the real record on a schedule, not once a year when something finally looks wrong.
Phone calls have their own version of this problem. A call that rings through and gets answered often never gets logged anywhere, so a phone line that is genuinely busy can look, on paper, like a website that is underperforming. Working backward from income starts from an honest count instead of a convenient one.
Setting up Google Analytics and Google Ads so a lead is counted correctly, and only once, is a skill of its own, not a box a website builder checks for you automatically. Whoever sets it up for you should be able to show you, in plain language, exactly how a lead gets counted. Our own measurement work is led by Robert Earl, who holds Google's Google Ads Search Certification and its Conversion Optimization Certification.
What can you check yourself this week
You don't need access to anyone's analytics account to find out where your own numbers stand. Three checks, none of which require software you don't already have:
- Call the phone number on your own ad and see whether anyone answers, and whether it gets recorded anywhere if they do
- Fill in your own contact form as if you were a stranger, and track exactly who receives it and how fast
- Reload your own thank-you page once, then look at whether your lead count in Google Ads moved, and ask whoever runs the account to remove that test entry afterward
None of these checks require guessing. They just require doing the thing a customer does and watching what happens, instead of trusting a dashboard to tell you.
If any one of those three comes back wrong, what you paid for the click already bought you less than the report says it did, and no amount of extra ad spend fixes a number that was never honest to begin with.
Checking what your own reports are really counting is work we do. If you want us to take a look, get in touch.
Questions owners ask
How can a lead be counted more than once in Google Ads?
It happens when the count is tied to a page loading instead of a form being confirmed received. If the thank-you page fires the count on every load, reload, or reopen, one person can be counted as several leads. The fix is to trigger the count once, at the moment the form is confirmed received, and never again for that same submission.
What is the difference between a conversion, a key event, and a lead?
A conversion is whatever action a Google Ads account was told to count, nothing more. A key event is Google Analytics' name for an action someone marked as worth watching, like a form being submitted. A lead is a real person who asked for something, by phone, by form, or in person. The three are not automatically the same thing, and the trouble starts when a conversion or a key event gets set up to count something that isn't really a lead.
Why would a form say it worked when it didn't?
Because the page that shows "Message sent" and the process that sends the message are two separate things, and most forms never check that the second one succeeded before showing the first. If the connection to the email service breaks, the page can still display its usual confirmation while every inquiry disappears behind it, with nothing recorded anywhere to say so.
Does it matter if my website is built on Wix or Squarespace?
It can, because these checks depend on having control over what a form does behind the page, and template builders keep that behind their own system. In our experience that can be rigid enough to make honest counting hard, sometimes impossible, depending on the plan and how the site was set up. That isn't a knock on the platforms themselves. Ask whoever built your site where every entry is stored, what happens if the email fails, and what triggers a lead being counted. If they can't answer, that's worth knowing.
Who should own the lead count in my business?
One named person, the same way one named person should own each new inquiry when it comes in. That person checks the lead count against the real record, the inbox, the phone log, the form entries, on a regular schedule, not just when a number looks strange. Without an owner, a wrong count can run for months, because everyone assumes somebody else is watching it, and nobody actually is.
From the field
A page load is not a person. A number worth trusting is checked, not just watched.