Use case / Whole site
Whole-site visibility
Point tools tend to cover one form. Volance gives you a consistent read on every session across a shared template, without sitting in your request path.
The problem
When bot defense is bolted onto a single form, everything around it is a blind spot: scraped catalogue pages, quietly created accounts, and automated journeys that never touch the protected endpoint. A whole-site view means one integration, one score, and one policy instead of a patchwork.
How Volance helps
Place the reviewed collector in your site template once. Each session is scored on on-site behavioural and client signals, and your backend applies your own allow, flag, or block policy per route. Nothing is collected from a page until you deploy the collector there, and fingerprint signals stay off until you turn them on.
What you see
- Sessions by page and path, with the human / agent / bot split for each.
- The score, verdict, and the named signals behind every saved session.
- Plan usage across the site, so noisy routes are visible against your quota.
Volance scores a session on human-likeness and returns the evidence. It is not a CAPTCHA and does not prove a human is present; enforcement stays on your server.
Frequently asked
Does a whole-site integration add latency to my pages?
No. Scoring happens on your server after collection, and Volance is not in your request path. There is no proxy or CDN requirement.
Can I collect on some pages and not others?
Yes. Collection is per-page and explicit. Many teams start with the sensitive routes and widen the scope once the signal quality is clear.
MAKE THE NEXT REQUEST MAKE SENSE.
Start where
it matters.
One script on your site.
One API call from your server.
Every signal behind the verdict, in your own portal.