> For the complete documentation index, see [llms.txt](https://docs.humblytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humblytics.com/split-testing-overview/creating-a-b-page-variants-for-split-testing/engagement-goals/increase-session-time.md).

# Increase Session Time

The **Increase Session Time** goal measures how long visitors stay and engage with your page or website content.

\
It’s designed to help you test layout, content, or interactive elements that encourage users to explore more, scroll deeper, and spend longer periods interacting with your site.

This goal is especially useful for **blogs, landing pages, or content-driven websites** where engagement duration is a key performance indicator.

Choose this goal when your objective is to **increase visitor engagement** and reduce bounce rates.\
Ideal for:

* Content-heavy or educational pages
* Landing pages or product demos
* Video or multimedia sections
* Interactive tools or dynamic content blocks
* Long-form blog posts or guides

> A great choice when optimizing user experience and content engagement before conversion goals like form submissions or purchases.

#### What It Tracks

Once activated, Humblytics automatically tracks:

* **Average session duration per visitor**
* **Engagement depth** — time spent actively scrolling, clicking, or viewing content
* Comparison of **average session time** between Control (A) and Variant (B)

> Works automatically — no manual setup or tagging needed.\
> Humblytics measures real user activity (not idle time) to ensure accurate engagement tracking.

#### How It Works

1. Visitors are randomly assigned to **Control (A)** or **Variant (B)**.
2. Humblytics monitors **how long users stay active** on each version of the page.
3. It calculates **average session time** per variant.
4. Real-time reports show which version leads to longer engagement sessions.

#### Common Test Ideas

* Test **content length** or reading experience (short vs. detailed).
* Experiment with **video placement** or autoplay vs. click-to-play.
* Try **interactive features** like accordions, carousels, or quizzes.
* Adjust **page structure** (single column vs. multi-section).
* Compare different **visual or media layouts** to maintain interest.

#### Steps to Set Up

1. Click the **Split Testing** menu in your Humblytics dashboard.
2. Click **Start Creating Experiment**.
3. Under **Select Testing Goal**, choose **Increase Session Time**.
4. Choose your **Experiment** and **Test Type**.
5. Add URLs for **Control (A)** and **Variant (B)**.
6. Configure **Visitor Assignment** (allow or prevent overlap).
7. Apply **Restrictions** (Geo or Audience filters, if needed).
8. Launch your test and monitor session time performance in real time.

By running this experiment, you’ll learn which version keeps users engaged longer, resulting in:

* **Higher average session durations**
* **Deeper content interaction**
* **Improved user retention and engagement signals**


---

# 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.humblytics.com/split-testing-overview/creating-a-b-page-variants-for-split-testing/engagement-goals/increase-session-time.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.