Why conversion numbers often do not match
A senior team reviews marketing performance.
Google Ads reports 48 conversions.
Meta reports 36 conversions.
GA4 shows 57 form submissions.
The CRM shows 41 new leads.
Sales says only 19 were qualified.
None of these numbers are automatically wrong. They are just answering different questions.
| System | What it usually shows | What it does not always prove |
|---|---|---|
| Google Ads | Conversions attributed to Google activity | Whether the lead became qualified or sold |
| Meta Ads | Conversions linked to Meta views or clicks | Whether Meta created demand or assisted it |
| GA4 | Website events such as forms, calls or purchases | Whether the event became a real business outcome |
| CRM | Leads, opportunities and sales stages | Whether the original marketing source was captured correctly |
| Sales / finance | Qualified leads, closed sales or revenue | Which touchpoints influenced the journey |
This is why conversion reporting can become uncomfortable at senior level. The business is not only asking, “How many conversions did we get?” It is asking:
Which number should we trust when making budget decisions?
A platform conversion can be useful for optimisation. A business conversion is different. It needs to connect the enquiry, sale or revenue back to an agreed definition.
Without that source of truth, marketing performance may look precise while still being unclear.
The problem: each platform counts conversions differently
Marketing platforms are not designed to agree with each other. They are designed to measure performance from their own view of the customer journey.
That creates a common reporting issue: the same customer action can appear in several places, under several rules, with several different totals.
| Why numbers differ | Example | What this can do to reporting |
|---|---|---|
| Different attribution windows | Google counts a lead within 30 days of a click. Meta may count after a click or view within its own window. | Two platforms may claim influence over the same lead. |
| Different conversion definitions | One report counts a form submit. Another counts a phone click. The CRM counts only new enquiries. | The business compares numbers that are not measuring the same action. |
| View-through attribution | A person sees an ad, does not click, but later converts. | A platform may report a conversion even when the visible journey looks direct or organic elsewhere. |
| Duplicate event firing | A form event fires twice after one submission. | Conversion volume looks stronger than reality. |
| Missing deduplication | A lead submits twice, or the same enquiry appears from two tracking paths. | One person may become multiple reported conversions. |
| CRM source gaps | The lead enters the CRM, but campaign source, medium or keyword is missing. | Sales can see the lead, but marketing cannot confidently connect it to spend. |
| Offline sales delay | A lead converts today but becomes a sale weeks later. | Campaign reports look complete before the business outcome is known. |
This is not a small technical detail. It can change how performance is interpreted.
A campaign with 100 reported conversions may become:
| Reporting layer | Reported number |
|---|---|
| Platform-reported conversions | 100 |
| Website form submissions after removing duplicates | 82 |
| CRM leads created | 67 |
| Sales-qualified leads | 31 |
| Closed sales | 9 |
The issue is not that the first number is useless. It may still help optimise media delivery. But it should not be treated as the final business result.
This is where many marketing reports lose senior confidence. They show performance, but not always the chain from spend to qualified lead, sale or revenue.
Data quality is seen as critical by most leaders, yet confidence in current measurement remains much lower. The gap is not usually caused by a lack of reports. It is caused by unclear definitions, disconnected systems and weak governance around what counts as the real conversion.
Platform conversions vs business conversions
A conversion is not always the same thing as a business result.
A platform may count a conversion when it sees a tracked action after an ad click or view. That is useful for campaign optimisation. But senior decisions usually need a different layer: whether that action became a qualified lead, sale, booking or revenue.
| Conversion type | Example | Main use | Risk if used alone |
|---|---|---|---|
| Platform conversion | Google Ads or Meta reports a lead | Optimising campaigns inside the platform | May over-credit the platform or include assisted actions |
| Website conversion | GA4 records a form submit, call click or purchase event | Understanding website behaviour | May include duplicate, test or low-quality actions |
| CRM conversion | A lead is created, qualified or moved to opportunity | Measuring lead quality and sales progress | Source data may be missing or inconsistent |
| Sales conversion | A deal is closed, booking is confirmed or invoice is paid | Measuring business outcome | May not show which marketing activity influenced the sale |
| Revenue conversion | Actual revenue, customer value or repeat purchase | Budget and commercial decision-making | Often delayed and disconnected from campaign reporting |
This is why platform conversions and business conversions should not be treated as interchangeable.
A campaign can look strong in the ad platform and still produce low-quality leads. Another campaign may look modest in clicks or conversions, but produce better sales outcomes. Without a clear link between campaign activity and business results, the report may reward volume instead of value.
The goal is not to remove platform conversions. They are important. The goal is to stop using them as the final answer when the business question is really about leads, sales or revenue.
Why businesses need one source of truth
One source of truth does not mean one tool replaces every other tool.
It means the business agrees which system is used as the final reference point for conversion reporting, and which systems are used for supporting analysis.
For example:
| Business model | Practical source of truth | Why |
|---|---|---|
| Lead generation | CRM | It shows whether enquiries became qualified leads or sales opportunities |
| Ecommerce | Ecommerce platform / transaction data | It records actual purchases and revenue |
| Appointment-based business | Booking system or CRM | It confirms whether enquiries became real appointments |
| B2B or long sales cycle | CRM plus sales pipeline stages | It connects marketing activity to opportunity quality over time |
| Offline sales | CRM, sales system or finance data | It captures outcomes that ad platforms cannot fully see |
The source of truth should sit close to the real business outcome. For many businesses, that is not the ad platform.
It is the system where the lead, sale or revenue is actually confirmed.
This creates a clearer reporting hierarchy. Platform data can still guide campaign optimisation, but budget decisions should be based on qualified leads, sales or revenue from the agreed business system.
For example, Google Ads can help decide which keyword to adjust today. CRM or sales data should help decide whether that channel deserves more budget next month.
Without this agreement, every report can become a negotiation.
Google Ads may show one version of success. Meta may show another. GA4 may show a third. Sales may see something different again. The senior team is left comparing numbers that were never designed to match.
With one source of truth, the conversation changes.
Instead of asking:
“Why are the numbers different?”
The business can ask:
“What do the differences tell us?”
That is a stronger question. It allows platform data to support optimisation, while business data remains the reference
point for commercial decisions.
Example: one customer journey, multiple reported conversions
One customer journey can create several reported conversions.
A person may first click a Google ad, return later from organic search, see a Meta retargeting ad,
and then submit a form directly on the website.
In the report, this can look like several separate wins.
| Step | Customer action | What may be recorded |
|---|---|---|
| Monday | Clicks a Google Search ad | Google Ads records a click and may later claim the conversion |
| Tuesday | Visits again from organic search | GA4 records another session from organic |
| Wednesday | Sees a Meta retargeting ad | Meta may count a view-through or assisted conversion |
| Thursday | Submits a website form directly | GA4 records a form submit |
| Friday | Lead appears in CRM | CRM records one new lead |
| Two weeks later | Sales qualifies the lead | CRM records one qualified opportunity |
In platform reporting, this journey may appear as:
| System | Reported result |
|---|---|
| Google Ads | 1 conversion |
| Meta Ads | 1 conversion |
| GA4 | 1 form submission |
| CRM | 1 lead |
| Sales pipeline | 1 qualified opportunity |
This does not mean the business received five separate outcomes.
It may be one person, one enquiry and one qualified opportunity, reported through different systems.
This is why adding platform conversions together can be dangerous. Google Ads and Meta totals are useful inside their own platforms, but they are not always additive at business level.
A simple example:
| Report view | Number shown |
|---|---|
| Google Ads conversions | 38 |
| Meta Ads conversions | 27 |
| LinkedIn Ads conversions | 12 |
| Total if added together | 77 |
| CRM leads created | 49 |
| Sales-qualified leads | 18 |
The total platform number may be much higher than the actual number of leads because several platforms may be claiming influence over the same people.
The better question is not only:
Which platform reported the conversion?
The better question is:
Which conversions became real business outcomes, and what role did each channel play?
What should and should not be treated as the source of truth
The source of truth should not be chosen because a system has the biggest number, the cleanest dashboard or the most familiar interface.
It should be chosen based on two business rules:
| Rule | Question it answers |
|---|---|
| Conversion source of truth | Where do we confirm that a real lead, sale or revenue event happened? |
| Attribution source of truth | How do we decide which channel, campaign or touchpoint gets credit? |
Both rules matter.
A CRM may confirm that a sale happened. But unless the business also agrees how attribution works, the sale can still be interpreted in different ways.
For example:
| Journey | Possible attribution rule | Channel credited |
|---|---|---|
| User first clicks Google Ads, returns later direct and buys | First-touch attribution | Google Ads |
| User first finds the website through organic search, later clicks Meta and converts | Last-click attribution | Meta |
| User clicks Google Ads, then email, then submits a form | Last non-direct click | |
| User sees Meta, clicks Google Ads, later becomes a sale | Multi-touch / assisted view | Meta and Google both receive partial credit |
| User comes through Google Ads but sale is closed offline 3 weeks later | CRM-based attribution | Google Ads, if original source was captured correctly |
This is why “agreed” does not just mean everyone looks at the same CRM number.
It means the business agrees:
| Attribution decision | Why it matters |
|---|---|
| First touch, last touch or multi-touch? | Changes which channel appears to create value |
| How long is the attribution window? | A 7-day and 30-day window can produce different results |
| Should direct traffic get credit? | Direct is often a return visit, not the original source |
| How are view-through conversions treated? | Important for Meta/display, but can inflate results if not controlled |
| How are offline sales connected back? | Critical for long sales cycles and lead generation |
| What happens when source data is missing? | Prevents “unknown” or “direct” from hiding marketing impact |
A practical reporting setup gives each system a clear role.
- Ad platforms support campaign optimisation.
- GA4 helps explain website behaviour.
- GTM controls the quality of event collection.
- The CRM usually confirms lead quality and pipeline progress.
- Ecommerce, booking, finance or sales systems confirm transactions and revenue.
- Attribution logic then decides how credit is assigned to channels.
This avoids the common mistake of forcing every number to match. They do not need to match perfectly. They need to be understood correctly.
For example, if Meta shows 120 conversions and the CRM shows 76 leads, the next step should not be to ask which system is “wrong”. The better question is:
What exactly did Meta count, what exactly did the CRM accept, and what attribution rule are we using?
That question usually reveals the real issue: attribution window, duplicate events, lead rejection, missing source data, form errors, offline delay or sales qualification rules.
The source of truth is not just a reporting preference. It is a business rule.
The goal is not to reduce the amount of data. It is to make the hierarchy clear.
Platform data explains how marketing activity performed.
CRM, sales or revenue data confirms what happened.
Attribution rules explain which marketing activity gets credit.
Checklist: what to review before trusting conversion data
Before conversion numbers are used for budget decisions, the setup should be checked from two angles:
Is the conversion real?
Is it attributed correctly?
A useful review should test the full path from user action to final report, not only the dashboard.
| Check | What to confirm |
|---|---|
| Conversion definition | Everyone agrees what counts as a conversion: form submit, call, booking, lead, qualified lead, sale or revenue. |
| Tracking setup | GA4, GTM, pixels, ad platform conversions and CRM fields are set up properly. |
| Conversion testing | Key actions are tested after setup and after website changes, so events fire once and in the right place. |
| Duplicate events | One user action is not counted multiple times. |
| Attribution rule | First touch, last touch, last non-direct click or multi-touch logic is agreed. |
| UTM standards | Campaign source, medium and naming are consistent. |
| CRM source capture | Lead source and campaign data are passed into the CRM where possible. |
| Sales stage mapping | Leads, qualified leads, opportunities and sales are clearly defined. |
| Revenue connection | Sales or revenue data is connected where possible. |
A simple test is often the most useful one: submit a test enquiry, check that the correct event fires once, confirm the lead appears in the CRM with the right source, and make sure the report shows it where expected.
If the answer is unclear at any point, the report may still look complete, but the business should be careful using it for budget decisions.
The goal is not perfect tracking. Perfect tracking is rarely possible. The goal is to know which parts are reliable, which parts are directional, and which parts should not be used as final proof.
How clearer conversion data supports better decisions
Good conversion reporting should reduce debate, not create more of it.
When conversion definitions, attribution rules and source-of-truth logic are clear, senior teams can make better decisions faster. They can see whether a channel is creating real leads, whether those leads are qualified, and whether spend is contributing to sales or revenue.
This is where marketing data becomes more commercially useful.
It is not only about proving whether marketing “worked”. It helps the business decide whether to increase spend, move budget, fix tracking, improve lead quality, or review the journey between enquiry and sale.
A mature reporting setup should also show confidence behind the numbers.
Some data is strong enough for budget decisions: confirmed leads, sales or revenue with clear source data. Some data is useful for optimisation: platform conversions, website events and campaign trends. Some data should be treated carefully: incomplete source data, duplicated events or platform-reported numbers that have not been reconciled.
This does not make platform reports less valuable. It gives them the right role.
- Platform data helps optimise activity.
- CRM and sales data show what happened after the enquiry.
- Attribution logic explains how credit is assigned.
KNOP helps review this structure: tracking setup, conversion definitions, attribution logic and reporting flow, so businesses can see where their marketing data is reliable and where it needs to be cleaned up before decisions are made.
Better conversion clarity leads to better decisions
Conversion numbers do not need to match perfectly across every system.
Google Ads, Meta, GA4, CRM and sales reports are all looking at different parts of the same journey. The problem starts when every number is treated as final truth.
For senior teams, the real question is not:
“Why are the numbers different?”
The better question is:
“Which number should guide which decision?”
Platform conversions are useful for optimisation. Website conversions help explain behaviour. CRM and sales data show whether activity became something valuable. Attribution rules decide how credit should be assigned.
When those roles are clear, reporting becomes less noisy.
The business can stop adding platform totals together, stop debating which dashboard is right, and start understanding what marketing is actually contributing.
Clear conversion data does not make marketing simple. But it makes decisions more grounded.
For businesses spending money across multiple channels, one agreed source of truth is not a reporting luxury. It is the difference between seeing activity and understanding commercial impact.
