> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/ab-tasty-prebuilt-widgets/scroll-rate-tracking-widget.md).

# Scroll Rate Tracking Widget

The Scroll Rate Tracking widget is part of the **Tracking** widget category. For more information on the widgets, please refer to [Widgets configuration in the visual editor](/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/widgets-configuration-in-the-visual-editor.md).

## Introduction <a href="#id-01gndd6kdsf4mg5ttbx5q24nwc" id="id-01gndd6kdsf4mg5ttbx5q24nwc"></a>

The Scroll Rate Tracking widget enables you to set one or more scroll goals on a web page.

Once the scroll threshold has been reached by a visitor, a goal is recorded in the report. If a user scrolls down, reaches a goal, scrolls back up and scrolls down again, the hit is not sent twice.

If they refresh the page and reach the scroll rate goal, a new hit is sent.

If you have a responsive website, it is probably more convenient to use the Element Visible Tracking widget instead of the Scroll Rate Tracking widget, which will consider a scroll rate the same way for visitors on desktop and on mobile.

<img src="/files/oG3SeOOF9aI2IsKTAy2X" alt="107.png" width="300">

Depending on how your website is designed and/or the device you use, you may see an element or not, without this being related to the scroll progression.

You can nevertheless use the Scroll Rate Tracking widget in two different campaigns, each one targeted on a per-visitor device basis, for a fair comparison.

## Configuration <a href="#id-01gndd6ke8twrkezadj7xjqfca" id="id-01gndd6ke8twrkezadj7xjqfca"></a>

<img src="/files/A4j4i3BS7AAceKFAoMwc" alt="" width="294">

To configure the widget:

1. Give it a name (for the Goals setup step and the Reporting),
2. Define a percentage of scroll (make sure to name it accordingly),
3. Save.

To use more than one goal, add them into the same tracking widget (by clicking on the "Add a setting" button) instead of adding another tracking widget. If you added one by mistake or if you would like to remove one inside a tracking widget, just click the cross to delete it.

<img src="/files/JheBATrQhPZBMmdGZhHs" alt="" width="279">

In order for your goal(s) to be displayed in your campaign reports, you need to add them as main or secondary goals. For more on the goal configuration step, refer to the [***metrics*** ](/reporting-and-performances/reporting/metrics.md)[***guide.***](https://support.abtasty.com/hc/en-us/articles/4711694271772)

To avoid creating conflicts within your campaign's reporting data, we recommend adding a single widget in which all your scroll goals will be defined.

To enable a fair comparison, event tracking widgets are applied to the original version and to the campaign variation(s).


---

# 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.abtasty.com/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/ab-tasty-prebuilt-widgets/scroll-rate-tracking-widget.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.
