Conversion tracking for Google Ads gets explained as a settings task. It's closer to plumbing. Automated bidding on Google and Meta works mostly from one input: the conversions the platform knows about. It doesn't see your CRM, your call log or your bank account unless something sends that information across. When the signal is thin, late or wrong, bidding optimizes toward the wrong thing. And nothing on the dashboard looks broken.

So let's follow one lead.

Say someone in Tampa searches "emergency AC repair" on a Saturday, taps your ad and fills in your quote form. A hypothetical, but a very ordinary one. For that lead to become something Google's bidding can learn from, five things have to happen.

  1. The click carries an identifier. With auto-tagging on, Google Ads adds a click ID (the gclid parameter) to the landing page URL. Meta adds its own (fbclid) and relies on cookies set by the pixel.
  2. Your site records the action. A tag fires when the form is successfully submitted, usually through Google Tag Manager, sometimes hard-coded into the site.
  3. The action counts as a conversion. In Google Ads, a conversion action exists for it and is set to Primary, which is what bidding uses. In GA4, the matching event is marked as a key event, Google's newer name for what GA4 used to call conversions.
  4. The platform matches it back to the click. It uses the click ID, cookies and, if you've set them up, hashed customer details sent through enhanced conversions or the Conversions API.
  5. It arrives on time, ideally with a value. Bidding learns as conversions come in. A lead with a value attached tells it more than a lead without one.

Break any link and the platform either misses the lead or counts something that isn't one.

Where the chain usually breaks

No enhanced conversions

When the form is submitted, the Google tag can send a hashed version of the email address or phone number (Google uses SHA-256). Google matches that against signed-in users, which recovers conversions cookies alone would miss.

  • Symptom: Google Ads shows fewer conversions than you have leads, especially from iPhone and Safari users.
  • Where to look: the conversion action's settings in Google Ads, which show whether enhanced conversions is on and how its diagnostics look.

Meta Pixel only, no Conversions API

The Conversions API sends the same events from a server instead of the visitor's browser. Browser events get blocked by ad blockers, privacy settings and short cookie lifetimes. Server events are much less exposed to that.

  • Symptom: Meta reports noticeably fewer leads or purchases than your site or store does.
  • Where to look: Meta Events Manager. Check each event's connection method (browser, server or both) and its Event Match Quality score.
  • The catch: if you send the same event from both, they need a shared event ID so Meta can deduplicate them. Without it, you count everything twice.

Counting the wrong thing

This one hides behind good-looking numbers. Cost per lead looks great; your sales team says the leads are junk.

Common causes:

  • A thank-you page view is the conversion, and the page can be reached without submitting anything.
  • Every form counts, including newsletter signups and job applications.
  • Spam submissions count as leads.
  • The same lead counts twice: once through a GA4 import, once through a Google Ads tag, both set to Primary.

Bidding will happily find you more of whatever you count. Spam included.

Phone calls nobody sees

Plenty of US service businesses get a big share of their leads by phone. If calls aren't tracked, the platform sees part of your results and bids as if the rest never happened. Options include call assets with call reporting, website call conversions using a Google forwarding number (availability varies by country), or a call-tracking tool that passes calls back as conversions. Set a minimum call length, so a 9-second wrong number doesn't count.

Google's consent mode tells Google tags what a visitor has agreed to. If your site shows a cookie banner, the two have to be connected properly. Two failures we look for:

  • The banner blocks tags until consent, but consent mode isn't configured, so Google gets nothing at all from people who decline.
  • Consent defaults to "denied" for every visitor, including US visitors who never see a banner.

For traffic from the EEA and the UK, Google requires consent mode v2 (the ad_user_data and ad_personalization signals) for some of its measurement and personalization features. For US-only advertisers, which state privacy laws apply to you is a question for your counsel, not a tag setting.

Sales that close offline

If a lead turns into revenue days later in your CRM, Google and Meta never learn which leads closed. Offline conversion imports fix that by uploading closed deals tied to the click ID or a hashed email. That's the step that lets bidding aim at customers instead of form-fillers. It also needs a CRM someone actually keeps up to date.

A quick self-check

Answer yes or no:

  • Is auto-tagging on in Google Ads?
  • Does each real lead action have exactly one Primary conversion action?
  • Are newsletter signups, page views and scroll events set to Secondary, or not tracked as conversions at all?
  • Is enhanced conversions switched on, with no errors in its diagnostics?
  • Does Meta Events Manager show your main event arriving from both browser and server, deduplicated?
  • Are phone calls counted, with a minimum length?
  • Do last month's leads in Google Ads roughly match your inbox and call log?

That last one will never match exactly. Attribution windows and reporting dates make sure of that. But if one number is double the other, something in the chain is wrong.

Every "no" is a place where the platform is bidding on less than you know.

What fixing it does, and doesn't, do

Fixing the chain gives automated bidding better information. It doesn't guarantee more leads or cheaper ones: your market, offer, budget and competitors still decide most of that. What it does is make sure decisions get made on what's really happening, and that your reports and your inbox start telling the same story.

These menus and requirements change often. Before you touch a setting, check the current Google Ads, GA4 or Meta help page for that feature.

If you'd rather hand it over

Our Tracking & analytics setup is a fixed $1,450, delivered in 7 business days: GA4 and Google Tag Manager, up to 8 conversion events, Google Ads enhanced conversions, Meta Conversions API, consent mode v2, call and form tracking, a QA log, one Looker Studio dashboard and a handover doc. It's all built inside your own accounts, so it stays with you. For how tracking fits into ongoing work, see our tracking setup page.