# Analytics

Track conversation volume, visitor feedback, and approximate customer locations for an agent.

**Analytics** summarizes customer-facing activity for the selected agent. Use the date-range control to review a specific launch, campaign, or operating period.

## Summary metrics

The top cards show conversation and message totals together with positive and negative feedback counts. Feedback appears only when a visitor rates an assistant response.

Use these totals as directional product signals. A conversation count does not represent a unique person, and the absence of feedback does not mean an answer was correct.

## Country and city tables

Country and city are approximate. When available, Orkata derives them locally from the request IP address at the start of a public conversation and stores the approximate location with that conversation. The tables show conversation counts and each location's share of located conversations.

Location can be missing or inaccurate because of VPNs, mobile networks, proxies, unavailable GeoIP data, or shared connections. Do not use approximate location for identity verification, eligibility, pricing, or decisions about a person.

## Investigate a change

Use Analytics to identify a period or segment worth reviewing, then open [Chat Logs](/docs/chatbot-management/chat-logs) to inspect the actual conversations and retrieved sources. Protect exported conversations because visitors may have included personal information.

## Privacy responsibilities

Tell visitors about chat logging, feedback, and approximate location processing when required for your use case. Avoid collecting information you do not need and provide a way to reach a person.