> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/axis-and-hanwha-cameras-people-counting-configuration.md).

# Axis and Hanwha Cameras: People Counting Configuration

Learn how Solink people analytics can provide helpful data.

Solink can integrate with select models of **Axis** and **Hanwha** cameras to enable **People Counting** - a feature that collects data by tracking how many people entered and left a location. The data obtained from Solink's People Counting integration can be useful for:

* **Allocating staff**: Analyze traffic levels throughout the day to make educated staffing decisions for the future. Assign the correct number of employees per shift, decide when maintenance tasks (cleaning, service repairs) should take place, etc.
* **Understanding Location Performance**: Alongside POS data integrations, review traffic and conversion data to see how stores are performing. With Solink's video capabilities, check what each location is doing to drive the numbers - right or wrong - and adjust the strategies accordingly.
* **Monitoring Offices, Warehouses and Stores**: Review footage to see if there was human presence in any location where people counting is on.

Once People Counting data has been configured, you can configure and leverage the following Solink features to get further value:

* **Widgets**: Configure widgets that display People Counting data, such as total number of visitors in a given period of time, total visitors per location and conversion rates. See [**People Counting Widgets**](/docs/understand-your-business/widget-configuration/axis-and-hanwha-cameras-people-counting-widgets.md) for more information. The following image also provides an example of a People Counting widget - total visitors to a location per day:

![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-c1ba3d2f6c5c9cdef703c56202baee5f7f9f3cb2%2F1b8791188b723ec1.jpeg?alt=media)

* **Events**: Automatically generate an event when someone enters or leaves a location. Or, set up regular conversion rate reports to get an hourly or daily summary of People Counting data. See [**People Counting Events**](/docs/review-events-and-save-evidence/events/motion-events/axis-and-hanwha-cameras-people-counting-events.md) for more information.

### How to Enable People Counting

Please reach out to our [Support](/docs/get-started/introductory-guides/how-to-contact-our-team.md) team if you are interested in configuring People Counting integration with your cameras.

Please ensure you have [**Axis**](https://www.axis.com/en-ca/products/network-cameras) and/or [**Hanwha**](https://www.hanwhasecurity.com/products-page/security-cameras/) cameras as these camera brands are currently the only supported cameras for People Counting. Our team can help check for eligible models.\
​


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.solink.com/docs/install-connect-and-integrate/axis-and-hanwha-cameras-people-counting-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.