{
  "acceptance": "A useful fix record contains a reproducible action, the changed release, a successful action check and later observations for the same issue. Mark absent error data as inconclusive if the collector or relevant coverage is missing.",
  "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 recommends considering occurrences and affected visits when prioritizing issues."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Release and environment labels can be used as error filters."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The documented error collector excludes several classes, including pre-tracker and server-side errors."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Automatic sensitive-data redaction is best-effort and should not be treated as complete."
    }
  ],
  "description": "Prioritize browser issues using both repeated exceptions and the number of visits affected, with collection limits visible.",
  "diagram": [
    "Count issue occurrences",
    "Count affected visits",
    "Reproduce the failing action",
    "Compare the fixed release"
  ],
  "draft_hash": "78a70eb330ea5e604762228f2a5a797fa756bc38c68d9577e5ffdd509811ad43",
  "evidence": {
    "observed_at": "2026-11-04T01:00:45.302722+00:00",
    "period": {
      "end": "2026-11-04T01:00:45.302722+00:00",
      "start": "2026-11-04T01:00:45.302722+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": "comparison",
  "figure_notes": [
    "One visit can produce repeated exceptions.",
    "Use affected visits as a separate impact dimension.",
    "Verify which action fails with a controlled reproduction.",
    "Keep release, environment and collection coverage consistent."
  ],
  "figure_title": "JavaScript errors: compare occurrences with affected visits",
  "group": "Measurement and interpretation",
  "human_review_claim": false,
  "intent": "javascript-error-occurrences-vs-visits",
  "interpretation": "An exception can recur during the same visit. Umami separates issue occurrences from affected visits and supports release and environment filters. Use those distinct units when deciding what to fix first. An error dashboard is also a partial observation: the documented collector does not capture every class of failure, including errors before the tracker loads and server-side errors.",
  "keyword_volume": "Not obtained",
  "limits": "Browser exceptions are not server errors, complete traffic measurements or conversion-loss estimates. Automatic redaction should not replace review of information sent to analytics.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/javascript-error-occurrences-vs-visits/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "One JavaScript issue dominates the error count but its user impact is unclear.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T05:20:02.599721+00:00",
  "reader": "Site owners and analysts investigating one JavaScript issue dominates the error count but its user impact is unclear.",
  "related": [],
  "related_links": [],
  "research_document_ids": [
    "09af5f76b05bd7c6362ab7ee7e2776c5"
  ],
  "slug": "javascript-error-occurrences-vs-visits",
  "source_signature": "a66c30243269422aa75c9f6b07814afa2adc500e24bc1fe2fef04e863117a8ed",
  "sources": [
    {
      "hash": "c5898d68e59c396c0363598917c5fa7b0bba71c4dadb0cf12d975fcf361be30b",
      "locator": "Privacy # / b36; Usage # / b10; Usage # / b13; Use Cases # / b5",
      "observed_at": "2026-11-04T01:00:45.302722+00:00",
      "title": "Error tracking",
      "url": "https://docs.umami.is/docs/error-tracking"
    }
  ],
  "sources_required": [],
  "steps": [
    "Confirm that browser error collection is enabled for the intended environment and that consent and data-handling requirements are preserved.",
    "Record issue identity, occurrences, affected visits, release, environment and time range. Keep production and test evidence separate.",
    "Reproduce the affected action with a controlled account, saving only redacted error details. Check whether repeated occurrences come from one loop or from independent visits.",
    "After a fix, compare the same issue and scope across documented release windows. Check the action itself and retain collection gaps alongside the observed counts."
  ],
  "title": "JavaScript errors: compare occurrences with affected visits",
  "worked_example": "Hypothetical comparison: issue A occurs 50 times in one visit, while issue B occurs once in each of 12 visits. A has more recorded occurrences; B affects more recorded visits. Neither total alone measures lost conversions. The useful next question is which action fails and whether the issue repeats in a controlled reproduction."
}