> ## Documentation Index
> Fetch the complete documentation index at: https://996f455-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://996f455-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://996f455-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://996f455-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Check tracking works (/docs/api/stores-and-tracking/tracking-get-last-purchase)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 1148 · updated: 2026-11-16 -->
Related: [Connect a store](/docs/api/stores-and-tracking/stores-connect.md), [New WooCommerce setup token](/docs/api/stores-and-tracking/stores-create-woocommerce-setup-claim.md), [Choose the store platform](/docs/api/stores-and-tracking/stores-select-platform.md), [Assign a store to a property](/docs/api/stores-and-tracking/tracking-assign-property.md), [Track a website](/docs/api/stores-and-tracking/tracking-create-website-installation.md), [Get store connections](/docs/api/stores-and-tracking/tracking-get-commerce-configuration.md)

> The is-tracking-working check for a tracked website (Cloudflare Tracking installation): the newest purchase tracking received, with its transaction id, value, currency and time, or null when none arrived yet.

`GET https://prod-backend.productmetrics.io/api/public/v1/companies/{companyId}/tracking/installations/{installationId}/last-purchase`

**Scope** `read` · **Access** Read only · **Operation id** `tracking.get_last_purchase`

## Try it

`productmetrics` runs after `productmetrics login`; curl needs `PM_TOKEN` (see [Authentication](/docs/api/overview#authentication)). Set `$COMPANY_ID`, `$INSTALLATION_ID` first.



**productmetrics CLI:**

```bash
productmetrics tracking get-last-purchase \
  --company-id $COMPANY_ID \
  --installation-id $INSTALLATION_ID \
  --json
```

**curl:**

```bash
curl "https://prod-backend.productmetrics.io/api/public/v1/companies/$COMPANY_ID/tracking/installations/$INSTALLATION_ID/last-purchase" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response

API response (200):

```json
{
  "data": {
    "lastPurchase": {
      "transactionId": "6f1c2a7e-3b4d-4e8f-9a01-2c3d4e5f6a7b",
      "valueMicros": "108000000",
      "currencyCode": "EUR",
      "receivedAt": "2026-11-02T09:30:00.000Z"
    }
  },
  "request_id": "req_01JT8G4FHECW224ECY51ZS1R50"
}
```

**CLI output:** `productmetrics tracking get-last-purchase --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Ask the person to place a test order on the website, then call this until it shows that order. Answers 409 for an installation that is a store connection rather than a website.

## Path parameters

| Name             | Type          | Description                                                                                                                                                                                                                                    |
| ---------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `companyId`      | string (uuid) | Your workspace id, from `productmetrics whoami` or [`properties.list`](/docs/api/account/properties-list) (`company_id`).                                                                                                                           |
| `installationId` | string (uuid) | The tracking installation: `installationId` from [`tracking.get_commerce_configuration`](/docs/api/stores-and-tracking/tracking-get-commerce-configuration) or [`tracking.get_configuration`](/docs/api/stores-and-tracking/tracking-get-configuration). |

## Errors

A failure answers with its HTTP status and `{ error: { code, message, details? }, request_id }`. Branch on `code` (stable, lower_snake); show `message` to the person. The CLI prints the same `error` with `"ok": false`.

```json
{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JDDQ8T7AP4T1N4QP1VYY6ANP"
}
```

| Status | Code                 | When                                                                                                                      |
| ------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| 400    | `invalid_request`    | A path, query or body value does not match this page. `details.issues` lists each `location`, `path` and `message`.       |
| 401    | `invalid_token`      | The token is missing, expired or revoked: sign in again (`productmetrics login`). The `WWW-Authenticate` header says why. |
| 403    | `insufficient_scope` | The token lacks the `read` scope (`details.required_scope`): sign in again and allow it.                                  |
| 404    | `not_found`          | An id in the path does not exist, or the signed-in person cannot open it.                                                 |
| 409    | `conflict`           | Answers 409 for an installation that is a store connection rather than a website.                                         |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Stores and tracking operations](/docs/api/stores-and-tracking)
