> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/analytics/vehicle-analytics/lpr-and-analytics-day-only.md).

# LPR and Analytics (Day Only)

The Verkada LPR and Analytics feature allows supported cameras to capture license plate reads and vehicle and people attributes simultaneously. Previously, cameras had to run either License Plate Recognition (LPR) or general analytics. With this feature, a single camera can perform both tasks in a single pass, providing visibility into license plates, people, and vehicles entering and exiting your sites.

***

#### Requirements

* **Model support:** This feature supports only the latest bullet series, the CBx3 line. Other camera models do not support simultaneous LPR and vehicle attribute detection.
* **Daytime only:** Cameras can run LPR and vehicle analytics simultaneously during **daytime** hours only.

#### How it works

The feature uses edge processing to analyze vehicles in real time.

* **Single-pass capture:** A single camera captures the license plate number and identifies key vehicle attributes, including the **make, model, and color**, from a single video stream.
* **Streamlined asset tracking:** Command indexes the license plate and vehicle attribute data together. You can search for a specific license plate number or filter results by vehicle color, make, and model from the same search interface.

***

## Enable LPR and vehicle analytics

{% hint style="danger" %}
You must have **Org Admin** or **Site Admin** permissions for the site where the camera is located to modify analytics settings.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**From the camera list, select the supported camera you want to configure.**
{% endstep %}

{% step %}
**In the top right, click Settings.**
{% endstep %}

{% step %}
**On the left, click Analytics.**
{% endstep %}

{% step %}
**Toggle on License Plate Recognition and complete the setup.**
{% endstep %}

{% step %}
**Toggle on Vehicle History.** 

This enables you to search for vehicle attributes based on vehicle detections from your CB63 camera.
{% endstep %}

{% step %}
**(Optional) Enable People History.** 

This enables you to search for attributes of people detections from your CB63 camera.
{% endstep %}

{% step %}
**Click Save to apply your changes.**
{% endstep %}
{% endstepper %}

***

## Search and filter vehicle events

Once enabled, you can search and filter for captured plates, as well as vehicle and people attributes (if you have enabled people history).

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**On the left navigation, select Vehicles.**
{% endstep %}

{% step %}
**Use the search bar and filter dropdowns at the top of the page to refine your search.**

* Enter a full or partial **License Plate** number.
* Use the **Attributes** filters to select specific vehicle characteristics, such as **Color**, **Make**, or **Model**.
  {% endstep %}

{% step %}
**Review the search results.** 

Click on any captured vehicle thumbnail to view the associated video recording, plate read, and detected vehicle attributes.
{% endstep %}
{% endstepper %}


---

# 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.verkada.com/verkada-cameras/analytics/vehicle-analytics/lpr-and-analytics-day-only.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.