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

# Workspaces and properties (/docs/concepts/workspaces-and-properties)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1696 · updated: 2026-11-16 -->
Related: [How Product Metrics works](/docs/concepts/how-it-works.md), [Conversion values](/docs/concepts/conversion-values.md), [Profit](/docs/concepts/profit.md), [New and returning customers](/docs/concepts/new-and-returning-customers.md), [Conversion actions and events](/docs/concepts/conversion-actions-and-events.md), [Consent](/docs/concepts/consent.md)

> How Product Metrics organises your company, stores, storefronts and ad accounts, and who can do what.

**A workspace is your company. A property is one Google Ads account in your workspace, with the store assigned to it. Storefront scopes connect a store's orders to a property.**

Most setups have one workspace with one property. Agencies and multi-store brands have several properties, each with its own Google Ads account, Meta pixel, ChatGPT Ads (OpenAI) pixel and customer history. The pipeline these feed is [How it works](/docs/concepts/how-it-works).

## Workspace vs property

|                | **Workspace**                                 | **Property**                                                                                                       |
| -------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **What**       | Your company                                  | One Google Ads account, with the store assigned to it                                                              |
| **Example**    | Example Shop                                  | Example Shop NL                                                                                                    |
| **Holds**      | Members and roles, billing, store connections | Google Ads account, Merchant Center, Meta destination, ChatGPT Ads destination, conversion actions, customer lists |
| **Created by** | Signing up and naming your workspace          | Connecting a Google Ads account                                                                                    |

## How they fit together

```text
Workspace  Example Shop
├── Store connection  Shopify  shop.example.com
│   ├── Storefront scope  NL (default)
│   │     → Property  Example Shop NL
│   │         Google Ads 123-456-7890, Meta pixel 1111…,
│   │         ChatGPT Ads pixel 3333…, 8 conversion actions
│   └── Storefront scope  DE (/de, EUR)
│         → Property  Example Shop DE
│             Google Ads 987-654-3210, Meta pixel 2222…
└── Members  admin, editor, viewer
```

### Store connection

One connected store: Shopify, WooCommerce, Magento, Lightspeed, Shopware or a website on Cloudflare. A connection belongs to the workspace.

### Storefront scope

One storefront of a connection, defined by country, path prefix, locale or currency, with one default.

* Each scope is assigned to a property.
* Its orders count for that property and go to its Google Ads account.
* Orders and order history are read per scope.

### Destinations

Where a property's purchases go:

| Destination    | Per                                                                  | Set up on                                 |
| -------------- | -------------------------------------------------------------------- | ----------------------------------------- |
| Google Ads     | Property: its Google Ads account and conversion actions              | [Google Ads](/docs/channels/google-ads)        |
| Meta           | Property: one Meta Conversions API destination (pixel)               | [Meta](/docs/channels/meta)                    |
| ChatGPT Ads    | Property: one OpenAI Conversions API destination (ChatGPT Ads pixel) | [ChatGPT Ads](/docs/channels/openai)           |
| Customer lists | Property's Google Ads account, filled per store                      | [Customer lists](/docs/features/customer-list) |

## Roles

| Role       | Can                                                                                                                 |
| ---------- | ------------------------------------------------------------------------------------------------------------------- |
| **viewer** | Read everything in the workspace, including through the CLI and MCP                                                 |
| **editor** | Also change settings: connect stores, set the Meta and ChatGPT Ads destinations, assign storefronts, file proposals |
| **admin**  | Also create Google Ads conversion actions, invite members, manage billing                                           |

Invite people on [Team](/docs/using/team); it needs an admin.

## Rules

1. **One store per property.** Assign a storefront to the property whose Google Ads account advertises it. Two stores sharing one property mix their orders.
2. **Customer history stays per store.** A customer of two stores is new in each.
3. **Conversion action names are per Google Ads account.** Two workspaces can't both manage the Product Metrics actions in the same Google Ads account.
4. **Pro per property.** Orders, inventory and the MCP server need a Pro subscription for the property. Connecting any platform except Shopify needs Pro too.

## For developers



**For developers: addressing from the CLI, API and MCP**

| You need     | CLI                     | API path                                    | MCP                                     |
| ------------ | ----------------------- | ------------------------------------------- | --------------------------------------- |
| Workspace    | `--company-id`          | `/companies/:companyId/…`                   | `company_id` from `list_properties`     |
| Property     | `--property-id`         | `/properties/:propertyId/…`                 | `property_id` (optional with one store) |
| Storefront   | `--storefront-scope-id` | `?storefront_scope_id=`                     | From `tracking.get_configuration`       |
| Installation | `--installation-id`     | `/tracking/installations/:installationId/…` | From `tracking.get_configuration`       |

One MCP connection covers every property you can open. The assistant calls `list_properties` first, then passes `property_id` to every other tool.

Ids come from reads: take `company_id` and `property_id` from `productmetrics whoami` or `productmetrics properties list`, and `storefront_scope_id` and `installation_id` from `productmetrics tracking get-configuration`. Never guess them.

## Try it

**Ask your assistant:** "Which stores can you see in Product Metrics, and which storefronts feed each one?"

You should see one entry per property, with its name, workspace, Google Ads account and currency.

## Where next

| If you need…          | Go to                                           |
| --------------------- | ----------------------------------------------- |
| Create your workspace | [Create a workspace](/docs/using/create-a-workspace) |
| Invite your team      | [Team](/docs/using/team)                             |
| Subscriptions         | [Billing](/docs/using/billing)                       |
| Connect a store       | [Choose your platform](/docs/platforms/overview)     |
| Connect an assistant  | [Connect Claude or ChatGPT](/docs/mcp/connect)       |
