@v4/analytics

Overview

@v4/analytics is how the site measures. It is the only package that loads OneTrust (the cookie banner) and Google Tag Manager (ELB's container), and the only one that pushes the site's events to window.dataLayer. There is no GA4 or gtag.js code in the site: GA4, Nielsen and every other tag live in ELB's container, configured by Joe Dawber's team, and read what the site pushes.

A server-safe root holds the rules (settings, consent, the head scripts, the tracking plan's events, what a page and its markup declare); @v4/analytics/client holds the provider, the declarations and the hooks that send events. Built like @v4/wsc and @v4/ecal, and off until its variables are set — the shape every club integration shares is described in Club integrations.

In the head: OneTrust, then GTM

The root layout writes, in this order and before any other script:

1. OneTrust's banner script, loaded async (7 Nov 2026: synchronous, as OneTrust ships it, it held the first paint for about 0.77s, and it never made consent known before GTM — the stub loads the banner asynchronously itself; Consent Mode's default, set inline before GTM, is what holds the tags), with the environment's domain script id, and its OptanonWrapper callback.
2. The dataLayer, with Google Consent Mode v2's default: every storage type denied except security, waiting up to 500 ms for OneTrust's answer.
3. GTM's snippet for the environment's container.

They are plain server-rendered tags, so the browser runs them in document order. Each id is checked before it is written into the page (GTM-XXXXXXX; a UUID, -test for OneTrust's test script): one that fails is left out, with its scripts. The config refuses it at build first.

Consent gates every event

The tracking plan gives each event one OneTrust category — Strictly Necessary, Analytics, Marketing or Functional — and the site sends it only once the reader has accepted that category. OneTrust names its categories by group id; which id is which is ELB's set-up, so they are settings (features.consent.groups in club.config.ts), defaulting to OneTrust's own (C0001–C0004).

Waiting is what lets a reader who accepts on their first page still have that page counted. At most 50 events wait; a reload starts empty. Without OneTrust on the page nothing is ever sent — except to a tester where a preview is allowed (every local dev server, and Dev with NEXT_PUBLIC_WSC_TRACKING_PREVIEW=true): localStorage.setItem("wsc:tracking-consent", "granted") in the console grants everything. Where OneTrust is on the page the switch is ignored, from the first event: OneTrust decides, however long its script takes to report.

Each change of answer is also sent to Consent Mode as gtag('consent', 'update', …) (pushed as an arguments object, which is the only shape GTM reads): Analytics opens analytics_storage; Marketing the three ad types; Functional functionality and personalisation.

The WSC events follow the same answer for the Analytics category: apps/web's WscTrackingConsent hands it to @v4/wsc.

Page views

page_viewed is pushed once per page: on the first load and every change of address — a change of the query or hash alone is not a page view. GA4's own history page views are off in ELB's container, which turns this push into GA4's page_view.

The page says what it is. Every route renders <PageAnalytics page={…} /> with what only the route knows: the page type, its competition, the id of what it shows. The address alone cannot tell an article from a category under /news/…. The view is sent once the page has declared itself, which may be after its address changes (a page that streams in). A page that never declares is still counted, as page_type: "unknown", after 5 seconds — it shows up in GTM's preview instead of going missing.

A page that moves itself to a new address (a team's tabs, a games round, the next video of a playlist) is viewed again at the new address. A page Next kept mounted and shows again on Back is viewed again. The 404 is viewed at the address the reader asked for.

After the first page, a page view waits up to one second (TITLE_WAIT_MS) for the new page's own <title>: Next can stream a page's metadata in after the page itself, and without the wait page_title would carry the previous page's. A view still waiting when the reader moves on again goes at once, with the title it has, so the next title to land is read for the next page only.

An event's page_path is the address as last reported to the provider, not the browser's at the moment of sending: Next moves the address before the page it leaves cleans up, so an event sent on the way out (a pause on hide, the Game Centre's exit) still belongs to the page it leaves.

The values are provisional until ELB agrees the vocabulary.

What every event carries

The tracking plan's common properties that the browser knows, on every push: event_id, timestamp (when it happened, even if it waited), event_category, platform: "web", language, competition (the page's section slug, null for content linked to none), page_path, user_id (null before sign-in), and the consent snapshot as flat booleans (consent_state_analytics and the rest). GTM sets anonymous_id, session_id and device_category.

page_viewed adds page_type, page_title, page_location, page_referrer (the page before on the site, or the referring site on the first load), content_type, content_id, team_id, player_id and game_id. Every key is always present, null where the page has none: GTM's data model merges pushes, so a key left out would keep the previous page's value.

user_id

The reader's Cortex id (the session's userId, the ID token's sub). The header asks for the session once per load, and only when the signed-in hint cookie is there; a possibly signed-in reader's first page view waits for that answer, up to 1.5 seconds (USER_WAIT_MS), so it carries the id. The header hands the answer over with <AnalyticsUser />.

The site's events

Every event is one row of the catalogue, src/tracking-plan.ts: its name, its taxonomy category (event_category), the OneTrust category that gates it, and where its name was read. Only the plan's Legend tab could be read, so a name is marked by its source — v6-legend, jira, approach (the pre-V6 Approach page), wsc-list or assumed (the plan's convention applied; check it in GTM's preview). A rename is one line there, and track() takes only catalogue names and each event's own properties, so a typo is a type error.

Events are sent three ways, always on success, never on intent, and at most one per click (V6's legend):

The precedence for a followed link: a promo block always reports in_product_placement_clicked; otherwise a link to a partner reports the partner's event (eltv_cta_clicked, fantasy_deeplink_clicked, hosts in apps/web/src/lib/analytics.ts); otherwise its declaration. A Login control is a button, so it never reports navigation. A click that names no source_surface takes the page's type.

Not sent yet, and why: game_selected (not wired: game cards only began linking to the Game Centre when it landed), game_centre_shot_selected and game_centre_play_highlight_viewed (the Game Centre has no shot chart or highlights), game_prediction_submitted (the site has no predictor), Brightcove's video events (decision D4), a sponsor badge's click (the badges are not links). A video sponsor has no name in the platform's data, so its logo's file name stands in.

Still to come

Waiting on ELB: the container id per environment, legal's guidance on the consent categories (whether page_viewed may go as Strictly Necessary — it is gated by Analytics until then), the user_id field, and the tracking plan's event rows — every assumed name and property in the catalogue is checked against them.

Where it lives