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

# Quickstart (/docs/quickstart)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1394 · updated: 2026-11-16 -->
Related: [Introduction](/docs/index.md)

> Set up Product Metrics in the app, from your workspace to the first order in Google Ads, in six steps.

By the end of this page you will:

1. **Create a workspace and connect your store** (where orders and product costs come from)
2. **Connect Google Ads and Merchant Center** (where conversions go)
3. **Set your consent banner** (so each channel only gets what the visitor allowed)
4. **Create the conversion actions** in Google Ads
5. **Add your costs** (so profit is complete)
6. **See your first order arrive** with its profit

Every paid order goes from your **store** to your **ad channels**, with its **profit** and whether the customer is **new or returning**.

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "Set up Product Metrics for my store, from connecting the store to sending the first order to Google Ads. Check my setup status first, walk me through each open step, and give me the link when I need to click something."

**Claude Code or Codex:** "Set up Product Metrics for my store, from connecting the store to sending the first order to Google Ads, and give me the link when I need to click something. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first)."

## In the app

### 1. Create a workspace and connect your store

Sign in at [app.productmetrics.io](https://app.productmetrics.io) and follow onboarding to name your **workspace**. It holds your stores, team and billing.

Then go to **Ecommerce platforms → Connect Shopify → Open Shopify App Store**. Other platforms: [choose yours](/docs/platforms/overview) (WooCommerce, Magento, Lightspeed, Shopware, or Cloudflare for a website without a store).



![The Ecommerce platforms page in Product Metrics, listing Shopify, WooCommerce, Magento, Shopware 6 and Lightspeed with a Connect button each, and Cloudflare Tracking for any other website.](/docs/_assets/b823ab60bccfe09fe85e1f76a3df731b71212ebac9e8ec285dc810ae503ed5a7)

*Figure: Ecommerce platforms: pick your platform and select Connect.*

In Shopify, **Install** the app, select **Connect Product Metrics account**, choose your workspace and select **Link Shopify store**. Then turn on **Product Metrics** under **App embeds** in the theme editor and **Save**, and select **Create subscription**: Shopify bills the app.

You should see **You're set up** with three ticks.

### 2. Connect Google Ads and Merchant Center

Go to **Ecommerce platforms**, select your store, then **Connect Google Ads → Continue with Google** and tick **Google Ads**. Pick the **client account** that runs your campaigns, not a manager account. **Merchant Center** is part of the Google Ads setup: link it to that Google Ads account in Google first.

You should see your Google Ads account under your store. Details: [Google Ads](/docs/channels/google-ads), [Merchant Center](/docs/using/merchant-center).

### 3. Set your consent banner

Consent decides what each channel may receive. Go to **Tracking → Complete your tracking setup → Configure consent** and choose the banner your store shows; on Shopify that is usually **Shopify Customer Privacy**.

You should see **Configure consent** ticked off with the banner you chose. Details: [Consent](/docs/using/consent).

### 4. Create the conversion actions

Go to **Tracking → Complete your tracking setup → Create Google Ads conversions** and select **Create 8 conversion actions**. They start as **secondary**, so your campaigns don't change yet.

You should see **Conversion actions** read **Tracking ready**; **Setting up** is normal for about 15 minutes. Details: [Conversion actions](/docs/using/conversion-actions).

### 5. Add your costs

Profit needs your shipping, handling, returns and payment fees. Go to **Tracking → Complete your tracking setup → Add your additional costs**, check the defaults Product Metrics prefilled for your country, and select **Activate additional costs**.

You should see **Profit tracking** say your additional costs are active. Details: [Costs](/docs/using/costs).

### 6. Check the first order

Place and pay for a test order, then open **Tracking**.

You should see the badge read **Tracking active** and **Conversion actions** read **Tracking ready**, and the order with its revenue, profit and **new** or **returning** customer. What the two badges mean: [App badges](/docs/using/check-tracking#app-badges).

## Optional: also send to Meta or ChatGPT Ads

Not one of the six steps. Server-side tracking (**Full Signal Tracking**) also sends each order to your **Meta** pixel and to **ChatGPT Ads (OpenAI)**. You need the pixel ID and an access token or API key from that channel.

Go to **Tracking → Meta Conversions API → Connect Meta**, or **Tracking → OpenAI Conversions API → Connect OpenAI**. You should see the test event accepted. Steps and custom conversions: [Meta](/docs/channels/meta), [ChatGPT Ads](/docs/channels/openai).

## Where next



* [POAS bidding](/docs/features/poas-bidding): bid on profit with a target ROAS as a %.
* [How it works](/docs/concepts/how-it-works): from paid order to conversion action.
* [Connect Claude or ChatGPT](/docs/mcp/connect): ask for a POAS report per campaign.
* [Quickstart for developers](/docs/cli/quickstart): the same setup from the CLI, MCP or API.

Developers: do the same with the [CLI](/docs/cli/quickstart) or the [API](/docs/api/account/setup-get-status).
