Plain-language explainer
GA4: a beginner’s guide
Google Analytics 4 measures visits and actions on your website and apps using events, so you can see which channels bring enquiries.
The work to plan together
A scope shaped around this requirement.
- Set up key events for enquiriesScope
- Link Search Console and Google AdsReview
- Respect cookie consent rulesCheck
The useful starting point
GA4 organises measurement around events. Define a small set of useful actions and verify their conditions before building a dashboard. A completed enquiry and a contact-button click are different events.
Set up and test an enquiry measurement plan
Start with the business action you want to count. On a lead website, an accepted form request is different from a button click, an automated acknowledgement or a sale. The following example is a testing plan, not live client data.
Prepare the property
Use a business-controlled GA4 property and the appropriate web data stream. Record the measurement ID and check the existing implementation before adding another tag.
Define the trigger
Ask the developer which event proves the enquiry was accepted. Connect generate_lead to that success condition, not to every press of the submit button.
Choose permitted parameters
Useful fields can describe the form or service category. Do not send names, email addresses, telephone numbers or message contents into analytics.
Test with one device
Use Tag Assistant or the supported preview/debug route. Open GA4 Admin → Data display → DebugView and inspect the event and its parameters.
Check the counting conditions
Perform success, validation-error and repeated-callback tests. Confirm that only the intended successful request produces the enquiry event.
Finish the reporting setup
Mark the agreed event as a key event using the current interface. Check the deployed consent behaviour, then distinguish source/channel reporting from the limited attribution in DebugView.
What to review
- Set up key events for enquiries
- Link Search Console and Google Ads
- Respect cookie consent rules
- Report on conversions, not just traffic
What to avoid or interpret carefully
Consent, blocking, attribution and missing data affect reports. Avoid sending private message contents or sensitive personal details into analytics events.
Practical detail
A practical review record
Illustrative checks for the task described above.
| Part of the work | Example output | How to review it |
|---|---|---|
| Successful accepted request | One generate_lead event | A test request exists in the enquiry destination. |
| Validation or server error | No completed-enquiry event | The visitor sees an error rather than a false success. |
| Repeated success callback | No second count for the same request | The implementation’s duplicate rule is documented. |
| WhatsApp/phone link | A separately named click event | The report does not label the click as a confirmed conversation or call. |
If nothing appears in DebugView, check the property, device selection, debug mode, tag firing and consent state. Do not bypass a denied consent choice just to make a test event appear. Analytics totals may differ from inbox totals because of consent, blockers and counting rules.
Reference guidance: Google Analytics event guidance; GA4 DebugView.
Build a report from meaningful events
GA4 reporting becomes useful when events reflect the actual journey. Decide what an accepted submission, booking or purchase means before adding tags. A dashboard cannot repair an event that counts failed actions as successes.
Define the event
Write the trigger and exclusions. A contact-button click and accepted form are different actions. Confirm that the website exposes a supported success state.
Test the paths
Check successful, invalid and repeated actions, along with the relevant consent states. Keep the test environment distinguishable so internal activity does not become a business result.
Protect data quality
Do not send names, email addresses or form messages as ordinary analytics parameters. Use approved non-sensitive context and document what is missing or modelled in the report.
How to interpret this guidance
Attribution is a reporting method, not perfect knowledge of a person’s decision. Use confirmed business records where required and keep definitions consistent across campaigns.
Why should analytics not contain the full enquiry message?
It can contain personal or sensitive information unnecessary for reporting. Route enquiry content through the approved lead-handling system. Analytics should use suitable event context without ordinary fields containing identifying details.
Why does my submission count look too high?
Check whether the trigger is a click, fires before sign-off, or runs from both a pageview and a success callback. Compare test request identifiers and the trigger record.
Should every contact click be a key event?
That is a reporting decision. Keep its name and meaning clear; a key-event label does not turn a click into a qualified lead.
Can Tangensys help with the next step?
Yes. Share your website, goal and the issue you are investigating. We can discuss the relevant service and provide a custom quote within 2 working days.
Related reading and services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days