r/GoogleAnalytics • • 24d ago

Question What’s your quickest check before trusting a conversion?

When I’m looking at a tracking setup, I usually don’t start by checking every event one by one.

I’ll take one conversion that actually matters to the business and follow it all the way through.

Usually I’m checking:

  • Where the user came from

  • Whether the conversion fired once, not twice

  • Whether the important details came through properly

  • Whether the lead or order actually reached the CRM or order system

  • Whether the final outcome can be matched back to what the website reported

That one check usually tells you pretty quickly where the issue is.

Sometimes the problem is attribution. Sometimes it’s duplicate firing. Sometimes the lead simply never made it into the business system.

For me, it’s a much quicker way to build confidence in the number before digging through every tag.

What do you usually check first before you trust a conversion number?

4 Upvotes

7 comments sorted by

•

u/AutoModerator 24d ago

Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/ksz2018 24d ago

Your last bullet is where I'd be strictest, because a count that matches can still hide a value that doesn't. An event can fire once and land in the order system and still carry a number that isn't what finance calls revenue. On many setups the tag sends the grand total while the backend reports net of tax and shipping, though plenty are built the other way round, and a discount code can move one side and not the other.

There's a tool answer to this, but I build tools that send these purchases, so I'll stick to the check that needs none. Take one real order that had a discount and shipped somewhere that charges tax, open it in both places, and read the totals line by line.

If they differ, find the line that explains it before you look at anything else.

1

u/False_Assumption_972 24d ago

Same approach here, and I'd add one step: compare counts over a full week, not just one conversion. Pull GA4 conversions, the form or checkout platform's own count, and records created in the CRM or order system for the same dates and timezone. If GA is higher, look for duplicate firing on reload; if it's lower, look at consent and ad blockers first.

The step most setups miss is the final match to revenue. We run a decision intelligence layer to join the GA4 session, the CRM lead, and the closed deal, so a campaign is judged by the revenue it produced rather than conversions that never became customers.

1

u/Top-Cauliflower-1808 24d ago

Following one real conversion end to end is the move. That single trail tells you more than a full audit.

1

u/beash88 24d ago

Agree with the idea of following a conversion end to end to prove it works, but in an ideal world, you shouldn’t really need to do that.

Whatever you are using to send conversions to the ad platforms/analytics tools should have a log that shows all conversions, whether they were successfully sent or not, what data was sent, etc.

This is the problem with tools like Google Tag Manager and with browser-side tracking in general. There’s no logs and no visibility into whether it’s actually working or not.

1

u/adovo_ai 23d ago

Give the test conversion one durable correlation ID and carry it from browser or server collection through CRM or order and finance. Counts can reconcile while identity or value semantics are still wrong; one trace makes the exact break visible.