How to Use BotRefund to Detect Sessions With No Scrolling

Quick answer: enable the script, then review the engagement behavior signal

Install the BotRefund snippet on every landing page that receives paid traffic from Google or Meta. The script records pointer movement, scroll depth, click timing, and dozens of browser attributes for each visitor session. In the BotRefund dashboard open the Engagement behavior section; there you will see a row labeled Absence of clicks or scrolling. Sessions that never trigger a scroll event are marked with this signal. BotRefund does not treat a single missing scroll as proof of fraud; it weighs the signal alongside 109 other independent checks (browser consistency, network context, pointer tremor, input speed, etc.) and produces a session‑level verdict with a confidence score. (S2)

Step‑by‑step: from install to "no scrolling" insight

1. Add the BotRefund snippet to your site header or via your tag manager. The snippet loads asynchronously and starts capturing behavioral data on every pageview. (S2)
2. Verify data collection in the BotRefund dashboard under Live sessions. Confirm that scroll depth, mouse movement, and click timestamps are populating for real visitors. (S2)
3. Let traffic accumulate for at least a few hundred paid clicks. BotRefund needs a baseline of human behavior to calibrate its anomaly thresholds. (S2)
4. Open the Engagement behavior report. Filter by campaign, placement, or date range. The Absence of clicks or scrolling column shows a count and percentage of sessions with zero scroll events. (S2)
5. Drill into flagged sessions. Each session row expands to a timeline with scroll depth (flat line = no scroll), pointer path, click map, and the full 110‑signal evidence list. (S2)
6. Export a refund‑ready report if the cluster of no‑scroll sessions aligns with a specific placement, creative, or audience. The report includes click IDs (GCLID/FBCLID), timestamps, session recordings, and signal‑by‑signal reasoning formatted for Google and Meta review teams. (S2)

What "no scrolling" actually means in BotRefund's model

BotRefund treats absence of scrolling as an engagement behavior signal, not a standalone verdict. A session that loads a landing page, fires a conversion pixel, and never moves the scrollbar is statistically unusual for a human visitor. However, privacy tools, corporate proxies, single‑page apps, or accessibility settings can also produce a flat scroll trace. That is why BotRefund keeps the signal as evidence and cross‑checks it against:

• Browser fingerprint consistency (canvas, WebGL, font enumeration) – see the Scrollbar Width Leak check (S3).
• Network context (data‑center IP, VPN, residential proxy).
• Pointer behavior (linear movement, missing tremor, grid‑aligned paths).
• Speed behavior (sub‑millisecond input events).
• Session duration (too short, too long, or suspiciously uniform).

Only when multiple independent signals point to automation does the AI model assign a high‑confidence bot label. (S2)

Key facts from BotRefund's detection framework

Signal category	Specific check	What it captures	Role in verdict
Engagement behavior	Absence of clicks or scrolling	Sessions with zero scroll events and no click interactions	One of 110+ independent evidence signals; cross‑checked before verdict (S2)
Pointer behavior	Robotic linear mouse movements	Unnaturally straight pointer paths	Independent evidence
Motion behavior	Absence of humanlike mouse tremor	Missing micro‑jitter typical of human motor control	Independent evidence
Speed behavior	Superhuman input speed (<1 ms)	Interactions faster than physically possible	Independent evidence
Session behavior	Unnatural session durations	Visits too short, too long, or too uniform	Independent evidence
Evasion traps	Clean Context Iframe	Browser API inconsistencies that automation tools leak	Independent evidence (S5)
Evasion traps	Scrollbar Width Leak	Mismatch between reported and actual scrollbar width	Independent evidence (S3)

Where the signal appears in the workflow

After installation, the BotRefund dashboard surfaces three main views:

• Live sessions — real‑time stream with scroll‑depth sparklines.
• Engagement behavior summary — aggregate counts of Absence of clicks or scrolling by campaign, placement, device, and hour.
• Refund‑ready reports — PDF/CSV exports that package flagged sessions with click IDs, timestamps, session replays, and the full 110‑signal evidence table in the format Google and Meta reviewers expect.

You can also push the bot/non‑bot classification back to your analytics or CRM via webhook so that downstream reports (ROAS, CAC, lead quality) only count verified human sessions. (S2)

Common investigation patterns that pair with no‑scroll sessions

BotRefund's analysis shows that no‑scroll sessions often cluster alongside other red flags:

• Placement‑level spikes — a single Audience Network or Reels placement suddenly shows 40% no‑scroll sessions while Feed stays at 2%.
• Creative‑level differences — a new video creative attracts clicks but zero scroll depth, suggesting accidental or incentivized taps.
• Device anomalies — desktop user‑agents reporting mobile viewport sizes with no touch events and no scroll.
• CRM outcome mismatch — high reported lead count from a campaign, but sales logs show zero connected calls or booked demos from those leads.

When you see these patterns together, the no‑scroll signal gains weight and the refund‑ready report becomes stronger. (S2)

Limitations and when the signal does not apply

• Single‑page applications that load content via AJAX without a traditional scroll event may register as no‑scroll for genuine users. Configure virtual‑pageview tracking or whitelist known SPA routes.
• Accessibility tools (screen readers, keyboard‑only navigation) can produce atypical scroll traces. BotRefund's cross‑checking reduces false positives, but review edge cases manually.
• Very short landing pages (e.g., a single‑screen offer with the form above the fold) may legitimately have zero scroll for converting humans. Compare scroll depth against conversion events, not just sessions.
• BotRefund does not block traffic — it detects, reports, and supports refund claims. For real‑time blocking, pair it with a WAF or server‑side suppression rule fed by its webhook.

Terminology quick reference

• Engagement behavior signal — a behavioral check (scroll, click, dwell) that contributes evidence toward a bot/human classification.
• Refund‑ready report — a structured export containing click IDs, campaign metadata, session recordings, and signal‑by‑signal reasoning formatted for Google Ads or Meta ad‑quality review teams.
• Click ID (GCLID / FBCLID) — the unique parameter Google or Meta appends to the landing‑page URL; required to tie a session to a specific paid click for a refund claim.
• 99% confidence — BotRefund's reported accuracy when the full 110‑signal pattern supports a bot verdict; not a guarantee for any single signal in isolation. (S2)

FAQ

Does BotRefund automatically flag every session with no scrolling as a bot?

No. The absence of scrolling is one of 110+ independent signals. BotRefund's AI weighs the complete pattern — browser, network, device, pointer, speed, session, and evasion signals — before assigning a verdict. A single missing scroll on an otherwise normal session will not trigger a bot label. (S2)

Can I see no‑scroll data without paying for the enterprise tier?

The free bot audit includes a sample of flagged sessions and the engagement behavior summary. Full session recordings, unlimited history, and refund‑ready report exports require a paid plan. (S2)

How long does it take before no‑scroll sessions appear in the dashboard?

Data appears in Live sessions within minutes of the snippet loading. Aggregate engagement behavior summaries update hourly. For statistically meaningful clusters, wait until you have at least a few hundred paid clicks from the campaign you are auditing. (S2)

What click IDs does BotRefund capture for Meta and Google?

BotRefund captures FBCLID (Meta) and GCLID (Google) automatically when they are present in the landing‑page URL. These IDs are included in the refund‑ready report so the platform reviewers can match each flagged session to the exact paid click. (S2)

Can I use the no‑scroll signal to suppress conversion pixels in real time?

Yes. BotRefund offers a webhook that fires a bot/non‑bot classification for each session. You can feed that into your tag manager or server‑side GTM to prevent the Meta Pixel or Google Ads conversion tag from firing for sessions classified as bots. (S2)

What if my landing page is a single‑screen form with no scroll possible?

In that case, zero scroll is expected for humans. Filter the engagement behavior report by conversion event fired and compare scroll depth only for non‑converting sessions. BotRefund's cross‑checking (pointer tremor, input speed, browser consistency) still separates bots from humans on single‑screen pages. (S2)

How does BotRefund's evidence differ from Google's or Meta's automatic invalid‑traffic filters?

Platform filters operate at the server/impression level (IP reputation, click frequency, known data‑center ranges). BotRefund adds client‑side behavioral evidence — scroll, pointer, timing, browser API consistency — that the platforms cannot see after the click lands on your site. That extra layer is what makes the refund‑ready report persuasive in manual reviews. (S2)

Related BotRefund resources

For deeper insight into the signals discussed, see these BotRefund pages:

• Scrollbar Width Leak – one of the 110+ independent checks (S3).
• Clean Context Iframe – another evasion‑trap check (S5).
• Engagement behavior signals overview – explains how BotRefund combines scroll, click, and other behaviors into a verdict (S2).

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• How do chatbots handle refund or return requests?
• r/ConsumerAdvice on Reddit: I got scammed by ChatbotApp.ai / Chatbot ...
• How can I get a refund? | Chatbot App

Learn more

Visit the website for more information.