> For the complete documentation index, see [llms.txt](https://docs.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growlytics.in/core-concepts-1/sessions.md).

# Sessions

User Sessions are series of events that are performed within a single visit or interaction with your application. Growlytics SDKs automatically keeps track of session automatically for you. But if your are using our HTTP api for trackign event, you might need to pass session ids manually.

![Session Insights of a particular webiste](/files/-LjFciZdje2uz2mQZHHz)

## Tracking Sessions

Every website visit or mobile app launch is marked as a session. So all the events taken during this session will be marked against this session. Session automatically expires if user is not taking any action within 30 minutes of time. Events triggered after 30 minutes of interactions will be grouped under another session.

## Default session metadata

By default, Growlytics captures the following session metadata

| Metadata Name  | Metadata Description                                  |
| -------------- | ----------------------------------------------------- |
| Landing Page   | First page visited by user for given session.         |
| Exit Page      | Last page visited by user for given session           |
| Traffic Source | Trafic source domain name(google, quora etc)          |
| Timestamp      | Start time of session                                 |
| Duration       | Session Duration, difference of first and last event. |
| City           | City, extracted from IP address.                      |
| Region         | Region, extracted from IP address.                    |
| Country        | Country, extracted from IP address.                   |


---

# 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.growlytics.in/core-concepts-1/sessions.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.