# Attributions and Conversions (/attributions-and-conversions)



**Conversions** let you tell LettrLabs when a recipient took action after
receiving your mail — a purchase, a signup, a booked appointment — so you can
attribute outcomes to a campaign and measure return on your direct mail.

## Record conversions [#record-conversions]

Send one or more conversions in a single call to `POST /v1/conversions`. The
exact body — what identifies a recipient, the conversion value, and any
metadata — is documented on the [`POST /v1/conversions`](/api-reference/conversions/v1-conversions-post)
reference page, with a live console.

```bash
curl -X POST https://app.lettrlabs.com/api/v1/conversions \
  -H "X-API-KEY: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '[ { /* see the reference for the conversion shape */ } ]'
```

## Read conversions back [#read-conversions-back]

| Action                        | Endpoint                                                                                     |
| ----------------------------- | -------------------------------------------------------------------------------------------- |
| List all conversions          | [`GET /v1/conversions`](/api-reference/conversions/v1-conversions-get)                       |
| Check one conversion's status | [`GET /v1/conversions/{id}/status`](/api-reference/conversions/v1-conversions-id-status-get) |
| Delete conversions            | [`DELETE /v1/conversions/{id}`](/api-reference/conversions/v1-conversions-id-delete)         |

Each is documented in full, with parameters and response schemas, under
[API Reference](/api-reference).

## How attribution fits together [#how-attribution-fits-together]

1. You **send mail** with [an order](/creating-an-order).
2. A recipient **acts** — and your system calls `POST /v1/conversions` to record
   it.
3. You **read conversions back** for reporting, or check an individual
   conversion's processing status.

For richer recipient‑level reporting, see the **Order Recipient Analytics**
group in the [API Reference](/api-reference).