# Working with Sessions

### Session Traits

There are 2 key traits that appear on each customer record pertaining to sessions:

* **Last Seen** - The date the customer was last tracked by the JavaScript Tag or Beacon API.
* **Sessions** - The total number of sessions logged for the customer over time.

{% hint style="info" %}
A 3rd trait, **First Seen**, is the date the customer was first added to CrowdPower, and will always be populated. It is not related to sessions.
{% endhint %}

### Session Timeout

All sessions are based on a **30-minute** window by default. The session count is incremented only if the customer is inactive for more than 30 minutes before coming back to your website. You can adjust this window in[ Settings](https://app.crowdpower.io/settings/options).

### Updating Sessions

Sessions are updated by default, but you can prevent this from happening by passing in the **update\_session** key on all Beacon API calls. Set the value to false to prevent logging new sessions. This could be useful if you're sending historical data in.

```javascript
{
    update_session: false
}
```

{% hint style="warning" %}
The update\_session key cannot be used with the Segment integration.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.crowdpower.io/resources/working-with-sessions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.