Published: Last updated:
TL;DR
GA4 and the Universal Analytics transition
GA4 uses an event-based model to record website and app activity. Standard Universal Analytics properties stopped processing new data on 1 July 2023; the Universal Analytics 360 extension ended on 1 July 2024. See Google's migration dates.
Page views and some interactions can be collected automatically or through enhanced measurement. Other events need configuration and testing. A reported form interaction does not by itself prove that an enquiry was received.
Use landing pages and enquiries together
Compare organic landing pages with engagement and meaningful actions. Define useful key events, such as a confirmed form submission, and test that each event fires once at the correct point. A telephone-link click records intent to call, not a completed conversation.
Explorations can show recorded steps after arrival. Consent choices, blocked scripts and incomplete tracking limit the data. An ordinary Google referral does not identify whether a visitor clicked an AI answer or a conventional search result.
Search queries belong in Search Console
Use Search Console for the Google queries and search appearances it reports. GA4 describes website behaviour; it does not independently reveal all organic search keywords. Linking Search Console to GA4 provides related reports, with their own scope and data limits.
Internal site-search events can help identify information visitors need if the site has search and the events are configured correctly. Prioritise questions relevant to your services rather than treating every recorded phrase as a new article topic.
Measure AI search with the appropriate report
Search Console now documents a Generative AI performance report for Google Search. Review it alongside normal search performance rather than attributing every traffic change to AI. Also check the Search generative AI control to understand whether the property permits inclusion.
These reports concern Google's features. They do not establish visibility across every answer engine or trace each visitor through an AI response into a sale.
Connect reporting to business outcomes
Agree what counts as a qualified enquiry and reconcile website events with received enquiries and booked work. Keep click counts, enquiries and sales separate. GA4 attribution assigns credit using its available data and chosen model; it does not prove what caused a sale.
For example, a service page may show 20 organic form-submit events in GA4 while the inbox contains 17 delivered enquiries, including duplicates and spam. Investigate the event trigger and delivery record before reporting leads. Report qualified enquiries separately after reviewing relevance and contactability; these figures are illustrative, not site results.
For a repeatable review, list the reporting period, organic landing pages, Search Console query groups, confirmed enquiries, tracking changes and work delivered. The content and internal linking guide helps select the next page improvement.
Use a consistent comparison period, record site and tracking changes, and account for seasonality before judging performance. Agree a review schedule that fits the business and the volume of usable data.
For help with setup and reporting, contact me for a tailored quote or email info@phil-carr.co.uk.
Update — October 2026
Reviewed on 14 October 2026. Corrected migration dates, query-source advice and AI attribution claims; added an illustrative reconciliation example.
