Measurement guide 01
Write down what each customer action means before you set up tracking. A phone-link tap is not a call, and a form submission is not a qualified lead. Give each action a plain definition, a way to test it, and a person responsible for it. Then build your Google Analytics 4 (GA4) events and key events from that list.
← All measurement and analytics guidanceSee the action
Confirm delivery
Sort the inquiry
Confirm the outcome
Make the decision
Why this matters
A page view, a phone-link tap, a connected call, a form submission, a booking request, a qualified inquiry, and a completed job answer different questions. If they all get called a 'lead,' the report overstates demand and rewards whatever is easiest to trigger. If you only record final sales, you lose the steps that show where a form broke, a call went unanswered, or follow-up slipped.
GA4 measures activity as events. Some are collected automatically, some come from enhanced measurement, and you can add Google's recommended events (such as generate_lead) or your own custom events. You can mark the most important ones as key events. Before 2024, GA4 called these 'conversions,' and older help articles still do. None of these settings tells you whether an inquiry reached staff, fit your services, or became paid work. Your business defines that and checks it.
Responsible practices
Name the decision the numbers should support: fix a broken path, improve follow-up, compare channels, or adjust an offer. Then list the steps from a site visit to a delivered inquiry, a qualified lead, and a completed job. Keep the steps separate so an early signal can point to a problem without posing as a sale.
For each action, write what happened and what did not necessarily happen. Hypothetical example: 'Phone tap — someone tapped the call button on a phone. It does not mean the call connected.' Also note where the record lives, who owns it, and how duplicates, spam, tests, and cancellations are handled.
Check which events GA4 already collects automatically and through enhanced measurement before adding code. If a Google recommended event matches the action, use its name and settings. Create a custom event only when nothing fits. Enhanced measurement can send interactions without code, so confirm each trigger means what you think it means.
Google describes a key event as an action that is particularly important to your business. Marking one changes how reports highlight it; it does not make the underlying data more reliable. Choose key events from your action list, note why and when you marked them, and do not mark scrolls or form starts just to show a bigger number.
Use GA4 Realtime or DebugView to confirm the event name, trigger, and count. Then send a labeled test through the real phone, inbox, scheduler, or customer system. Check that it arrived, reached the right person, and was not duplicated. Both checks need to pass before the number goes in a report.
Do not send names, email addresses, phone numbers, or form text to Google Analytics; Google's policies prohibit personally identifiable information there. Keep customer details in a restricted system. In reports, state the action definition, date range, unresolved cases, and any setting changes. GA4 is not a complete customer or revenue record.
Customer-action list
List the decisions you want measurement to support and who makes each one.
For each contact path (call, form, directions, booking), list the steps from page visit to completed job.
Write a customer-action list: name, plain definition, exclusions, where the record lives, GA4 event name, key-event status, and owner.
Compare the list with the events actually live in your GA4 property, and fix any that do not match.
Test each path on a phone and a computer; confirm the event in DebugView and the message in the real inbox or phone.
Once a month, match a sample of GA4 events to your inbox, call log, and job records, counting tests, spam, and duplicates.
Log every event or key-event change with the date, the reason, and the person who approved it.
Avoid these failures
Collection, attribution, qualification, bookings, costs, and revenue depend on technical, customer, operational, and platform factors outside any provider's control. Results are not guaranteed.
Questions business owners ask
Measure the steps you need to run and improve the customer journey: contact intent on the site, successful call or form delivery, qualification, follow-up, and completed jobs where you can record them. Keep each step separate instead of reporting every interaction as a lead.
No. A key event is an event you have marked as important. A generate_lead event may mean an online form was submitted. Whether that inquiry was a good fit is a separate business decision, recorded in your own system.
Use automatic and enhanced-measurement events where they fit. For anything else, prefer a Google recommended event when it matches the action. Use a custom event only when nothing fits, and document it, because custom events do not fill most standard reports automatically.
No. Consent choices, ad blockers, device changes, offline conversations, and tracking gaps all leave holes. Compare analytics with your own call, form, and job records, label what is unknown, and avoid claiming that one channel caused a sale.
Primary guidance
Define it before you dashboard it