July 1, 2023 marked the start of the end of new-data processing for standard Universal Analytics properties. Google had set out this milestone in its transition announcement. Analytics 360 properties had a separate extension. For website owners, the change highlighted a practical responsibility: verify that the reports used for decisions still reflect the actions taking place on the site.
Define a useful result before configuring a report
Google Analytics 4 uses an event-based measurement approach for websites and applications. This makes the definition of each event important. Opening a contact form, attempting to submit it and successfully sending an enquiry describe different stages of a customer journey.
Start with the questions the business needs answered. Which services attract interest? Where do people abandon a request? How many completed enquiries reach the team? Choose a small set of actions connected to those questions, name them consistently and record when each should be counted.
A tracking plan should be understandable to both the person maintaining the website and the person reading the reports. Include the relevant page, the expected trigger and the decision the information supports. This helps prevent a later redesign from silently changing what a familiar report means.
Check the journey behind the number
Test the important actions on the actual website, including French and English pages and mobile layouts. Confirm that a successful submission is recorded at the intended point and that refreshing or repeating a step does not create unintended duplicates. A functioning tag alone does not establish that the chosen business event is measured correctly.
Review the information sent with events, the people who can access reports and the behaviour associated with visitor privacy preferences. Do not send form contents or personally identifiable information, such as names, email addresses or phone numbers, in ordinary analytics event fields. Assign responsibility for checking measurement again when forms, payment flows or external integrations change.
Keep historical comparisons meaningful
Google’s migration explanation confirms that historical Universal Analytics data cannot be imported into GA4. When comparing retained reports across the transition, identify their source and period, and check how each metric was defined. A change in the measurement setup can affect a trend without proving an equivalent change in business activity.
Nuagerie’s website and application development services can help connect measurement requirements to the forms, journeys and integrations your business uses. The aim is information that supports a decision, with a clear explanation of what was measured.
To discuss a review, bring two or three business questions, the relevant pages and examples of the reports you currently use. Our team can help scope the implementation checks, identify who should validate the result and give your staff a clearer basis for interpreting reports and prioritizing website improvements.
