> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadinfo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trackers

> A tracker is one tracking script on one website. Every company, session and analytics endpoint is scoped to a tracker code.

A tracker corresponds to the Leadinfo tracking script installed on a website or subdomain. Visits are recorded under the tracker they came from, and every per-website endpoint lives under `/v1/trackers/{tracker_code}/...`.

## List your trackers

```bash cURL theme={null}
curl --request GET \
  --url "https://data.leadinfo.com/v1/trackers" \
  --header "Authorization: Bearer <token>"
```

```json theme={null}
{
  "data": [
    {
      "code": "LI-5A14070B93509",
      "domain": "leadinfo.com",
      "company_name": "Leadinfo B.V.",
      "company_id": 35483,
      "customer_id": 1,
      "has_data": true
    }
  ],
  "meta": { "returned": 1 }
}
```

| Field | Description |
| - | - |
| `code` | The tracker code. Use it in every tracker-scoped path. |
| `domain` | The website the script is installed on. |
| `company_name`, `company_id`, `customer_id` | The Leadinfo account that owns the tracker. |
| `has_data` | `false` for trackers that never received traffic; querying them returns empty results. |

> [!TIP]
>
> Tracker codes are stable. Cache the list at start-up instead of fetching it on every request.

## Partner accounts

A partner account sees its own trackers and the trackers of every company it manages. `GET /v1/auth/me` reports `is_partner` and `managed_companies`. Tags, segments and personas follow the same visibility.

## Self-traffic

Visits from the tracker owner's own company are excluded from every tracker endpoint, so your own employees never show up as visiting companies.

## Ownership errors

Requesting a tracker that is not visible to the token returns `403 Forbidden`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.