> ## 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

# Get conversion action readiness (/docs/api/google-ads/get-conversion-actions)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 1203 · updated: 2026-11-16 -->
Related: [Create conversion actions](/docs/api/google-ads/create-conversion-actions.md), [Create customer lists](/docs/api/google-ads/create-customer-lists.md), [Connect a Google Ads account](/docs/api/google-ads/create-property-connection.md), [Disconnect a Google Ads account](/docs/api/google-ads/delete-property-connection.md), [Get customer lists](/docs/api/google-ads/get-customer-lists.md), [Get plan results](/docs/api/google-ads/get-plan-results.md)

> Whether the property's Google Ads account has the conversion actions Product Metrics reports purchases to: per purpose, whether the action exists and is linked, its goal status in Google Ads, and whether the account's acceptance by Google is verified.

`GET https://prod-backend.productmetrics.io/api/public/v1/properties/{propertyId}/google-ads/conversion-actions`

**Scope** `read` · **Access** Read only · **Operation id** `google_ads.get_conversion_actions`

## 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 google-ads get-conversion-actions \
  --property-id $PROPERTY_ID \
  --json
```

**curl:**

```bash
curl "https://prod-backend.productmetrics.io/api/public/v1/properties/$PROPERTY_ID/google-ads/conversion-actions" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response



API response (200):

```json
{
  "data": {
    "property_id": "8c1f4d2e-7a3b-4c5d-9e6f-0a1b2c3d4e5f",
    "action_registry_readiness": "not_configured",
    "provider_readiness": {
      "state": "accepted"
    },
    "actions": [
      {
        "purpose": "CUSTOMER_NEW",
        "registry_state": "missing",
        "conversion_action_id": "6f1c2a7e-3b4d-4e8f-9a01-2c3d4e5f6a7b",
        "goal_status": "unknown"
      }
    ],
    "report": {
      "state": "ready",
      "data": {
        "new_customers": 0,
        "returning_customers": 0,
        "revenue_micros": "108000000",
        "profit_micros": "48460000",
        "revenue_ltv_micros": "108000000",
        "profit_ltv_micros": "48460000",
        "orders": 14,
        "refunds_micros": "108000000",
        "unlinked_orders": 14,
        "unknown_margin_orders": 14,
        "currency_code": "EUR",
        "period_start_at": "2026-11-02T09:30:00.000Z",
        "period_end_at": "2026-11-02T09:30:00.000Z",
        "ltv_cutoff_at": "2026-11-02T09:30:00.000Z",
        "history_coverage": "complete",
        "cohort_basis": "first_authoritative_paid_order"
      }
    }
  },
  "request_id": "req_01JSZS4015Y85PTBRD5RKZKZ8Y"
}
```

**CLI output:** `productmetrics google-ads get-conversion-actions --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Read-only. Needs a Pro plan and read access to the workspace. If actions are missing, [`google_ads.create_conversion_actions`](/docs/api/google-ads/create-conversion-actions) creates them.

## Path parameters

| Name         | Type          | Description                                                                                                         |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------------- |
| `propertyId` | string (uuid) | The property id, from `productmetrics whoami` or [`properties.list`](/docs/api/account/properties-list) (`property_id`). |

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

| 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. |
| 402    | `subscription_required` | The workspace has no Pro plan.                                                                                            |
| 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`          | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Google Ads operations](/docs/api/google-ads)
