# Start with the signal you need to measure.

> Install Virent human analytics and AI crawler tracking, configure visibility monitoring and verify each data path.

Canonical: https://stage.virent.app/docs
Last updated: 2026-07-29

Start with visibility, then add browser or crawler capture only for the signal you need.

- [Read the quickstart](/docs/get-started/quickstart)

- [Choose your framework](#installation)

## Start here

### From sign-up to your first answers

The eight onboarding steps, connecting Analytics, and how to verify each data path.

[Quickstart](/docs/get-started/quickstart)

### What each number means

Brands, prompts, sampled answers, mentions, citations, crawler requests and attribution, and the limits of each.

[How Virent measures](/docs/get-started/concepts)

### Hand the docs to your agent

Markdown for every page, llms.txt, and ready-made prompts for Claude Code, Codex, Cursor and others.

[Use with AI agents](/docs/get-started/ai-agents)

### Something isn't working

Fixes for missing data, changing answers, keys, limits and billing.

[Troubleshooting and FAQ](/docs/reference/troubleshooting)

## Choose an instrumentation mode

### URL-only visibility monitoring

Use it for: prompts, answers, mentions, observable position, citations, competitors, and share of voice.

Site change required: No.

[Start here: Visibility](/docs/visibility/overview)

### Human Analytics

Use it for: pageviews, sessions, referrers, campaigns, custom events, goals, and funnels.

Site change required: A site-wide browser script or SDK installation.

[Read next: Human Analytics](/docs/analytics/human-analytics)

### AI Crawler Analytics

Use it for: crawler classification, request volume, routes, response status, coverage, and crawl rules.

Site change required: A server-side, edge or log integration.

[Read next: AI Crawler Analytics](/docs/analytics/ai-crawlers)

### Content Agent

Use it for: turning observed gaps into researched, reviewed articles published through GitHub after human approval.

Site change required: GitHub access to your site's repository.

[Early access: Content Agent](/docs/content-agent/overview)

## Choose your framework

Each framework guide covers Human Analytics and AI Crawler Analytics where the framework supports them, and starts with a prompt for your coding agent.

## JavaScript and TypeScript

- [Next.js](/docs/installation/nextjs)
- [React](/docs/installation/react)
- [Vue](/docs/installation/vue)
- [Nuxt](/docs/installation/nuxt)
- [Astro](/docs/installation/astro)
- [SvelteKit](/docs/installation/sveltekit)
- [Express](/docs/installation/express)

## Server and CMS

- [Laravel](/docs/installation/laravel)
- [WordPress](/docs/installation/wordpress)

## Hosting integrations

No server code, or pages served from a CDN cache? Capture AI crawlers from your host's logs or an edge Worker instead. See [Hosting integrations](/docs/integrations/overview).

- [Vercel](/docs/integrations/vercel)
- [Cloudflare](/docs/integrations/cloudflare)
- [AWS CloudFront](/docs/integrations/aws-cloudfront)
- [Akamai](/docs/integrations/akamai)
- [Netlify](/docs/integrations/netlify)
- [Google Cloud](/docs/integrations/google-cloud)
- [Fastly](/docs/integrations/fastly)
- [Framer](/docs/integrations/framer)
- [Webflow](/docs/integrations/webflow)

## Framework not listed?

Use the platform pattern that matches your architecture:

- a global site template for the browser script;
- a server, edge, reverse-proxy, middleware, or plugin hook for crawler requests, or your host's logs (see [AI Crawler Analytics](/docs/analytics/ai-crawlers));
- environment variables for server secrets;
- route exclusions for APIs, static assets, images, robots files, and sitemaps.

Contact support before inventing a public SDK API or payload.

## Keys and data boundaries

### Publishable write key

Use the publishable key (`vha_pk_…`) in browser tracking. It identifies the site's public ingest configuration and only accepts events from the website's allowed origins.
### Server ingest secret

Use the server secret (`vha_sk_…`) only in server, edge, proxy, middleware, or protected backend code. Never hard-code it in committed source or expose it to the browser. See [Keys and secrets](/docs/workspace/keys).
### Ingest endpoint

Use Virent's default endpoint unless the implementation requires an approved custom or proxied endpoint, such as a [first-party relay](/docs/installation/first-party).
### Sensitive data

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

## Product guides

- [Analytics](/docs/analytics/overview)

- [Visibility](/docs/visibility/overview)

- [Prompts and answers](/docs/visibility/prompts)

- [Brands and competitors](/docs/visibility/brands-and-competitors)

- [Actions](/docs/actions)

- [Content Agent](/docs/content-agent/overview)

- [Team and roles](/docs/workspace/team-and-roles)

- [Plans and billing](/docs/workspace/plans-and-billing)

- [API and SDK Reference](/docs/api)

## More resources

- [Help Center](/help)

- [Security](/security)

- [Privacy Policy](/privacy)

- [Data Processing Addendum](/dpa)

## Need help choosing the right integration?

Describe your framework, hosting layer, and the signals you need to measure. Do not send passwords, API keys, server secrets, or sensitive customer data.

- [Contact Virent](/contact)