{
  "acceptance": "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.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Umami documents automatic tracking of SPA page navigations without additional configuration."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The collection guide recommends browser network inspection when investigating tracking behavior."
    }
  ],
  "description": "Trace route navigation to tracker calls when single-page app pageviews appear twice.",
  "diagram": [
    "Inventory pageview emitters",
    "Trace one route transition",
    "Disable only the overlap",
    "Retest navigation cases"
  ],
  "draft_hash": "cde356727e1d988a63e73e2416485edc0c193a39fc15ffe90b9edb67fdc59fa6",
  "evidence": {
    "observed_at": "2026-11-03T22:45:09.225534+00:00",
    "period": {
      "end": "2026-11-03T22:45:09.225534+00:00",
      "start": "2026-11-03T22:45:09.225534+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Include framework hooks, tracker instances and tag managers.",
    "Record the initiator of each emitted request.",
    "Test one change at a time in staging.",
    "Check initial load, route changes, back/forward and refresh."
  ],
  "figure_title": "SPA pageviews: check automatic tracking before adding a manual hook",
  "group": "Measurement and interpretation",
  "human_review_claim": false,
  "intent": "spa-pageview-double-instrumentation",
  "interpretation": "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.",
  "keyword_volume": "Not obtained",
  "limits": "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.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/spa-pageview-double-instrumentation/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "One route change appears to produce two pageview sends in a single-page application.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T11:50:02.661080+00:00",
  "reader": "Site owners and analysts investigating one route change appears to produce two pageview sends in a single-page application.",
  "related": [
    "analytics-event-retry-deduplication",
    "browser-pageviews-vs-log-requests"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/analytics-event-retry-deduplication/",
      "title": "Prevent delivery retries from inflating outcomes"
    },
    {
      "path": "/ai-analytics/guides/browser-pageviews-vs-log-requests/",
      "title": "Reconcile browser pageviews with server requests"
    }
  ],
  "research_document_ids": [
    "8677b1bc823773140f79f62fb3fa0ec2"
  ],
  "slug": "spa-pageview-double-instrumentation",
  "source_signature": "a9d3997102d038e8abdaedc0870404306c729659c10a9d143b38365d960e8cbc",
  "sources": [
    {
      "hash": "1dcfaa966a316717efe849c8eb5e42c9ebf51c474f99a9c8c22219eeb3ecf156",
      "locator": "Collect data / b10; Collect data / b7",
      "observed_at": "2026-11-03T22:45:09.225534+00:00",
      "title": "Collect data",
      "url": "https://docs.umami.is/docs/collect-data"
    }
  ],
  "sources_required": [],
  "steps": [
    "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."
  ],
  "title": "SPA pageviews: check automatic tracking before adding a manual hook",
  "worked_example": "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."
}