GA4 · Conversion measurement
How to check whether GA4 tracks enquiries and purchases correctly
GA4 is not correctly configured merely because it shows visitors. Check whether important business actions are recorded at the right moment, with accurate data and without duplication. Clicking Submit is not the same as a successfully received enquiry.
First define what a result means for your business
For a service website, this may be a successfully received contact enquiry. For an online store, a confirmed order is important, while payment and returns require additional business tracking. Write down the event, exact trigger, required parameters and verification method.
Example measurement plan: generate_lead fires after the server confirms that the enquiry was accepted. contact_click describes a click on email or telephone but does not prove that a conversation happened. purchase describes a purchase with a unique transaction identifier and the correct currency. This distinction prevents large click counts from being mistaken for large numbers of clients.
Check the property, domain and consent
Make sure the website sends data to the expected GA4 property and web stream. The presence of Google Tag Manager alone does not confirm that the appropriate Google tag and events are configured. Conversely, a directly installed Google tag can work without GTM.
Test behaviour before and after the analytics choice separately. If a website uses a setup where analytics loads only after consent, missing events before consent are expected. Do not fix measurement by removing the user's existing choice.
Repeat the test in a clean session. Tracking-blocking extensions may explain why one person does not see events. Distinguish that from a fault affecting every visitor. Do not change settings for all users simply to make one test pass.
Realtime and DebugView serve different purposes
Use Realtime for a quick check that data is arriving. DebugView allows more detailed event inspection during testing when debug mode is enabled for the test device. Neither view alone confirms that every future report and business calculation is accurate.
Record the test time, page, action, expected event and observed result. For a problematic event, inspect its parameters and occurrence count. If page_view fires twice, check whether the same configuration exists both directly and through GTM, or whether multiple triggers are active.
After live verification, allow standard reports to process and check the same reporting period. Do not immediately conclude that a tag is broken because a new event is not yet visible in every standard report.
Test both form success and failure
Submit an invalid form: a successful-enquiry event should not fire. Next, check a failed server response or network interruption in a test environment. Clicking the button must not become a successful conversion in either case.
For success, verify three separate things: the application accepted the enquiry, the message reached its intended destination and the event appeared once. An analytics confirmation does not prove email delivery. Use a controlled address and clearly labelled test content.
Do not send message text, email addresses, phone numbers or names as GA4 parameters. Check page URLs too: contact details can end up in query parameters and be unintentionally passed to analytics.
For purchases, verify the complete journey
Follow the journey from product and cart to purchase confirmation. Check that purchase carries the appropriate transaction_id, value, currency and product data where required by the measurement plan. In particular, verify that refreshing or revisiting the confirmation page does not create another sale.
Compare several labelled test orders with store records. Revenue differences cannot be resolved merely by looking at total event counts. Inspect individual amounts, currencies, taxes, shipping, cancellations and the reporting period.
Once an event reliably describes an important business action, mark it as a key event where appropriate for the objective. Marking it does not repair an incorrect trigger or turn a click into an actual sale.
Checklist
- Correct property and web stream.
- Analytics choice and test debug mode checked.
- Enquiries recorded after confirmed success.
- Purchases have correct amounts and identifiers.
- No personal data or duplicate transmissions.
Why does GA4 show fewer purchases than the store?
Possible causes include analytics consent choices, tracking blockers, technical faults or differences in processing and reporting periods. Determine the cause through controlled tests and order comparisons, rather than merely comparing two totals.
Official documentation
Would you like your system reviewed?
Send your website address and a short description of the problem. We will agree the scope of a campaign, analytics or sales journey review.
Talk to Aleksandar