{
  "acceptance": "The verification should show two separately identifiable test sessions and the link that connects them. Reports must describe the timeline as linked activity, without claiming that the underlying sessions were merged.",
  "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 supports Distinct IDs for linking activity across visits and devices."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Setting a Distinct ID links sessions but does not merge them."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A linked profile can combine activity from multiple sessions in one timeline."
    }
  ],
  "description": "Use Umami identity links carefully and keep a combined visitor timeline separate from session totals.",
  "diagram": [
    "Define the counting unit",
    "Assign an opaque test ID",
    "Inspect separate sessions",
    "Compare the linked timeline"
  ],
  "draft_hash": "4ce66d4300becfb4c91da120c75aa59baa8d16f86cb562f8610c3814aff72bc2",
  "evidence": {
    "observed_at": "2026-11-03T23:45:40.366155+00:00",
    "period": {
      "end": "2026-11-03T23:45:40.366155+00:00",
      "start": "2026-11-03T23:45:40.366155+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": [
    "Events, sessions and linked IDs are different units.",
    "Use a permitted test identifier without personal details.",
    "Identification does not merge browser sessions.",
    "A combined timeline is a view across linked sessions."
  ],
  "figure_title": "Distinct IDs and sessions: explain linked activity without merging counts",
  "group": "Measurement and interpretation",
  "human_review_claim": false,
  "intent": "distinct-ids-vs-session-counts",
  "interpretation": "Umami documents Distinct IDs as a way to associate activity across sessions. It also explicitly distinguishes linking sessions from merging them. A combined timeline is therefore a different view from a session count. Define the unit before treating the apparent discrepancy as duplicate data or a tracking failure.",
  "keyword_volume": "Not obtained",
  "limits": "An identifier association is not proof of a person’s real-world identity. This guide does not authorize collecting personal identifiers or bypassing an existing consent policy.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/distinct-ids-vs-session-counts/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A linked visitor profile contains activity from multiple sessions while session totals stay separate.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:05:03.826099+00:00",
  "reader": "Site owners and analysts investigating a linked visitor profile contains activity from multiple sessions while session totals stay separate.",
  "related": [],
  "related_links": [],
  "research_document_ids": [
    "3e8daadd78e5acd5f4c5137fb2d28c75"
  ],
  "slug": "distinct-ids-vs-session-counts",
  "source_signature": "4a73a9a822114069ce227dacf9bec6d49b7cb95f6f904303d6dc56092b52832e",
  "sources": [
    {
      "hash": "02ab9a6927e6c119d00dd4c030aaaacd4eb28c6430bd81bdb72d314a55dfe149",
      "locator": "Distinct IDs / b1; Session linking # / b20; Session linking # / b21",
      "observed_at": "2026-11-03T23:45:40.366155+00:00",
      "title": "Distinct IDs",
      "url": "https://docs.umami.is/docs/distinct-ids"
    }
  ],
  "sources_required": [],
  "steps": [
    "Document whether the report counts events, sessions or linked identifiers. Keep these fields separate in exports and dashboard labels.",
    "Review how identifiers are assigned and permitted for the intended analytics purpose. Use an opaque test identifier rather than an email address in the fixture.",
    "Run two controlled sessions and inspect the linked timeline alongside the session view. Record when identification occurred relative to the first page view.",
    "Check that identifiers are not accidentally shared across unrelated accounts. If the mapping is uncertain, mark the linked-user interpretation unresolved instead of altering historical counts."
  ],
  "title": "Distinct IDs and sessions: explain linked activity without merging counts",
  "worked_example": "Hypothetical controlled test: an authorized tester uses two browser profiles with the same opaque test identifier. The resulting linked timeline may show both sets of activity while each browser retains its separate session. That example demonstrates the intended distinction; it is not evidence that two unknown visitors are the same person."
}