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

# Product Metrics in Claude (/docs/integrations/claude)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1972 · updated: 2026-11-16 -->
Related: [Product Metrics in ChatGPT](/docs/integrations/chatgpt.md), [Product Metrics in Claude Code](/docs/integrations/claude-code.md), [Product Metrics in Codex](/docs/integrations/codex.md), [Product Metrics in Cursor](/docs/integrations/cursor.md)

> Add Product Metrics to Claude on the web and Claude Desktop as a custom connector, sign in, and ask about your store and Google Ads.

Add Product Metrics to Claude (claude.ai and the Claude desktop app) as a **custom connector**. It connects to the **MCP server** at `https://www.productmetrics.io/mcp`. Claude can then:

* read your stores, products and Google Ads account
* explain what changed and report profit on ad spend
* run setup steps such as connecting your store

You sign in in your browser. There is no API key. A connector you add on claude.ai also appears in the desktop app, and the other way round.

## Install



**1. Open connectors**

In Claude, open [**Add custom connector**](https://claude.ai/new?modal=add-custom-connector#customize/connectors) (or **Settings → Connectors → Add custom connector**).

**2. Enter the name and URL**

| Field                     | Value                               |
| ------------------------- | ----------------------------------- |
| **Name**                  | `Product Metrics`                   |
| **Remote MCP server URL** | `https://www.productmetrics.io/mcp` |

Leave **OAuth Client ID** and **OAuth Client Secret** empty: Claude registers itself. Click **Add**.

`productmetrics mcp-config --client claude` prints the same steps with the URL filled in.

## Authenticate

Product Metrics appears under your connectors. Click **Connect**.

A Product Metrics page opens: sign in, or choose **Continue with Google** to create an account. The page says Claude wants to use your account and lists what Claude **Can read** and **Can change**. Click **Connect Claude**.

Access tokens last one hour and renew on their own. If you don't use the connector for 30 days, connect again.

## How it works

* **Pick a store first.** One connection covers every store (property) you can open. Claude calls `list_properties`, then passes the store to every other tool. With one store, it uses that one without asking.
* **Analysis tools read live.** Tools such as `explain_google_ads_change`, `get_google_ads_report` and `get_poas_report` read your Google Ads account and your store's margins and stock. They never change Google Ads or your store.
* **Setup runs through Code Mode.** `search` finds an API operation; `execute` runs code that calls it: setup status, connecting stores and Google Ads, creating conversion actions. Operations that delete something run only after you confirm.
* **Browser steps come back as a link.** Google consent, a store install or checkout needs you in a browser. Claude gives you the link, waits, then reads the setup status again.
* **Secrets stay out of the chat.** Fields such as a store setup token never reach Claude. They show only in the Product Metrics app or the CLI.

## Tools

| Tool                           | Description                                                     |
| ------------------------------ | --------------------------------------------------------------- |
| `list_properties`              | The stores (properties) you can open; called first              |
| `get_store_overview`           | The store's own sales, orders and profit next to the ads        |
| `explain_google_ads_change`    | Why a Google Ads metric changed, in one call                    |
| `get_google_ads_report`        | Live Google Ads performance at any level                        |
| `get_poas_report`              | Profit on ad spend per product, campaign or account, with stock |
| `get_google_ads_changes`       | Who changed what in the account, last 30 days                   |
| `list_products_to_investigate` | Products that need attention first                              |
| `propose_change`               | File a proposal that a person approves in **Priorities**        |
| `search` / `execute`           | The whole Product Metrics API in Code Mode                      |

All 24 analysis tools and their arguments: [MCP tools](/docs/mcp/tools).

## What you can ask

In a new chat, check that **Product Metrics** is on in the tools menu, then ask:

```text
"Where is my Product Metrics setup, and what is the next step?"
→ execute (GET /setup/status)

"Connect my Shopify store to Product Metrics."
→ execute (POST /companies/:companyId/stores), then a link to approve
  the install in Shopify Admin

"Create the Product Metrics conversion actions in Google Ads."
→ execute (POST /properties/:propertyId/google-ads/conversion-actions)

"Which products lose money after ads this month?"
→ list_properties, then get_poas_report (level: product,
  only_unprofitable: true)

"Why did my Google Ads ROAS drop last week?"
→ list_properties, then explain_google_ads_change
```

## Skills

The Product Metrics skills (`set-up-tracking`, `connect-google-ads`, `check-tracking`, `bid-on-profit`, `analyse-google-ads`) are written for agents that install them with `npx skills`, such as [Claude Code](/docs/integrations/claude-code). In Claude on the web and desktop, the connector alone is enough: the tools carry their own instructions.

The `productmetrics` CLI is for terminals and coding agents; Claude on the web and desktop uses the connector instead.

## Configuration

### Pin one store

To give Claude one store only, add the property to the connector URL. The analysis tools then read that store without asking; `search` and `execute` still work on your whole account.

```text
https://www.productmetrics.io/mcp?selectedAccountPropertyId=<propertyId>
```

### Turn the tools on or off per chat

Use the tools menu in a chat to switch **Product Metrics** on or off. To remove it everywhere, open **Settings → Connectors** and remove it.

## Troubleshooting

| What Claude says                                                                  | What to do                                                                                                                      |
| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| "This connection expired or was removed; connect Product Metrics again."          | In **Settings → Connectors**, click **Connect** on Product Metrics again. If that fails, remove the connector and add it again. |
| "This connection only has MCP access, so it cannot call the Product Metrics API." | Remove the connector, add it again and allow everything the consent page shows.                                                 |
| "The MCP server is not enabled for this account yet."                             | Ask Product Metrics support to turn it on for your account.                                                                     |
| "This property needs a Product Metrics Pro subscription for the MCP server."      | Upgrade that store to Pro, or ask about another store.                                                                          |
| "No property chosen."                                                             | Name the store in your question; Claude calls `list_properties` and tries again.                                                |
| "The limit of … tool calls per hour … is reached."                                | Wait the minutes it names. Expensive tools have a lower hourly limit: see [MCP tools](/docs/mcp/tools).                              |
| Claude doesn't use Product Metrics                                                | Check that **Product Metrics** is on in the chat's tools menu, and name your store in the question.                             |

## Where next

* [Setup and usage](/docs/mcp/connect): how sign-in works, every client
* [MCP tools](/docs/mcp/tools): every tool and argument
* [MCP overview](/docs/mcp/overview): access control and disconnecting
* [Claude Code](/docs/integrations/claude-code) · [ChatGPT](/docs/integrations/chatgpt)
