Measurement and interpretation · FIELD GUIDE
SPA pageviews: check automatic tracking before adding a manual hook
Trace route navigation to tracker calls when single-page app pageviews appear twice.
What the evidence can establish
Umami’s collection guide states that it automatically tracks SPA navigations. A separate manual pageview hook may therefore overlap with the automatic path, depending on the deployed integration. Diagnose the call origins before labeling all repeated requests as delivery retries. Two independent tracking calls and a retry of one call require different fixes.
Hypothetical trace: clicking from /overview to /details invokes an application route listener and an automatically installed tracker listener. Each sends a pageview. This is a candidate explanation to verify in the browser, not a claim about an observed website. Count the actual sends and their initiators before removing any code.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- Umami documents automatic tracking of SPA page navigations without additional configuration. Source 1
- c2 · Explanation and verification steps
- The collection guide recommends browser network inspection when investigating tracking behavior. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- Inventory the deployed tracker instances and application hooks that emit pageviews. Include tag-manager and framework integration paths.
- Perform one controlled client-side navigation with the browser network panel open. Record the destination, event type, send time and initiator for each request.
- Compare automatic tracking alone with the manual integration in a staging environment. Change one emitter at a time and preserve consent behavior.
- Retest initial load, internal navigation, back and forward navigation, and a hard refresh. Record the expected pageview for each operation in the application’s own measurement contract.
How to check the result
The trace should explain each emitted pageview and identify any duplicated instrumentation. After the fix, each tested operation should match its declared expectation without silently losing initial or subsequent navigation events.
Limits of this conclusion
The documentation does not prove that a particular duplicate was caused by a manual hook. Delivery retries, repeated user actions and multiple tracker installations remain separate hypotheses until the trace distinguishes them.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-03T22:45:09.225534+00:00
Location: Collect data / b10; Collect data / b7
Saved source fingerprint
1dcfaa966a316717efe849c8eb5e42c9ebf51c474f99a9c8c22219eeb3ecf156