Skip to content
Stores and tracking

Check tracking works

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 /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). Set $COMPANY_ID, $INSTALLATION_ID first.

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

Response

API response (200):

{
  "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

NameTypeDescription
companyIdstring (uuid)Your workspace id, from productmetrics whoami or properties.list (company_id).
installationIdstring (uuid)The tracking installation: installationId from tracking.get_commerce_configuration or 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.

{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JDDQ8T7AP4T1N4QP1VYY6ANP"
}
StatusCodeWhen
400invalid_requestA path, query or body value does not match this page. details.issues lists each location, path and message.
401invalid_tokenThe token is missing, expired or revoked: sign in again (productmetrics login). The WWW-Authenticate header says why.
403insufficient_scopeThe token lacks the read scope (details.required_scope): sign in again and allow it.
404not_foundAn id in the path does not exist, or the signed-in person cannot open it.
409conflictAnswers 409 for an installation that is a store connection rather than a website.
429rate_limitedMore than 600 requests a minute for this person: wait the Retry-After seconds (60) and retry.

All Stores and tracking operations