> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/connectors/tracker-connector.md).
# Tracker Connector
Connect OBD2, CAN bus, and GPS vehicle trackers to Kilo IoT Server with the Tracker connector and its model templates.
The Tracker connector enables the Kilo IoT Server to accept data from vehicle trackers — OBD2, CAN bus, and standalone GPS vehicle tracking devices. The server includes preconfigured templates for over 2,000 vehicle tracker models.
## Adding the Tracker connector
1. Navigate to **Connectors** in the sidebar.
2. Click **Add connector**.
3. In the **Connector type** dropdown, select **Tracker**.
4. Click **Add**.
The connector is created immediately. Each organization can have only one Tracker connector.
## Inside the Tracker connector
Click the Tracker connector row in the connectors table to open it. This shows the shared device list. When registering a device through the Tracker connector, the **Connection** tab includes tracker-specific fields: **Unique ID**, **Device model**, and a **Url for GPS tracker** endpoint.
For device registration and management, see [Registering Devices](/devices/registering-devices.md) and [Device Management](/devices/device-management.md).
---
# 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://docs.kiloiot.io/connectors/tracker-connector.md?ask=&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.
