# Sales-intelligence traces

A trace records a site visitor's journey and acquisition source. Create a lead with `POST /v1/leads`, then pass its id in `entities` when creating a trace.

Bitrix24 API: `crm.tracking.trace.add`, `crm.tracking.trace.delete`

Scope: `crm`. A READWRITE key is required.

## Operations

- [Create a trace](./crm-traces/create.md) — `POST /v1/crm-traces`
- [Delete a trace](./crm-traces/delete.md) — `DELETE /v1/crm-traces/:id`

## Scenario: website form

Get the trace from `b24Tracker.guest.getTrace()`. Create a lead with the [leads API](./leads.md), then pass the returned id:

```json
{"trace":{"url":"https://example.com/form","ref":"https://example.com/news","tags":{"list":{"utm_source":"newsletter","utm_campaign":"autumn"}}},"entities":[{"type":"LEAD","id":123}]}
```

The REST API provides no trace read method. Deletion is idempotent: its response confirms neither trace existence nor removal of every binding.