How Do I Check My Conversion Tracking Without Sending Test Leads?

Google Ads is claiming more leads than your sales team remembers, and you want to know whether the tracking is broken without dropping another "test, please ignore" form into the CRM. Every test lead triggers a follow-up and clutters the pipeline report. Unless you clicked your own ad first, it never shows up in Google Ads anyway.
You can check most of your conversion tracking without a single test lead. Reconcile a settled week of Google Ads conversions against ad-sourced CRM leads. Audit which conversion actions count and how. Then use preview mode to see what fires before anyone submits. Only the final link, a real submission firing the tag, needs a test, and recent traffic usually proves that already.
Does Google Ads agree with your CRM?
Reconciliation is the strongest check you can run because it tests your tracking against real visitors instead of one staged visit. Pull a full week of leads from your CRM, along with form notification emails and call logs if phone leads matter to you. Put them next to the conversions Google Ads reports for the same dates.
Two adjustments make the comparison fair.
- Compare against ad-sourced leads only. Google Ads counts a conversion only when it follows an ad interaction, so organic and direct leads in the CRM should never appear on the Ads side. If your forms capture the GCLID or UTM source, filter on that. If they don't, the comparison is rougher but still catches gross gaps.
- Pick a week that has had time to settle. The standard Conversions column credits each conversion to the date of the ad click, not the day the lead arrived, so last week's figure keeps rising as late converters come in. The "by conversion time" columns line up better with how your CRM dates its records.
Then read the direction of the gap, because it tells you which failure you have.
- Google Ads reports several times more leads than the CRM. That points to a tag firing twice, a tag firing on the wrong event, or more than one conversion action counting the same lead.
- Google Ads reports fewer leads. That points to a form path with no tag, or to leads arriving by a route you never tracked, such as people who see an ad and phone you directly.
If Ads comes out ahead, the wider guide to finding double-counted leads when Google Ads shows more than your CRM walks through tracing which source is inflating the count.
Most teams skip this check because it means two exports and a spreadsheet every time. SproutMe Companion handles it as a question instead. It works from a data lake that ingests Google Ads alongside HubSpot and Shopify. Asking what Ads claimed last week against what landed in HubSpot returns a grounded comparison rather than a manual reconciliation.
Which conversion actions are actually counting?
If the numbers disagree, look next at the conversions summary under Goals in Google Ads. You're checking three things there, and none of them needs a visitor.
Names and sources. Read every active conversion action and ask what real business event it represents. The usual culprits are:
- actions called "Page view" or "Session start"
- GA4 events imported alongside a native Google Ads tag that tracks the same form
A lead generation account rarely needs more than a handful of conversion actions. A long list usually means old setups were added and never retired.
Primary or secondary. Only primary actions feed the Conversions column and bidding. If two primary actions record the same form submission, every lead counts twice. That happens in your reports and in what the bidding algorithm optimises towards.
Count setting. For leads, set Count to "One." Then a person who submits twice, or reloads the confirmation page, is counted once. "Every" is for purchases, where repeat transactions are genuinely separate revenue.
This audit catches most double counting, but not all of it. The full set of causes is covered in why Google Ads counts more conversions than you're getting.
What does preview mode show before a submit?
Settings tell you what's configured. Preview mode tells you what actually fires, and much of that is visible without submitting anything.
Open Google Tag Manager's Preview mode, or Tag Assistant if your tags are hardcoded. Use a browser that hasn't clicked your ads. Then run three checks.
- Load the form page and do nothing. If your lead conversion tag fires now, it's attached to a page view rather than a submission. Every visitor who reaches the form is being counted as a lead. This is one of the most frequent reasons dashboards outrun CRMs.
- Load the thank-you page directly by typing its URL. If the conversion fires on that page view, then refreshes, bookmarks and back-button visits all count as new leads. A conversion tied to a confirmation page isn't wrong in itself. It's only as reliable as the page is hard to reach without submitting.
- Count how many times the conversion tag fires on a single page load. Two firings usually means the tag exists twice. A common example is a hardcoded gtag snippet left in place after the same conversion was rebuilt in Tag Manager.
These are real hits. Without an ad click, though, they won't register as Google Ads conversions, so they don't pollute your account the way a test lead pollutes your CRM.
When do you still need one test lead?
Everything above stops short of one thing: proving the tag fires when a real submission succeeds. Preview mode can't fully settle that, for two reasons.
- A tag can fire even when the form itself fails.
- Forms that submit without loading a new page can only be checked by submitting them.
Usually you don't need to prove it separately. If ad-sourced leads in the CRM track closely with Google Ads, real visitors have already run the test for you, many times over.
A deliberate test earns its place in three situations:
- You've just changed the form, the site or the tag.
- The account has too little recent volume to reconcile.
- Google Ads reports fewer leads than the CRM, and you need to find the untagged path.
When you do run one, make it count.
- Search for the business and click your own ad once, so the conversion can register.
- Submit the form with "TEST" in the name field.
- Watch in preview that the tag fires after the submission, not on load.
- Confirm the lead reached your inbox or CRM.
- Delete the lead or mark it there so it never reaches a sales rep or a pipeline report.
One labelled test is a reasonable cost. A habit of firing test leads every time a number looks odd isn't, because each one muddies the data you're trying to check.
Conclusion
You don't need a test lead to find out whether your tracking is wrong. Each check answers a different question:
- Reconciliation shows whether Google Ads and the CRM agree, and which direction they disagree in.
- The conversion list shows what is counting and how.
- Preview mode shows what fires before anyone submits.
Together they catch double counting and wrong-event tags, the failures that inflate dashboards, using only real traffic and a browser. Save the test lead for the one thing only a submission can prove, and run it once.
See how Companion puts what Google Ads claims next to what reached your CRM, from one grounded view of spend and pipeline.
Frequently Asked Questions
Google Ads records a conversion only when it follows an interaction with one of your ads. Suppose you reached the site directly or through an organic result before submitting the form. The tag may fire perfectly and Google Ads still won't count it. To test end to end, click your own ad once first, then submit. Allow some time for the conversion to appear in reporting.
Largely, yes. The Meta Pixel Helper Chrome extension shows which browser events fire on the page you're viewing, so the same page-load checks apply. A lead event firing on the form page, or on a directly loaded thank-you page, is a wrong-event problem. Events Manager's overview also shows each event's volume and whether it arrives from the browser, the server or both.
Yes. The two systems date and deduplicate records differently. Conversion windows let leads arrive days after the click, and a CRM may merge contacts that Google Ads counted as separate conversions. A modest difference either way is expected. The warning signs are a gap of several multiples, or a gap that suddenly widens after a site, form or tag change.
Get a complimentary audit to uncover AI opportunities hidden in your data.
Put these strategies to work


