The recent discussions about GA4 conversions not matching backend numbers made me think about a related issue that feels easy to miss.
Sometimes the problem is a broken tag or a duplicated event.
But sometimes the harder problem is that GA4, Shopify, CRM, and backend revenue all use the word “conversion,” while meaning different business things.
A GA4 purchase event may be useful for traffic analysis, but it may not match the final paid order in Shopify after refunds, cancellations, taxes, discounts, or payment issues.
A GA4 lead event may look fine in a report, but the CRM may show that only part of those leads became qualified, booked, or closed.
So the question is not just whether GA4 is “right” or “wrong.”
The question is what each conversion is supposed to mean, and whether that definition still matches the number being used in reporting.
Before trusting a GA4 conversion in a client report, the checks that seem useful are:
What event GA4 is actually counting.
Whether it matches Shopify, CRM, or backend revenue.
Whether known issues like refunds, duplicates, failed payments, or test events are being handled.
A simple classification also helps:
- safe for reporting
- useful for trend analysis
- needs a warning
The harder part may be maintaining the conversion definition itself over time. Tags change, checkout flows change, CRM fields change, and people forget why a certain event was counted in the first place.
I keep coming back to the idea that this may need more than a one-off note. When AI or automation starts helping with analytics reports, unclear conversion definitions can turn into wrong conclusions faster.
What may be more useful is a lightweight conversion reference that stays with the GA4 property over time: what each conversion actually means, and who is responsible for keeping it updated.
That way, the next report, or the next person looking at the property, does not have to restart the same argument about which number is safe to trust.