WysLeap
Data quality

Make decisions on real data, not bot noise.

WysLeap filters bots, referral spam and internal traffic out of your clean view. Its Data Quality Score also counts duplicate pageviews and impossible sessions, so you know how far to trust your numbers. Switch between raw and clean in one click.

  • No cookies
  • GDPR-ready
  • On by default
wysleap · data quality
Last 30 days
65/ 100

Data Quality Score

Fair: 35% of pageviews were flagged

Bots, referral spam and internal traffic excluded from the clean view.

Sessions
6,500
Conversions
195
Conv. rate
3.0%

Top sources

  • google.com63%
  • newsletter29%
  • linkedin.com8%

Illustrative example, not measured results. Try the toggle.

The problem

Raw analytics is full of noise.

Industry reports suggest a significant share of most sites' traffic is non-human. Add spam referrers, your own team and duplicate events, and conversion rates, bounce rates and session depth can all be off, sometimes dramatically.

Bots & crawlers

Scrapers, AI agents, SEO crawlers and automation tools counted as visitors.

Referral spam

Fake referrers that pollute your source and attribution reports.

Your own team

Internal browsing and testing that inflates engagement and feature usage.

Invalid sessions

Duplicate events and sessions with impossible characteristics.

What gets checked

Six checks between your traffic and your dashboard

Each one targets a distinct source of noise. Together they keep junk traffic out of your clean view.

Bot & crawler filtering

Known bot and AI-crawler user agents, automation/headless detection and simple browser signals. Unusual patterns are surfaced for your review. How bot detection works →

Referral-spam exclusion

Visits from a curated list of about 70 known referral-spam domains are excluded from the clean view and kept in raw data.

Internal-visitor exclusion

Exclude your team by visitor ID in site settings instead of IP lists that break with VPNs. Or open your site once with ?wysleap_internal=1 to opt that browser out entirely.

Duplicate & impossible sessions

Duplicate pageviews (same visitor and page within 5 seconds) and visitors with more than 100 pageviews in a day are counted in your Data Quality Score.

Data Quality Score

One 0–100 score (the share of pageviews that passed every check) with a grade, so you know how far to trust your numbers.

Bot-spike alerts

Get notified in Slack or via webhook when bot traffic spikes, so problems don't go unnoticed.

How it works

Flagged, explained, never deleted.

  1. 01Checked at ingest

    Every pageview runs through bot and referral-spam checks as it arrives. Nothing to configure.

  2. 02Flagged with reasons

    Anything that fails is excluded from your clean metrics, not deleted, and the reason it was flagged is saved with it.

  3. 03Raw or clean, your call

    Toggle between raw and clean views at any time, and watch the Data Quality Score for how much was affected.

Pageview detail
/pricingExcluded from clean view
Referrer
seo-offers.example
Browser
Chrome · Linux
Stored
Raw data (not deleted)
Visible in
Raw view

Why it was flagged

known referral-spam domainno mouse or scroll activity

Illustrative example of a flagged pageview.

Manual vs automatic

Stop maintaining filters by hand

The same four chores, without the spreadsheets and filter lists.

Bot detection
GA4 drops known bots, but other bot traffic needs hand-built segments or tag rules.
Known-bot and browser-signal checks run automatically; unusual patterns surfaced for review.
Referral spam
Review referrer reports and block domains one by one.
Known spam domains are excluded out of the box, so there are no referrer filters to maintain.
Internal traffic
Maintain IP exclusion lists that break with VPNs and remote work.
Exclude team members by visitor ID, or opt a browser out with one URL.
Session validation
Write custom segments to exclude anomalies; edge cases get missed.
Duplicate pageviews and impossible sessions counted in your Data Quality Score.

Example scenarios

How dirty data distorts decisions

Illustrative examples, not real customers or measured results.

Marketing · Attribution

A “high-traffic” referrer that wasn’t

What they saw

A new referral source showed 500 sessions, and the team started shifting budget toward it.

What the clean view showed

480 came from known referral-spam domains and were excluded from the clean view. Only 20 sessions were real.

Known referral-spam domain list

SaaS · Internal traffic

The team was its own biggest user

What they saw

Daily testing on the live site made a new feature look far more popular than it was. About 30% of its usage was internal.

What the clean view showed

Adding the team’s visitor IDs to the internal-visitor exclusion took their activity out of the clean view, revealing real adoption.

Internal-visitor exclusion by visitor ID

E-commerce · Sale day

A real rush stays in the numbers

What they saw

A big sale-day traffic spike raised the worry that it was “just bots”.

What the clean view showed

Bot checks look at each visitor (known bot patterns and browser signals) rather than at traffic volume, so genuine shoppers stay in the clean view.

Per-visitor bot checks, not volume thresholds

Same site, two views

Raw

10,000 sessions · 200 conversions → 2.0% CVR

Clean

6,500 human sessions · 195 conversions → 3.0% CVR

Illustrative example, not measured results.

Quick self-check

How clean is your data?

Tick every symptom you've noticed in your analytics to get a rough risk level.

Your risk level

0 of 6 checked

No obvious warning signs

Your data may be clean. The Data Quality Score will confirm it once WysLeap is installed.

  • Flagged data is never deleted. Switch to the raw view any time.
  • Good bots (search and AI crawlers) are never blocked from your site; they're reported separately.

FAQ

Frequently asked questions

Everything you need to know about data quality filtering.

What if I want to see bot traffic for analysis?
Filtered data is never deleted. It stays in your raw data and is always accessible. You can view bot traffic in its own section and toggle between raw and clean data views directly in your dashboard.
Can I exclude my own team's visits?
Yes. Internal visitors can be excluded by visitor ID in your site settings, so your own browsing doesn't inflate the numbers. Team members can also open your site once with ?wysleap_internal=1 to stop tracking in that browser (undo with ?wysleap_internal=0).
What happens to my historical data?
Nothing is deleted. Pageviews are checked as they arrive; flagged ones stay in your raw data together with the reasons they were flagged, and you can switch between raw and clean views at any time.
How do I know the filtering is accurate?
Every flagged pageview stores the reasons it was flagged, so you can see exactly why it was excluded. You can also compare the raw and clean views side by side, and the Data Quality Score shows how much of your traffic was affected.
Does this affect my Google Analytics data?
No. WysLeap is completely separate from Google Analytics. Your GA4 data remains untouched, and you can use WysLeap as a clean, parallel analytics source alongside GA4.
How long does it take to set up?
You add a single script tag to your site and filtering starts immediately. Data quality scoring and filtering are on by default, so there's nothing to configure to get started. Excluding your own team by visitor ID in site settings takes a minute.

Still have questions? Talk to our team

Get clean analytics data today.

Bots and referral spam are kept out of your clean view automatically. See your Data Quality Score from day one.

90-day free trial · Pro $30/month