Skip to main content

See how people and AI crawlers use your site.

Analytics for human traffic and AI crawler activity, with observed answer citations alongside. Coverage depends on what you install.

Visits, crawler requests, and answer evidence in one place.

Entry pages with the sessions they start and the goals those sessions reach.

What Analytics measures

Visitors12.4k

Human traffic

Pageviews, visitors, sessions, landing pages, referrers, campaigns, events, goals, and funnels from the browser script or SDK. Sessions are derived from observed events.

GPTBot/pricing200
ClaudeBot/docs200
PerplexityBot/old404

AI crawler activity

Crawler requests captured at the server, edge, middleware, or log layer, classified by crawler family, with the requested URL and response status. A classification is not proof of identity.

[1]yourbrand.com/guideYou
[2]runnersworld.com
[3]reddit.com/r/running

Observed answer citations

Pages cited in answers to your monitored Visibility prompts appear beside traffic and crawler activity. They are sampled API observations for your prompt and provider scope, not a count of every AI conversation.

/
/pricing
/compare
/compare/a

Pages

Open a page to see its human activity, crawler coverage, and answer references side by side. Each stays a separate measure, never one blended score.

→/guide→Goal

Referral and campaign context

Referrer and UTM context is preserved where the browser provides it, so AI-referred visits can be measured directly.

Coverage depends on what you install.

Each signal comes from a different collection path, so a site can have one without the others. A missing path means the data is unavailable, not that activity was zero.

At a glance04 items
  1. 01Human traffic needs the browser script or SDK on the pages you want to measure.
  2. 02Crawler activity needs a server, edge, middleware, or log integration, because most crawlers do not run browser JavaScript.
  3. 03Answer citations need Visibility monitoring and reflect the prompts, providers, and schedule you configure.
  4. 04Requests, citations, and visits are related signals. Virent does not add them together or treat one as proof of another.

Know what the website evidence can and cannot prove.

Follow a visit from the answer that mentioned you to the goal it reached, and keep unobservable influence labeled.

Someone can meet your brand in an AI answer and arrive days later through another channel. Unless the path is observable, Virent keeps that relationship inferred or unknown.

Illustrative example, not customer data. A path is reported as direct only while every step stays observable.

Add collection when the question needs it.

Install the browser script for pageviews, or the npm SDK for explicit events and goals. Add server or edge capture when you need crawler requests.

Never place the Virent server ingest secret in browser code. Localhost traffic is skipped by default.

Virent in the middle of a circuit board: the browser script and the npm SDK send pageviews, goals and events; Vercel, Cloudflare or your own server send crawler request logs.pageviewseventscrawler requestsBrowser scriptPageviews and goalsnpm SDKEvents from your codeVercelLog drain or middlewareCloudflareLogpush or a WorkerYour serverServer or edge captureVirent
Browser data and crawler logs arrive on separate paths and stay separate in reports: crawler requests are never counted as visits.

Workflow

  1. 01

    Establish the measurement plan

    Choose the pages, events, goals, and crawler routes that answer a real business question. Avoid collecting fields simply because they are available.

  2. 02

    Verify each data path

    Confirm a pageview is sent, the expected goal arrives, and a crawler request reaches the workspace from the server layer.

  3. 03

    Compare useful segments

    Review landing pages, channels, crawler families, and observable AI referrers with sample size and time range visible.

  4. 04

    Connect the evidence

    Compare visitor outcomes with crawler and citation changes without treating correlation as causation.

For teams

Questions

Frequently asked questions

Does Virent replace our existing web analytics?

Virent is built around AI discovery investigations. It measures core website activity, but the reason to use it is the connected view across human behavior, crawler activity, prompts, and citations. Whether it replaces another tool depends on your reporting requirements.

Can Virent attribute every AI-influenced visit?

No. A visit is attributed directly when the referral or campaign path is observable. Other relationships stay labeled as inferred or unknown.

Do answer citations show real AI search volume?

No. Citations come from API answers to the prompts you monitor, sampled on your schedule. They show what those answers referenced, not how often people ask AI products about a topic.

Do we need to install anything for visibility monitoring?

No. URL-only visibility monitoring needs no site instrumentation. Add the browser script or server capture when the question includes on-site behavior or crawler access.

What should we avoid sending?

Do not send passwords, payment-card data, health data, government identifiers, precise location, secrets, or other sensitive personal information unless Virent has expressly agreed in writing to process it.

Keep reading

Continue exploring

Connect discovery to the outcomes you can observe.

Measure visitors and crawlers with their context intact, beside the answer evidence your team already reviews.