Future InTech
Language · English

Measurement and interpretation · FIELD GUIDE

Distinct IDs and sessions: explain linked activity without merging counts

Use Umami identity links carefully and keep a combined visitor timeline separate from session totals.

By Future InTech · Published
Evidence cutoff: 2026-11-03T23:45:40.366155+00:00 · UTC

What the evidence can establish

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.

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.

Define the counting unit; Assign an opaque test ID; Inspect separate sessions; Compare the linked timeline
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.

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 supports Distinct IDs for linking activity across visits and devices. Source 1
c2 · Explanation and verification steps
Setting a Distinct ID links sessions but does not merge them. Source 1
c3 · Explanation and verification steps
A linked profile can combine activity from multiple sessions in one timeline. 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

  1. Document whether the report counts events, sessions or linked identifiers. Keep these fields separate in exports and dashboard labels.
  2. 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.
  3. Run two controlled sessions and inspect the linked timeline alongside the session view. Record when identification occurred relative to the first page view.
  4. 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.

How to check the result

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.

Limits of this conclusion

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.

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.

Distinct IDs

Obtained: 2026-11-03T23:45:40.366155+00:00
Location: Distinct IDs / b1; Session linking # / b20; Session linking # / b21

Saved source fingerprint02ab9a6927e6c119d00dd4c030aaaacd4eb28c6430bd81bdb72d314a55dfe149

Download this edition's evidence and action record (JSON)