The short answer
- Google Ads counts a conversion when something happened. Your CRM counts a lead when a person exists. They are not the same event.
- Attribution windows, models and de-duplication all differ, so the numbers can never match exactly.
- The reconcilable number is revenue, because an invoice is a fact and a conversion is an opinion.
- Stop trying to make the two dashboards agree. Make both of them point at the same invoices.
Every business that runs paid advertising and a CRM eventually has this meeting. Google Ads says 84 conversions. The CRM says 51 leads. Sales says they spoke to about 30 people worth speaking to. Finance says four of them bought something.
Everyone assumes somebody’s tracking is broken. Usually nothing is broken. The systems are counting different things on purpose.
Four reasons the numbers cannot match
They count different events
Google Ads counts an action: a form submitted, a call over a threshold, a button clicked. Your CRM counts a record: a person who now exists in the database. One enquirer who submits a form and then rings is two conversions and one contact.
They use different windows
Google Ads credits a conversion back to the click, which may have been up to 30 or 90 days earlier depending on your settings. Your CRM records the lead on the day it arrived. In any month where spend changed, the two will disagree simply because of when things are counted.
They use different models
Google’s attribution model spreads credit across multiple clicks and reports fractions. Your CRM records one source, usually the last one, and usually as a whole number. Neither is wrong. They are answering different questions.
They de-duplicate differently
The same person on two devices is often two conversions and, if you are lucky, one CRM record. If you are not lucky it is two records and somebody merges them later.
The trap: picking a winner
The usual response is to decide one system is the truth. That fails whichever one you choose.
Trust Google Ads and you optimise towards volume, including the enquiries that were never worth having. Trust the CRM alone and you have no idea which marketing produced the records in it, so you cannot act on any of it.
The dashboards are not the problem. The absence of a shared reference is.
The number both can agree on
Revenue. An invoice is not a modelled event or an estimate. Either the money arrived or it did not.
So the useful architecture is not “make the dashboards match”. It is to make sure every enquiry keeps its source from first contact all the way to the invoice, and then to report on the invoices.
That needs three links in a chain:
- Every enquiry captured with its source, whether it arrived as a call, a form, a chat or a checkout.
- That source travelling with the person into whatever system your team works in, so it is not lost the moment somebody creates a record.
- Revenue matched back, from your accounts package or CRM, to the enquiry and therefore to the campaign.
The first link is where most businesses break, and it is the phone that breaks it. A form can carry hidden fields. A phone call arrives as a person talking, with nothing attached, unless something attached it.
This is the loop Clear Ring exists to close. Calls, forms, chats and events all captured with their source, then matched to quotes and invoices from Xero, QuickBooks or Sage so a campaign shows the money it produced. See what it connects to, or watch the loop close on real data.
What to do about the meeting
Agree what a lead is, once, in writing. Most of the argument is definitional. If marketing counts enquiries and sales counts qualified opportunities, you will disagree forever and both be right.
Stop comparing totals. Compare direction. If Google Ads conversions rose 20% and CRM records rose 18%, that is agreement. Chasing the last 2% is a waste of a morning.
Report on revenue by source monthly, not on conversions weekly. Revenue lags, which is inconvenient and also the point. Weekly conversion reporting is what makes people optimise towards noise.
Send outcomes back to the ad platforms. Once you know which enquiries were real, feed those back rather than all of them. The platforms then optimise towards the same definition your CRM uses, and the gap narrows on its own.
A realistic expectation
The numbers will still not match, and they should not. Different systems, different windows, different models.
What changes is that the disagreement stops mattering, because both are pointing at the same list of invoices. That is a much better meeting than the one about whose tracking is broken.
Common questions
Should we switch to last-click attribution to make things simpler?
It makes the numbers easier to explain and less accurate. Worth doing only if the reporting is not being acted on anyway.
Do we need a data warehouse for this?
Not for most businesses. You need the source to survive the journey from enquiry to invoice, which is a tracking and integration problem rather than a storage one.
What about offline sales that never touch the CRM?
Those need the invoice matched back manually or through your accounts package. It is worth doing for high-value work even if it cannot be automated.
How long before revenue reporting is meaningful?
One full sales cycle, and a second one to compare against. For most B2B that is a quarter.