or an image),
* the element is hidden and is only displayed after a click (or any other user behavior).
In all of these cases, we collect a hit. Once an element has been made visible in the viewport, reading it and re-displaying it will not count it twice. However, if the visitor reloads the page and the element is visible again, 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.
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.
## Configuration
To configure the widget:
1. Select the element you want to track,
2. Give it a name (for the Goals setup step and the Reporting),
3. Save.
To use more than one goal, add more in the same tracking widget (by clicking "Add a setting") 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 on the red cross to delete it.
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 guide*.](/reporting-and-performances/reporting/metrics.md)
To enable a fair comparison, event tracking widgets are applied to the original version and to the campaign variation(s).
---
# 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.abtasty.com/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/ab-tasty-prebuilt-widgets/element-visible-tracking-widget.md?ask=
```
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.