The flagship publication and the GA4 transition - analytical defence during investor diligence (2024–2025)

The situation

Following Google's deprecation of Universal Analytics in mid-2023 and the forced migration to GA4, the flagship publication's reported unique visitors appeared to drop sharply - from 6–8 million monthly in late 2023 to 3–4 million post-transition. The numbers didn't reflect a real traffic decline. They reflected a methodology change. But the discrepancy surfaced during a group investor diligence cycle, when the analyst preparing documentation for investors raised the question: the Looker Studio dashboard showed 9.4 million monthly visits for March; GA4's native interface showed 1.7 million. The answer needed to be technically correct, methodologically defensible, and clear enough that a finance-trained reviewer could absorb it.

The technical read

Universal Analytics counted every device as a separate visitor. GA4 introduced identity stitching across devices - a single reader using a phone, laptop, and tablet now consolidates into one user. For most websites this rebalancing is minor. For the flagship publication, where the readership is habitual and a significant portion read across multiple devices daily, the unique visitor figure took a disproportionate hit relative to retail or listing sites. The reported drop wasn't traffic loss. It was the platform's measurement model catching up to a publication's reader behaviour.

Cross-validation

I cross-checked against Realtime, the WordPress-native tracker that integrates at server level rather than relying on JavaScript tags or GA4 methodology. Realtime showed no traffic cliff during the period GA4 was reporting the drop. I also cross-checked against Google Ad Manager's available impressions - if the readership had genuinely declined by the magnitude GA4 was reporting, ad inventory would have dropped proportionally. It didn't. A third check: the vehicle-database platform, which derives roughly half its traffic from the flagship publication referrals, actually grew over the same period. A genuine drop on the flagship publication would have shown up there. It didn't.

The methodological decision

Rather than display the apparent decline, I rebuilt the flagship publication Looker Studio dashboard using GA4's Pageviews metric (which post-transition more closely tracked Realtime's visit measurement) relabelled as Visits, and GA4 Sessions (which more closely tracked unique visitor counts) relabelled as Visitors. The vehicle-database platform and the classifieds site kept the standard GA4 labels because their browsing patterns matched GA4's session model. The decision was documented, the reasoning was structured, and the dashboards remain consistent with the underlying business reality - ad impressions, server-level tracking, and cross-site referral traffic - rather than the platform's measurement artefacts.

The investor diligence response

When the group analyst raised the discrepancy, I provided the full technical and methodological explanation in writing, cross-referenced against the independent data sources, preempted the SimilarWeb comparison question (SimilarWeb's panel-data model produces unreliable estimates for niche regional publishers without direct integration), and closed on the auditability principle: "we want to make sure we are clear in everything we do, and in things like this, it is always auditable and defensible." The explanation was accepted. The numbers held.

What this shows

Analytical depth combined with the operational instinct to anticipate where a measurement methodology will mislead its readers, and the discipline to engineer the reporting layer around the underlying business reality rather than the platform's defaults. The defence held under scrutiny because the methodology was documented before the question was asked.