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

# Recheck a Google Ads connection (/docs/api/google-ads/recheck-property-connection)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 929 · 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 conversion action readiness](/docs/api/google-ads/get-conversion-actions.md), [Get customer lists](/docs/api/google-ads/get-customer-lists.md)

> Verifies again that Product Metrics can reach the property's Google Ads account and marks the connection active when it can.

`POST https://prod-backend.productmetrics.io/api/public/v1/properties/{propertyId}/google-ads/connection/recheck`

**Scope** `setup` · **Access** Changes data · **Operation id** `google_ads.recheck_property_connection`

## 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 recheck-property-connection \
  --property-id $PROPERTY_ID \
  --json
```

**curl:**

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

## Response

API response (200):

```json
{
  "data": {
    "propertyId": "8c1f4d2e-7a3b-4c5d-9e6f-0a1b2c3d4e5f",
    "status": "active",
    "lastCheckedAt": "2026-11-02T09:30:00.000Z"
  },
  "request_id": "req_01JJ0TGZSD3XTTXCYF53PKWJD7"
}
```

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

## Before you call

Call it after fixing access (an accepted invite, a renewed Google sign-in) or when a connection shows status `error`. A 409 says the connection was revoked or what is still missing. Needs company admin.

## Path parameters

| Name         | Type   | Description                                                                                                         |
| ------------ | ------ | ------------------------------------------------------------------------------------------------------------------- |
| `propertyId` | string | 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 setup scope; connect again and allow it.",
    "details": {
      "required_scope": "setup"
    }
  },
  "request_id": "req_01JRSSMDYM3G23PG1K1W51EWXS"
}
```

| 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 `setup` 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`           | A 409 says the connection was revoked or what is still missing.                                                           |
| 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)
