How to tell whether your GA4 conversion tracking works
If your contact button shows 80 conversions and the team received 12 enquiries, start by checking what the event measures. A button click, a submitted form and a lead accepted by your CRM are three different steps. Combining them makes it difficult to know which campaign generated business.
Give each meaningful action a definition
For every event, write down the customer action, what success looks like, the system that confirms it and who uses the result. A booking might count when the booking provider confirms it. A contact form might count after the server accepts a valid submission. Keep intent signals such as a button click separate so you can still analyse where visitors abandon the journey.
Test success, failure and repetition
- Submit one valid enquiry with an obvious test reference and verify that it arrives in the destination system.
- Try a submission with missing required information. It should produce a useful error for the user and zero success events.
- Refresh the confirmation page or go back and forward. Confirm that one successful action still generates one event.
- Test across mobile and desktop, any embedded form or separate booking domain, and the consent choices you support.
Reconcile totals over a sample period
Use a stable test period and compare the event definition against confirmed enquiries or orders. Document expected differences, including consent settings, attribution and reporting delays. An unexpected jump after a release is easier to investigate if you know which checks passed before it.
Document the trigger and test result alongside the event name so a new teammate can repeat the test. If you need help tracing the gap between campaigns and confirmed leads, see our GA4 and conversion tracking service.