> ## Documentation Index
> Fetch the complete documentation index at: https://f82cc46-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://f82cc46-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://f82cc46-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://f82cc46-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Recommend minimum clicks (/docs/api/settings/recommend-min-clicks)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 1275 · updated: 2026-11-16 -->
Related: [Generate the feed now](/docs/api/settings/feed-generate.md), [Get feed source settings](/docs/api/settings/feed-source-settings-get.md), [Save feed source settings](/docs/api/settings/feed-source-settings-update.md), [Get Product Segmentation settings](/docs/api/settings/get.md), [Get inventory planning settings](/docs/api/settings/inventory-settings-get.md), [Save an inventory planning setting](/docs/api/settings/inventory-settings-update.md)

> Computes the minimum clicks a product needs before Product Segmentation segments it, so the best sellers (Stars) carry a healthy share of revenue, from the property's Google Ads data.

`POST https://prod-backend.productmetrics.io/api/public/v1/properties/{propertyId}/settings/recommend-min-clicks`

**Scope** `read` · **Access** Read only · **Operation id** `settings.recommend_min_clicks`

## Try it

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



**productmetrics CLI:**

```bash
productmetrics settings recommend-min-clicks --property-id $PROPERTY_ID --json
```

**curl:**

```bash
curl -X POST "https://prod-backend.productmetrics.io/api/public/v1/properties/$PROPERTY_ID/settings/recommend-min-clicks" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response



API response (200):

```json
{
  "data": {
    "recommended_min_clicks": 120,
    "confidence": "high",
    "reason_code": "target_reached",
    "target": {
      "stars_revenue_min": 12.5,
      "stars_revenue_max": 12.5,
      "stars_revenue_ideal": 12.5
    },
    "result": {
      "min_clicks": 120,
      "score": 12.5,
      "stars_revenue_share": 0.25,
      "stars_product_share": 0.25,
      "stars_count": 42,
      "total_products": 42,
      "low_volume_product_share": 0.25
    },
    "coarse_results": [
      {
        "min_clicks": 120,
        "score": 12.5,
        "stars_revenue_share": 0.25,
        "stars_product_share": 0.25,
        "stars_count": 42,
        "total_products": 42,
        "low_volume_product_share": 0.25
      }
    ],
    "refinement_results": [
      {
        "min_clicks": 120,
        "score": 12.5,
        "stars_revenue_share": 0.25,
        "stars_product_share": 0.25,
        "stars_count": 42,
        "total_products": 42,
        "low_volume_product_share": 0.25
      }
    ]
  },
  "request_id": "req_01JHFHJRSW80CX3VNS9K3QPHZN"
}
```

**CLI output:** `productmetrics settings recommend-min-clicks --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Saves nothing: put `recommended_min_clicks` into the settings from [`settings.get`](/docs/api/settings/get), check it with [`settings.preview`](/docs/api/settings/preview), then save with [`settings.update`](/docs/api/settings/update). Takes up to a minute; a 429 means the same calculation is already running, so wait and call again.

## Path parameters

| Name         | Type          | Description                                                           |
| ------------ | ------------- | --------------------------------------------------------------------- |
| `propertyId` | string (uuid) | A property_id from [`properties.list`](/docs/api/account/properties-list). |

## Query parameters

| Name         | Type   | Required | Description                                                                                                            |
| ------------ | ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| `feed_scope` | string | No       | Which feed of the property: a feed id, or `all` for the property-wide settings. Omitted: the property's default scope. |

## 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_01JJQ7EZJVSERKTCZA10XS2EQ1"
}
```

| 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.                                                 |
| 429    | `rate_limited`       | Takes up to a minute; a 429 means the same calculation is already running, so wait and call again.                        |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Settings and rules operations](/docs/api/settings)
