GA4 lead tracking audit: tests before you trust the report
A lead tracking audit should connect a successful customer action to the event and business record it creates. Test failures, repeated submissions and consent choices as well as successful journeys. Write down what the report measures and where its coverage ends.
Define the action being counted
A business might measure a submitted enquiry, an appointment request, a phone link click or a paid order. Give each action a clear definition. A phone link click records an interaction with the website. Call completion and sales outcomes require their own evidence.
In GA4, an important event can be marked as a key event. The recommended generate_lead event records a request for information or an enquiry. Agree when the event should occur and how its result relates to the record your business receives.
For an enquiry form, the acceptance rule might be: create the lead event after the server successfully stores the request. A failed form submission should produce a visible error and no successful-lead event.
Run the same journey through different outcomes
Use labelled test enquiries and record the time, browser, page and expected outcome. Ask the person checking the business inbox or CRM to confirm the matching record. Keep test records identifiable so they are excluded from normal sales reporting.
| Scenario | Acceptance question |
|---|---|
| Successful submission | One accepted enquiry and the agreed event |
| Missing required field | Clear validation and no successful-lead event |
| Server error | Failure shown, with no false success |
| Repeated tap or page refresh | No accidental duplicate business record or inflated count |
| Consent declined | Tracking follows the configured choice and declared behaviour |
| Return visit | Source treatment follows the documented attribution rules |
Keep customer identity in the right place
Decide which system holds the customer's name, contact information and enquiry detail. Limit analytics parameters to the fields needed for measurement and permitted by the platform. Review URLs and form fields for accidental personal information.
Google Analytics User-ID uses identifiers supplied by the business to associate activity across sessions and devices. The identifier must not contain information a third party could use to determine a person's identity. An anonymous visit alone provides no confirmed customer name.
Record the limitations created by consent choices, blocked scripts, different devices and missing source information. A business needs those limits to interpret the report responsibly.
Reconcile leads using the same reporting rules
Compare the analytics report and business records for the same period and time zone. Identify test enquiries, spam, duplicates and requests received through other channels. Record the meaning of qualified lead and who assigns that status.
A useful review separates the website event count, accepted enquiries, qualified opportunities and completed sales. Differences should have an explanation, such as an excluded test or a customer contacting the business twice.
For an illustrative test, submit five labelled enquiries: three successful requests, one validation failure and one deliberate repeat. Agree the expected accepted-record count before testing. Inspect the events and stored requests together to confirm the implementation follows that rule.
Ask for an audit handover you can use
Request the event definitions, test sheet, configuration changes, access arrangements and known limitations. The report should identify the systems checked, the evidence collected and the defects still open. Attach the date of the checks so later changes are visible.
Agree who retests tracking when a form, website template, consent setting or CRM connection changes. Keep a short recurring operational check within the business's existing maintenance process.
DSDillon provides analytics and attribution work around the enquiries and business outcomes a company needs to measure. Bring the website, current reporting access and a description of where your enquiries are recorded.
Discuss GA4 measurement
Tell us about the work you are planning and the result you need.
Discuss GA4 measurement