The number in your Conversions column is not a count of jobs. It is the output of a set of configuration choices — which actions you decided to count, how you told Google to count them, and which of those actions you marked as important. Change the settings, and the number changes without a single extra customer calling you.

So when an owner says "I got 47 conversions last month but nowhere near 47 leads," that's usually not Google lying. It's the account counting things the owner never intended to count.

Here's how to find out what yours is actually counting, and what to fix.

Step one: read the conversion actions table, not the campaign report

In Google Ads, go to the Goals icon, then Conversions, then Summary. This table is the source of truth. For every row, you want four things:

  • The name and source (website, phone calls, Google Analytics, import)
  • The Count setting (One or Every)
  • Whether it's Primary or Secondary
  • The Tracking status — Google shows a status column here, and if it says something other than recording conversions, that action is broken (Google Ads Help)

A typical local account that has been through two agencies and a website rebuild will have something like eight to twelve rows in this table. Form submissions from the old site. A GA4 imported event. A "contact page view." Two different phone call actions. A leftover "click to call" tap. Several of them fire on the same visit, several are marked Primary, and all of them get added into one number.

That's the whole problem in most cases. Not a broken tag — too many working tags.

The counting setting: One vs Every

Every conversion action has a Count setting. Google's documentation is direct about it: One is for leads, where only one conversion per ad click adds value to your business, and Every is for sales, where each one genuinely counts (Set up conversions manually).

For a plumber, a roofer, a dentist, a law firm — almost everything you track is a lead. One person filling out one form is one lead, even if they hit refresh on the thank-you page, even if they come back and fill out a second form two days later. Google's own guidance on understanding conversion data says to use "One" for leads specifically to prevent duplicate counts from page refreshes (Google Ads Help).

If your form conversion is set to Every, your lead count is inflated and your cost per lead looks better than it is. Fix it. Note that the change only applies going forward — it does not restate your historical data (About conversion counting options).

Primary vs Secondary is the lever nobody touches

This is the setting that decides which actions inflate your headline number and which ones just sit there for observation.

Primary actions are reported in the Conversions column and used for bidding, as long as the goal they belong to is the one your campaign is optimizing toward. Secondary actions are observation only — they show up in the All conversions column and are not used for bidding, with the one exception that a secondary action inside a custom goal will be used for bidding (About primary and secondary conversion actions).

So the cleanup rule is simple. Decide what a real lead is for your business. Usually that's two things: a submitted contact form and a phone call that lasted long enough to be a conversation. Those are Primary. Everything else — contact page views, chat widget opens, PDF downloads, newsletter signups, GA4 engagement events — goes Secondary.

Google's documentation on conversion goals flags this explicitly: misconfiguring primary and secondary settings can undermine Smart Bidding (About conversion goals). This matters more than it used to, because automated bidding and Performance Max both take your conversion signal at face value. If you tell the system a contact page view is a conversion, it will happily go buy you cheap contact page views. That's the mechanism behind a lot of "Performance Max spent my budget and I got nothing" stories — worth reading alongside our piece Should a Local Service Business Run Performance Max?

One caution when you make changes: Smart Bidding needs a learning period of roughly 7–14 days to stabilize after conversion goal changes, per Google's documentation. Make your fixes in one pass, then leave it alone.

Phone calls: where local accounts go wrong most often

For a service business, the phone is the conversion. And there are several different ways to track it, which look similar in reporting and mean completely different things.

Google lists them separately: calls from ads (call assets and call-only ads), calls to a phone number on your website, clicks on a number on your mobile website, and imported call conversions (About phone call conversion tracking).

The distinction that matters: a tap on a phone number is not a phone call. "Clicks on a number on your mobile website" counts the tap. It doesn't know whether the call connected, whether anyone answered, or whether it lasted two seconds. If that action is Primary in your account, your conversion count includes misdials and hang-ups.

The actions you want use a Google forwarding number and a minimum call length. You set the duration, and calls that last at least that long count as conversions. Google also now offers the option of using AI to analyze call recordings to identify high-quality leads instead of using a duration threshold (Measure calls from ads).

Two practical notes:

  1. Call reporting has to be enabled in your account settings for duration-based call conversions to work — that's what puts the forwarding number in place (Google Ads Help).
  2. Check the Call details report before you pick a minimum length. It shows actual call durations, so you can set the threshold based on your real answered-call pattern rather than a default. If calls are being placed but not counting as conversions, a threshold that's too high is a documented cause.

Also worth knowing: the default counting method differs by call type. "Calls from ads" defaults to One conversion per interaction, while website-based conversion actions default to Every (Google support documentation). Don't assume — look.

Enhanced conversions, and what changed in 2026

Enhanced conversions supplements your existing tags by sending hashed first-party data — email addresses, for example — using SHA-256, which Google matches against signed-in accounts to attribute conversions more accurately (Google Ads Help).

Two changes are relevant right now. First, enhanced conversions for web and for leads have been combined into a single on/off setting; as of April 2026 Google accepts user-provided data from website tags, Data Manager, and API connections without you choosing an implementation method, and existing users are being migrated automatically. Second, if you or your CRM upload offline conversions or enhanced conversions for leads, that traffic moved to the Data Manager API and was blocked in the Google Ads API starting June 15, 2026 (About enhanced conversions for leads). If a Zapier or HubSpot integration silently stopped feeding conversions this year, that's the first thing to check.

There's also an enhanced conversions diagnostics report inside Google Ads that flags the usual failure causes — missing or badly formatted user data, or in-page code that isn't implemented correctly. Use it rather than guessing.

Two gotchas that quietly break otherwise-good setups

GA4 imports. If you import conversions from Google Analytics and also have a native Google Ads tag firing on the same form, you're counting the lead twice. Also, only events marked as key events in GA4 are eligible for import at all (Set up your web conversions). Pick one system as the source of truth for each action.

Tag Manager and blank values. If you're using GTM and leave the Conversion Value field empty, Tag Manager sends the value as 0 (Tag Manager Help). That's fine if you don't use value-based bidding, and a problem if you do.

Why your numbers will never match your CRM exactly

Even after a clean setup, the Google Ads number and your job board won't tie out. That's expected, not a bug:

  • Google Ads reports conversions on the date of the ad interaction, not the date the conversion happened. A call today from a click three weeks ago lands on that older date.
  • Conversions can be reported up to 90 days after the click, so recent weeks keep filling in.
  • Some conversions are modeled — cross-device behavior, for example — rather than directly observed.
  • Google retroactively removes conversions it identifies as spam or invalid traffic, which can look like a small drop in past data (Data discrepancies: Factors and troubleshooting).
  • The click-through conversion window itself is a setting you chose: 1 to 90 days for Search, Shopping, and Display (Google Ads Help).

The goal isn't a perfect match. The goal is a number that moves in the same direction as your booked work, in roughly the same proportion, so you can make decisions with it.

The cleanup, in order

  1. Open Goals → Conversions → Summary. Screenshot it before you touch anything.
  2. Kill anything with a broken tracking status or a tag that no longer exists on your site.
  3. Decide your two or three real leads. Set those Primary. Everything else Secondary.
  4. Set every lead-type action to Count = One.
  5. Enable call reporting. Check the Call details report, then set a minimum call length you can defend.
  6. Demote any phone-number-tap action to Secondary.
  7. Remove duplicate GA4 imports where a native action already covers the same event.
  8. Turn on enhanced conversions and check the diagnostics report.
  9. Wait two weeks before judging performance. Bidding has to relearn.

Do that and the Conversions column starts meaning something. It won't equal your job count, but it will be a consistent proxy — which is all a bidding algorithm needs, and all you need to decide whether to spend more.

If you'd rather work from a fixed sequence than a checklist — the exact conversion actions to build, what to name them, what to set them to, and how to sanity-check the data before you trust it — that's what the Launchpad system walks through.

One last thing. Before you rebuild anything, check that the tag is actually on every page of your site, including any new landing pages. The Google tag is meant to be installed sitewide, with event snippets on the specific pages that matter (Use the Google tag for conversion tracking). A surprising amount of "tracking is broken" turns out to be one page a developer forgot.