Go from sign-up to your first AI answers.
Last reviewed 2026-10-19
Onboarding takes you through eight short steps. Visibility starts on its own after the Prompts step; installing Analytics is optional and never blocks the dashboard.
Before you start#
- A brand to monitor: a company, a person or creator, a local business or anything else. A website is optional for Visibility and required for Analytics and Content Agent.
- A plan. Virent has no free plan or trial: you choose a plan before any AI work runs. See Plans and billing.
- For Analytics only: access to the website's code, hosting or CMS, or a developer who has it.
The eight onboarding steps#
Profile
Your name, the workspace name (which sets the workspace URL) and how you heard about Virent.
Plan
Choose a plan in the embedded checkout, in USD or BRL, billed monthly or annually. The page waits until the plan is active, then moves on.
Brand
Enter the website URL. Virent reads the homepage to prepare the brand profile and find adjacent brands. No website? Choose "I don't have a website", then give the brand name, what kind of brand it is and, optionally, its profiles.
Review
Check the profile Virent drafted (name, other names, what you do, audience) and correct anything wrong. Without a website you fill in the same profile yourself.
Competitors
Confirm or dismiss each suggested competitor, or add one by name or domain.
Prompts
Review the suggested prompts (the questions buyers ask AI assistants), edit or dismiss them, and confirm the ones to track. Confirming starts daily monitoring.
Install
Connect Human Analytics and AI Crawler Analytics, or skip this step and return later. Brands without a website have nothing to install.
Launch
Open the dashboard.
Connect Analytics#
Analytics has two independent collection paths. Install the one that answers your question, or both.
People on your site
A site-wide browser script with the publishable key (vha_pk_…). Pageviews, sessions, referrers, campaigns, events, goals and funnels.
AI crawlers on your site
Server, edge or log-based capture with the server secret (vha_sk_…). Crawler requests, pages, response status and crawl rules.
The fastest path is the dashboard: open Connect analytics in the Analytics header (or the Install step) and choose Open in Claude Code, Open in Codex or Copy for Cursor and other agents. The agent detects your framework. The prompt includes your publishable key and site ID; a copied prompt also includes the server secret if you used Rotate + reveal first, otherwise the agent asks you for it. Each framework guide has the same prompt without keys.
Verify each path#
Visibility#
Open Prompt Monitoring after the first daily run. Each prompt shows one answer per engine. Open an answer to see the full text, the brands it names and the sources it cites.
Human Analytics#
Load a page of your site (not localhost), then refresh the connection status. It moves from "Waiting for first event" to "Receiving events".
AI Crawler Analytics#
Run curl -A "GPTBot" https://your-domain.com/ and refresh the connection status. A controlled user agent tests the integration; it does not prove a real crawler visited.
Analytics in the dashboard#
A failed status check shows "Health unknown", never "Not installed". Check again before reinstalling anything.