Workspaces and properties
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.
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
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, viewerStore 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 |
| Meta | Property: one Meta Conversions API destination (pixel) | Meta |
| ChatGPT Ads | Property: one OpenAI Conversions API destination (ChatGPT Ads pixel) | ChatGPT Ads |
| Customer lists | Property’s Google Ads account, filled per store | Customer lists |
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; it needs an admin.
Rules
- One store per property. Assign a storefront to the property whose Google Ads account advertises it. Two stores sharing one property mix their orders.
- Customer history stays per store. A customer of two stores is new in each.
- Conversion action names are per Google Ads account. Two workspaces can’t both manage the Product Metrics actions in the same Google Ads account.
- 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
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 |
| Invite your team | Team |
| Subscriptions | Billing |
| Connect a store | Choose your platform |
| Connect an assistant | Connect Claude or ChatGPT |