> 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/integration/browser/reading-session-identifer.md).

# Reading Session Identifer

If you are planning to add events from your backend application and if you want to associate that event with the Growlytics Session, this article will guide you on how you can achieve that.

## Passing Session Identifier to your server

The Session identifier is nothing but the device id of the customer that Growlytics maintains. You can use `Growlytics.getDeviceId()` to read the device id.

```javascript
let deviceId = Growlytics.getDeviceId();
```

{% hint style="warning" %}
Device Id is always associated with a single customer and its a permanent for the given browser/device. If in the same browser, if the user logs out and logs in as another user, then the device id will remain the same but it will be pointing to a newer user.
{% endhint %}

You can pass the device id received to your backend server and use it while adding an event to Growlytics from your backend.


---

# 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/integration/browser/reading-session-identifer.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.