> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/use-cases-and-tutorials/activate-tags-once-per-page-session-or-user/understanding-sessions-and-users.md).

# Understanding Sessions and Users

Before diving into the nitty-gritty of JENTIS elements, it is essential to comprehend the distinction between sessions and users. In analytics terms, a session refers to a group of user interactions with your website that take place within a given time frame. A user, on the other hand, is an individual visiting your website. A user can have multiple sessions. A user will see one or many pages within a session and trigger multiple events.

When setting tags to fire once per page, session, or user, you effectively prevent redundant data, which can sometimes distort your analytics, AI training data, or conversion tracking. Mitigating redundant data is particularly useful in cases where you want to measure unique interactions, such as unique form submissions, downloads, or video views.

In this context, the scope (page, session, user, etc) describes the "uniqueness factor" ("how often" per "occurrence").


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jentis.com/use-cases-and-tutorials/activate-tags-once-per-page-session-or-user/understanding-sessions-and-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.