Find the shortest path to a useful answer.

Confirm the browser script loads on the affected route, the publishable key is correct, Content Security Policy permits the script and request, localhost behavior is intentional, and the test is not blocked by a browser extension.

Confirm the capture hook runs before browser JavaScript, covers the intended route, uses the full server secret rather than a masked preview, and does not exclude the test path.

Exclude framework internals, API routes, image optimization, favicons, robots files, sitemaps, and common static file extensions.

Distinguish a completed run with no observed brand presence from a queued, running, failed, or incomplete run. Confirm the prompt and provider scope.

Open the affected runs and compare the full answers, source URLs, provider, model, time, region, and language. One change may reflect normal provider variability.

Collection depends on what the customer enables:

visibility monitoring processes configured prompts, provider responses, mentions, citations, competitors, and run context;

Human Analytics processes enabled pageviews, sessions, referrers, campaign context, custom events, and goals;

AI Crawler Analytics processes request and response metadata used for classification and coverage.

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.

Estimate monitored brands, prompts, providers, competitors, telemetry volume, workspaces, and seats.

Use the sign-in and password-reset flows. Virent support will not ask for a password or server secret.

Contact the workspace owner or administrator for role and membership changes. Include the workspace name, but do not send private exports unless support specifically requests them through an approved channel.