> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/visitor-management/analytics.md).

# Visitor analytics

Visitor analytics is the reporting surface that turns your visitor activity into visual views of site traffic and visitor trends. You reach it from the **dashboard**, which reads the same operational records Kenai keeps as people sign in and out.

## How it fits

Every visit Kenai handles is captured as a timestamped record in the **visitor log**, the operational history of who signed in at your site. Visitor analytics sits on top of that record and presents it visually, so you can see traffic and trends rather than reading the raw log line by line. The visitor log and these analytics are part of the same reporting surface; employee activity is kept separately in the employee log.

Reporting aggregates within an organisation. If you manage more than one site, you can view activity across those sites from a single dashboard. A partner managing several client organisations selects one organisation to scope into before reporting.

## Working with the data

The dashboard is the main way to work with visitor data:

* **Visual analytics** show site traffic and visitor trends.
* **Custom log views** let you filter the data and save a view for reuse, with no limit on how many you keep per user (for example, a reception view of today's expected arrivals).
* **Export** is available on demand as PDF or CSV.

{% hint style="info" %}
**Note:** **AI natural-language search** lets you build filters and views in plain English across the available dashboard data. It produces an auditable filter over your records, not an opaque result.
{% endhint %}

For programmatic access, the Kenai REST API gives read access to operational data and supports a scheduled or on-demand data extract. API keys are generated in the dashboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/visitor-management/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.