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

# Get customer lists (/docs/api/google-ads/get-customer-lists)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 1170 · 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 plan results](/docs/api/google-ads/get-plan-results.md)

> The Google Ads Customer Match lists Product Metrics manages for the property (one per list kind): whether each is not provisioned, provisioning, managed or in conflict, and the Google Ads account they live in.

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

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

## Try it

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



**productmetrics CLI:**

```bash
productmetrics google-ads get-customer-lists \
  --property-id $PROPERTY_ID \
  --company-id $COMPANY_ID \
  --json
```

**curl:**

```bash
curl "https://prod-backend.productmetrics.io/api/public/v1/properties/$PROPERTY_ID/google-ads/customer-lists?company_id=$COMPANY_ID" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response



API response (200):

```json
{
  "data": {
    "google_ads_customer_id": "1234567890",
    "lists": [
      {
        "kind": "all_customers",
        "state": "not_provisioned",
        "display_name": "Product Metrics - All customers - Example Store",
        "user_list_id": "1234567890",
        "required_customer_type_categories": [
          "ALL_CUSTOMERS"
        ],
        "customer_type_categories": [
          "ALL_CUSTOMERS"
        ],
        "complete": true,
        "conflict_code": "duplicate_display_name",
        "updated_at": "2026-11-02T09:30:00.000Z"
      }
    ]
  },
  "request_id": "req_01JX87GABSTDK2PEZ4SP12PM6B"
}
```

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

## Before you call

Read-only. Needs read access to the property. If lists are missing, [`google_ads.create_customer_lists`](/docs/api/google-ads/create-customer-lists) 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`). |

## Query parameters

| Name         | Type          | Required | Description                                                                                           |
| ------------ | ------------- | -------- | ----------------------------------------------------------------------------------------------------- |
| `company_id` | string (uuid) | Yes      | Your workspace id, from `productmetrics whoami` or [`properties.list`](/docs/api/account/properties-list). |

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

| 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    | `property_not_found` | The property does not exist in this workspace.                                                                            |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |
| 503    | `internal_error`     | The lists could not be read just now: retry later.                                                                        |

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