Advertorial disclosure: This article is for information only and contains affiliate links to Total Adblock. If you install through them, Zorvelix may earn a commission at no extra cost to you. It does not change what the extension does or what you pay.
Most people picture a website visit as a one-way exchange. You open a page, read what you need, and move on. In practice, some sites also observe how you move through the page itself: where your cursor travels, which parts you pause on, and how far you scroll before leaving.
This is the work of session recording scripts, sometimes called session replay tools. They are a common part of web analytics, and understanding them helps you make informed choices about your browsing. This article explains what these scripts capture, why sites use the data, why cookie settings and private browsing offer limited protection, and how the Total Adblock browser extension app filters them at the network level. The goal is a plain description of how the technology works, not a warning.
What a Session Recording Script Actually Captures
A session recording script is a piece of code a website loads to observe how a visitor interacts with a page. Unlike a basic analytics tag that logs which pages you open, a replay tool records the finer details of your on-page activity. In most cases, these scripts capture a combination of the following:
- Mouse movement: the path your cursor follows across the screen.
- Clicks and taps: where you click, including on elements that are not links or buttons.
- Scroll behavior: how far down a page you go and where you slow down or stop.
- Form interaction: which fields you focus on and, depending on configuration, what you enter before submitting.
The recorded activity is often reconstructed into a replay that resembles a video of the session. What this means in practice is that a site owner can review how visitors behaved on a page, either individually or grouped into aggregate patterns.
It is worth noting that responsible implementations mask sensitive fields such as passwords and payment details. The exact scope of what is captured depends on how each site configures the tool.
Why Sites Collect This Data
Session recording is generally used for analytics and design purposes. When a site owner can see where visitors hesitate, misclick, or abandon a form, they can adjust layouts, wording, and navigation to reduce friction. Viewed this way, the data supports usability improvements.
The same behavioral data can also inform advertising and personalization. Patterns in how you move through a page may indicate hesitation, comparison shopping, or strong interest. Combined with other signals, this contributes to a broader behavioral profile.
That profile can then shape what a site shows you: the timing of a prompt, the placement of an offer, or the ads selected for your session.
The same recording that helps a designer fix a confusing menu can also help an advertiser estimate your intent.
Whether the data serves usability, marketing, or both depends on the site and its partners.
Why Cookie Settings and Private Browsing Do Little Here
A common assumption is that clearing cookies or opening a private window stops this kind of observation. With session recording, those steps address only part of the picture.
The reason is technical. A replay script is loaded directly within the page's own code when the page opens. It does not depend on a stored cookie to begin observing your movements during that visit. Private or incognito mode mainly changes what your browser keeps in local history after you finish; it does not prevent a script from running while the page is open.
So while clearing cookies remains a reasonable habit, it tends to be a limited and temporary measure against this specific tool. To affect a script that runs on page load, the more consistent approach is to prevent it from loading in the first place.
Filtering Scripts at the Network Level With the Total Adblock Browser Extension App
Stopping a script after a page has finished assembling is difficult, because by then it has already run. A steadier method works earlier, at the point where your browser first requests the script from an outside server.
This is the approach the Total Adblock browser extension app takes. Rather than hiding elements after a page loads, it operates at the network level. When you open a page, it reviews the outgoing requests and stops those pointing to servers on its filter lists before the connection completes.
Because a filtered request never finishes, the associated recording script is not downloaded or executed. Your mouse movements, clicks, scrolling, and form input on that page are not passed to that tool, since the tool was never loaded. This differs from methods that only change how a page appears after everything has already arrived, since here the script is filtered before it can run.
A Measured Way to Think About Session Recording
The core point is straightforward. Session recording scripts observe on-page behavior, that behavior can feed into both usability work and behavioral profiling, and standard steps like clearing cookies address only a small part of it. Understanding this chain puts you in a better position to decide how much of it you take part in.
Network-level filtering gives you more say over which scripts your browser is allowed to load. It fits comfortably alongside familiar practices such as keeping your browser current, reviewing site permissions, and being selective about the sites you use most. Taken together, these steps let you browse with a clearer sense of what is running behind the page.