From Built-In Analytics to GA4: Rebuilding the Measurement Foundation

What this upgrade enabled

• GA4 live tracking validated on a custom domain

• Portfolio measurement moved from built-in visibility to event-based infrastructure

• Foundation prepared for CTA, outbound click, and resume download tracking

Overview

The original portfolio measurement layer was built on Wix Analytics, which was useful for early traffic visibility and engagement monitoring. As the site matured, I needed stronger tracking control and a better foundation for more deliberate behavioural analysis.

The move to GA4 came from that shift: not from wanting a different dashboard, but from needing a measurement system that better matched the next stage of the portfolio.

The Limitation

What became limiting was not the presence of data, but the ceiling on what that data could support. Wix Analytics could show that traffic was happening and give a useful view of page level activity, but it became less effective once I wanted to move from general visibility to more intentional measurement.

As the portfolio matured, I was no longer only interested in whether users were visiting. I wanted a setup that could better support actions such as CTA clicks, outbound navigation, resume downloads, and more structured behavioural analysis.

The issue was not that the original setup failed. It was that it had become too narrow for the next stage of measurement.

Why GA4

GA4 made sense as the next system because it offered a measurement structure closer to how digital behaviour is handled in real analytics work. Where the earlier setup was mainly useful for visibility, GA4 provided a more industry standard environment built around event-based tracking and more deliberate measurement design.

That mattered because I wanted the portfolio to reflect not just an interest in analytics, but a stronger alignment with how tracking and behavioural analysis are actually approached in practice.

Objective

The goal was not simply to install GA4 on the site. It was to rebuild the portfolio’s measurement foundation so it could support stronger tracking control, more intentional event-based analysis, and better alignment with industry-standard analytics practice.

In practical terms, that meant moving beyond built-in visibility and setting up GA4 as the primary analytics layer for deeper behavioural measurement over time.

Implementation

The implementation focused on getting the portfolio into a clean, live measurement environment rather than simply adding GA4 code to the site. I connected a custom domain, created a dedicated GA4 property and web stream, configured the stream for the Wix environment, connected the Google Tag through Wix, and tested the installation using Google’s tag detection and GA4 realtime reporting.

The goal was to ensure that the migration was not only technically complete, but also validated against live site activity.

Validation

I treated validation as part of the migration, not as an afterthought.

To confirm the setup was working:

• Google’s detection tools confirmed GA4 was installed correctly on the live domain

• GA4 realtime reporting showed active users and page views

• Core events such as first_visit and session_start were firing correctly

This confirmed that the portfolio was no longer just configured for GA4, but actively sending behavioural data into the new measurement system.

What Changed After the Upgrade

After the migration, the portfolio had a more credible analytics setup for both current tracking and future experimentation. The site was no longer limited to platform native visibility.

It now had a GA4 measurement layer that could better support:

• structured event tracking

• more intentional analysis of user actions

• stronger alignment with real digital analytics workflows

In practical terms, the portfolio became better prepared to analyse behaviours such as CTA engagement, outbound clicks, resume downloads, and other actions that matter more than page views alone.

Key Takeaway

This project reinforced that good analytics work starts before analysis itself. It starts with the quality of the measurement environment behind the data.

A setup can be sufficient for one stage and still become the wrong setup for the next.

This migration showed me that part of thinking like an analyst is not only interpreting behaviour once data exists, but also recognising when the system collecting that data is no longer strong enough for the questions being asked.

Next Step

The migration is only valuable if it changes what the portfolio can measure next.

With GA4 in place, the next priority is to move beyond general traffic visibility and begin instrumenting the actions that matter more:

• CTA interaction

• outbound clicks

• resume downloads

• behavioural paths that show where interest is strengthening or dropping off

That next stage is where the case study moves from measurement upgrade into actual portfolio optimisation.