What changed
On August 21, Cloudflare began rolling out improved soft-navigation measurement in Web Analytics. Where Chrome’s Soft Navigation API is available, Cloudflare now records client-side navigations as `soft-navigation` and can capture Largest Contentful Paint for those pageviews. On browsers without that API, it falls back to Navigation API or History API detection under a new `routing-apis` navigation type. Cloudflare warns that the change can alter pageview volume reported in its dashboard and GraphQL API depending on front-end architecture and traffic mix.
Why it matters
For client-routed applications, analytics continuity is part of product and growth measurement. A tracking-model change can look like a traffic, engagement or performance change even when user behavior is stable. Teams using Cloudflare Web Analytics for dashboards, experiments, conversion denominators or Core Web Vitals now need to annotate the August 21 rollout, segment by navigation type and avoid comparing pre- and post-change numbers naively. The upside is better measurement of perceived performance inside SPAs, including LCP on supported soft navigations that was previously a blind spot.
SPA navigation is becoming a first-class analytics event
Traditional analytics often model a pageview around a full document navigation, while React, Angular, Vue, Svelte and other client-routed applications can change screens without unloading the page. Cloudflare now distinguishes those transitions explicitly rather than folding all detected navigation into the older `navigate` bucket.
Chrome can now provide LCP on soft navigations
The main capability comes from Chrome’s Soft Navigation API. When available, Cloudflare records a `soft-navigation` event and can measure Largest Contentful Paint for that transition. On Safari, Firefox and older Chromium browsers, Cloudflare falls back to Navigation API or History API detection under `routing-apis`; other Core Web Vitals are available there, but LCP is not.
The rollout creates a reporting discontinuity
Cloudflare explicitly says pageview volume may change in both the dashboard and GraphQL API. That means a jump or drop after the rollout should not automatically be interpreted as acquisition or engagement movement. The magnitude depends on how much of a site’s navigation is client-side and on its browser mix.
Historical comparisons need segmentation
Teams should annotate the rollout date, inspect the new navigationType values and separate measurement changes from business changes before acting on dashboards or experiments. If external BI systems ingest Cloudflare’s GraphQL data, derived metrics whose denominator uses pageviews should be checked as well.