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

# Should I use Product Metrics? (/docs/overview/comparison)

<!-- agent-signals: reading_time_min: 6 · est_tokens: 2130 · updated: 2026-11-16 -->
Related: [Agents, skills and MCP](/docs/overview/agents-skills-and-mcp.md), [What is Product Metrics?](/docs/overview/what-is-product-metrics.md)

> How Product Metrics compares with the standard Google Ads tag and Meta pixel, Google tag gateway and server-side Google Tag Manager, and ProfitMetrics, Producthero, DataFeedWatch and Channable.

This page compares the **ways stores send conversions to Google Ads and Meta**, and the tools stores weigh against Product Metrics. For each: what it is, when it is enough, where it breaks, and what Product Metrics does instead.

Product Metrics is **the operating system of ecommerce**: it maximises product performance and grows your profit. It combines **server-side conversion tracking**, **bidding on POAS, new customers, returning customers and LTV**, a **profitability dashboard** (profit, POAS and ROAS per product and campaign) and **Product Segmentation**. The full product is in [What is Product Metrics?](/docs/overview/what-is-product-metrics).

The tracking part confirms every paid order from your shop's own data and sends it from the server, with its revenue, profit, new or returning customer and lifetime value.

## vs the standard Google Ads tag and Meta pixel

**What this path is:** the browser tags Google and Meta give you. The tag fires on the thank-you page and reports the order's revenue.



![With a standard Google Ads tag or Meta pixel, the browser calls a tracking domain that ad blockers list, so the request is blocked and the sale is lost. Full Signal Tracking calls a unique endpoint on your own domain, which gets through, and Product Metrics sends the confirmed order from its server.](/docs/_assets/8cf6a8539b13863d2f07ff8a5f7960a90a7e44fbe29a7a7a90b72412246a57e3)

*Figure: Standard tags vs server-side tracking on your own domain.*

**When it is enough**

* You bid on revenue and accept that part of your orders never reaches Google Ads or Meta
* Your margins are the same on every product
* You don't need to tell new customers from returning ones

**Where it breaks**

* Ad blockers stop it: see [Server-side tracking](/docs/features/ad-blocker-proof-tracking)
* Safari ITP cuts its cookies to 7 days, so a purchase a week after the click loses its campaign
* It only knows revenue: a €100 order at 8% margin counts the same as one at 40%
* Smart Bidding learns from a smaller, skewed set of orders

**Product Metrics instead:** its server-side tracking, **Full Signal Tracking**, gets through every adblocker.

* It runs on a unique endpoint on your own domain.
* It keeps the click ID first-party, with a 30-day cookie.
* It sends each paid order server-side, with its profit and customer type.

See [Server-side tracking](/docs/concepts/server-side-tracking).

## vs Google tag gateway and server-side Google Tag Manager

**What this path is:** Google's own tags, loaded through your domain (Google tag gateway) or relayed by a server-side Google Tag Manager container you host.

**When it is enough**

* You already run a tagging server and have someone to maintain it
* You only need revenue in Google Ads

**Where it breaks**

* Ad blockers also block Google tag gateway and server-side Google Tag Manager setups
* The value is still what the browser reported: no profit, no new or returning customer, no lifetime value, unless you build that pipeline yourself
* You maintain the container, the tags and the hosting

**Product Metrics instead:** server-side tracking gets through. The order is read from your shop, not trusted from the browser. It goes to Google Ads through Google's Data Manager, and to Meta through the Meta Conversions API.

There is no container to host:

* **Shopify, WooCommerce, Magento and Shopware**: the app, plugin or module serves it.
* **Lightspeed**: it runs through a Cloudflare gateway.
* **Any other website**: setup is signing in to Cloudflare.

See [How it works](/docs/concepts/how-it-works).

## vs ProfitMetrics

**What it is:** profit-based conversion values for Google Ads and Meta, plus Shopping Booster labels in Merchant Center.

**When it is enough**

* You spend a lot on ads but have few orders a month: ProfitMetrics charges per order, not on ad spend
* You only need profit conversion values, not product-level analysis

**Where it differs**

* Its Conversion Booster is server-side tracking, but it gets blocked by ad blockers
* Shopping Booster segments products by clicks only

**Product Metrics instead:** both send profit, revenue, new and returning customers and LTV to Google Ads and Meta. Product Metrics also:

* gets through every adblocker
* segments every Shopping and Performance Max product with machine learning on profitability, stock, return rate, potential and price against competitors

You can run both: let one tool send the conversion values, and give each its own Merchant Center custom label.

## vs Producthero

**What it is:** a Comparison Shopping Service (CSS) in the EEA, which Producthero markets as up to 20% lower CPC, and four Labelizer labels (Heroes, Sidekicks, Villains, Zombies) from clicks and ROAS against a target ROAS.

**When it is enough**

* You advertise in the EEA, are still on Google's own CSS, and the saving covers the fee
* Four click-and-ROAS labels fit your account structure

**Where it differs**

* Labelizer runs on the conversions your Google Ads tag reports, and that tag gets blocked
* Producthero's pages state no margin or POAS input

**Product Metrics instead:** segments based on profit, with the reason behind each product's result (price position, stock, margin), and every paid order sent server-side. Product Metrics offers a CSS through a CSS partner.

## vs DataFeedWatch and Channable

**What they are:** feed management. They map, fix and send product data to Google, Meta, marketplaces and other channels, with custom labels set by rules you write.

**When they are enough**

* Your feed has errors, disapprovals or weak titles: fix the data first
* You sell on many channels beyond Google and want one tool for the feeds

**Where they differ**

* DataFeedWatch has no conversion tracking in its plans, and Channable Insights reads the conversions your Google Ads tag reports. That tag gets blocked
* Labels come from rules you write and maintain (DataFeedWatch) or four rule-based segments from clicks and ROAS (Channable Insights)

**Product Metrics instead:** keep your feed tool for the feed. Product Metrics sends every paid order server-side and writes the segmentation labels you approve to Merchant Center directly, so the two don't overlap.

## Decision cheat sheet

| If your job is…                                              | Prefer                                                                             |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
| Revenue-only bidding, and missing orders are acceptable      | The standard Google Ads tag and Meta pixel                                         |
| Every paid order in Google Ads and Meta, through ad blockers | Product Metrics                                                                    |
| Bid on profit, new customers or lifetime value               | Product Metrics                                                                    |
| Profit values with few, large orders                         | ProfitMetrics, or Product Metrics if you also want every order through ad blockers |
| A CSS saving in the EEA                                      | Producthero, with Product Metrics for tracking and segmentation                    |
| Fix and syndicate product feeds to many channels             | DataFeedWatch or Channable, with Product Metrics for tracking and labels           |

## Prove it yourself

1. Run the [quickstart](/docs/quickstart): connect your store and Google Ads, and place a test order
2. Check the order arrived, with its profit and customer type: [Check tracking](/docs/using/check-tracking)
3. Open the [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking) in your own browser with your own blocker
4. Analyse your products for free, with no credit card: log in at [app.productmetrics.io](https://app.productmetrics.io)

## Related



* [What is Product Metrics?](/docs/overview/what-is-product-metrics): the product and what it sends.
* [Server-side tracking](/docs/concepts/server-side-tracking): why server-side tracking gets through ad blockers.
* [Billing and usage](/docs/overview/billing-and-usage): pricing, if cost is part of the decision.
* [Security and privacy](/docs/overview/security-and-privacy): consent, hashing and access.
