> 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/understand-your-business/ai-features/vision-analytics/drive-off-detection.md).

# Drive-Off Detection

**Drive-Off Detection** allows you to track when drive-offs occur at your location.

Drive-offs occur most commonly in drive-thru lanes or oil change bays when a vehicle waits for service but drives away from the area without receiving service.

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-cacd12bbfc4c5940fbec9ca5876e795b812775a7%2F7cf6a4e2875b413a.gif?alt=media" alt="" width="560">

**Note**: Drive-Off Detection (included with [**Zone Tracking Events**](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md)**)** is only available with a subscription to [**Vision Analytics**](https://solink.com/ai/vision-analytics/).

***

## How to Enable Drive-Off

Drive-Off Detection can be enabled on any camera that is currently enabled with [Vision Analytics](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) and has at least one AI monitored zone.

In order to enable Drive-Off Detection for a specific zone, the zone type must also be one of the following:

* Queue
* Dwell

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-2a036732fab61001d032347749cf9285ce3e9a52%2Ff7a7390cae13cef4.png?alt=media" alt="" width="560">

To enable Drive-Off Detection in the Solink platform:

1. From the **Video** page, select an AI-enabled camera. See [Enable Vision Analytics](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) for more information.
2. Select **AI** > **Zone Tracking**.
3. Select the **Events** tab ([Zone Tracking Events](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md)).
4. Either create a new zone or use an existing zone to measure drive-offs.
5. For the chosen zone, select **Advanced Settings** > toggle the "Drive Off" option to "on":

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-ea85367a5de0a8cf5119425673d2bff5ddae79f6%2F88dbf920b3250fc8.png?alt=media" alt="" width="560">

**Note**: When creating/editing zones, the AI uses the currently selected video stream quality in the video player to review video footage (SD or HD). Try switching the stream from SD to HD to improve performance if needed.

***

## Drive-Off Events

Once a drive-off occurs (if you have enabled Drive-Off Detection as per the steps in the previous section), a drive-off event is created on the Events page:

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

The relevant Drive-Off event fields are defined below:

* **Drive-offs Detected**: Displays the total number of drive-offs recorded in this event. Typically this will be "1" to indicate one drive-off occurred.
* **Zone Label**: The name of the associated AI zone. You can change the zone name at any time - see [Zone Tracking Events](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md) for more information on zone configuration and editing.
* **Zone Time**: The total amount of time the vehicle(s) remained in the camera view until a drive-off occurred.

You can create a report using Drive-Off events to measure drive-off occurrences on the Dashboard page.

To locate drive-off events on the Events page:

1. Select the **AI** tab at the top of the page.
2. Select **Add Filter**.
3. Search for the **Drive-Off** filter in the filter list and select it.
4. Select "yes".
5. Select **Add**. All drive-off events are now displayed on the page:

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-4a6a3cbee966b905d8f4351b0c5c033b7240134c%2F8da1e71149c68540.png?alt=media" alt="" width="560">

***

## Drive Off FAQs

See the following for frequently asked questions (FAQs) around Drive-Off.

### How does Solink know when a drive-off occurs?

Solink decides what counts as a drive-off by comparing each vehicle's path to the normal flow of traffic it has learned for that zone.

For example, if traffic typically flows from one end of the zone to another (from the start of a drive-thru to the end), any deviation from this flow counts as a drive-off (exiting the drive-thru outside of the normal flow of traffic).

### What is the best camera placement to catch drive-offs?

[Refer to this guide](/docs/understand-your-business/ai-features/vision-analytics/camera-placement-guide-for-vision-analytics.md#line-cross-camera-placement-for-drive-offs) for information on how to optimize camera placement for capturing drive-offs.


---

# 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/understand-your-business/ai-features/vision-analytics/drive-off-detection.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.
