Compare your metrics with anonymized peers
Stop analyzing your traffic in isolation. WysLeap aggregates weekly, anonymized, hashed site-level metrics from participating sites so you can see how your traffic and engagement compare.
- Site-level aggregates only
- No cookies
- GDPR-ready
Your site vs anonymized peers
This week
- Weekly sessions4,820 · peer median 3,900
- Avg. session duration1m 52s · peer median 2m 10s
- Engaged sessions58% · peer median 51%
Illustrative values. Peers are shown only as aggregates, never as individual sites.
The problem
A number without context is just a number
Is this number good?
Is it just us?
Analyzing in isolation
How it works
From weekly snapshot to peer benchmark
How your site-level metrics become anonymized benchmarks.
Your weekly metrics are summarized
Once a week, site-level metrics such as traffic volume and session duration are summarized into a snapshot. No visitor-level records are included.
The snapshot is anonymized and hashed
Your site identifier is hashed. No personal data, no visitor IDs, no cross-site tracking.
Aggregated across participating sites
Snapshots are combined into peer benchmarks. Other sites only ever see aggregates, never your individual metrics.
Compare your metrics with peers
See how your metrics compare in your dashboard. The investigator agent can also use the benchmarks as context when explaining changes.
What you get
Context for your numbers
Peer benchmarks in your dashboard
Benchmark-aware investigations
Your models stay yours
Privacy by design
We share aggregates, never visitors
Benchmark snapshots contain weekly site-level metrics only. No visitor IDs, no IP addresses, no personal data. Site identifiers are hashed, and other participants only see aggregated benchmarks.
- Site-level metrics only: weekly totals and averages
- Hashed site identifiers; benchmarks combine many sites
- Other sites never see your individual metrics
What shared data is not used for
- Training or improving other sites' WysAI intent models
- Bot detection on any site
- Recognizing or identifying visitors
- Pre-scoring visitors before they reach your site
Benchmarks are for comparison and investigation context only.
Example scenario
“Our sessions dropped. Is it just us?”
- 1
The change
A store's weekly sessions fall compared with the previous week.
- 2
The context
The investigator agent checks the peer benchmark and sees peers' traffic fell in the same week.
- 3
The takeaway
The drop looks market-wide rather than a broken page, so the team keeps its campaign running and checks again next week.
Example scenario: illustrative, not a customer or measured result.
FAQ
Frequently asked questions
What are WysLeap peer benchmarks?
What data is shared?
Does shared data make my intent model or bot detection smarter?
How often are benchmarks updated?
How does the investigator agent use benchmarks?
Put your numbers in context.
Compare your metrics with anonymized peer benchmarks that are hashed, aggregated and refreshed weekly. 90-day free trial, no credit card.