> 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/review-events-and-save-evidence/events/motion-events/axis-and-hanwha-cameras-people-counting-events.md).

# Axis and Hanwha Cameras: People Counting Events

Generate an event when people leave or enter a location.

Using data from your Axis and Hanwha cameras, [People Counting](/docs/install-connect-and-integrate/axis-and-hanwha-cameras-people-counting-configuration.md) events can help you track whenever an individual enters or exits or location, as well as other important transaction information throughout the day.

Reach out to our Support or Customer Enablement teams to configure People Counting events (see [How to Contact Our Team](/docs/get-started/introductory-guides/how-to-contact-our-team.md) for contact information).

### Entry and Exit Events

With a People Counting integration from your Axis and Hanwha cameras, each instance of an individual entering and exiting a location creates an event.

Entry events include helpful information to keep track of the following information:

* **Current Occupancy**: The total number of occupants in the location at the time of the event creation.
* **Total Entries**: The total number of individual entries in the location during the given day.

Exit events also include **Current Occupancy** information at the time of the event creation.

An example of an **Entry** and **Exit** event are shown in the images below:

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

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

### Conversion Rate Events

There are two types of Conversion Rate events, which are created daily as a bookmark event:

**Hourly Summary Report**: An event is generated for each hour throughout the day. However, an event is not generated for a given hour if no transactions or people are detected in that hour. Hourly Summary Report events displays the following information:

* **Number of People**: Total number of exit events during the hour.
* **Number of Transactions**: Total number of transactions during the hour.
* **Total Sales**: Total dollar amount of sales during the hour.
* **Average Sales**: Average is calculated by (Total Sales) / (Number of Transactions).
* **Average Revenue/person**: Average is calculated by (Total Sales) / (Number of People).
* **Conversion Rate**: Calculated by \[(Number of Transactions)/(Number of People)]\* 100.

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

**Daily Summary Report**: This event is created once per day. The event displays the following information:

* **Number of People**: Total number of exit events during the day.
* **Number of Transactions**: Total number of transactions during the day.
* **Total Sales**: Total dollar amount of sales during the day.
* **Average Sales**: Average is calculated by (Total Sales) / (Number of Transactions).
* **Average Revenue/person**: Average is calculated by (Total Sales) / (Number of People).
* **Conversion Rate**: Calculated by \[(Number of Transactions)/(Number of People)]\* 100.

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


---

# 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/review-events-and-save-evidence/events/motion-events/axis-and-hanwha-cameras-people-counting-events.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.