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

# Server-side tracking (/docs/concepts/server-side-tracking)

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

> How server-side tracking runs on your own domain, and why ad blockers and Safari ITP don't hide your conversions.

**Server-side, adblocker-proof conversion tracking: Full Signal Tracking gets through every adblocker, and auto-rotates its endpoint if it is ever blocked.**

Two halves work together:

* **In the browser**, the tracking script runs on a unique endpoint on your store's own domain. It records the visit, the ad click and consent.
* **On the server**, Product Metrics confirms the order from your shop's own data and sends it to Google Ads, Meta and ChatGPT Ads.

The full pipeline is [How it works](/docs/concepts/how-it-works).



![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.*

## Standard tags vs server-side tracking

|                       | **Standard Google Ads tag / Meta pixel**    | **Product Metrics**                   |
| --------------------- | ------------------------------------------- | ------------------------------------- |
| **Runs on**           | A tracking domain blockers list             | A unique endpoint on your own domain  |
| **Sends conversions** | From the visitor's browser                  | From the Product Metrics server       |
| **The order**         | Whatever the browser reports                | Confirmed from your shop's order data |
| **Ad blockers**       | Blocked by uBlock Origin, Brave and AdGuard | Gets through every adblocker          |
| **Safari ITP**        | Cookies cut to 7 days                       | Same-origin cookie lasts 30 days      |
| **If blocked**        | Lost                                        | Auto-rotates to a fresh endpoint      |

## Try it

**Ask your assistant:** "Where does Product Metrics collect tracking on my store, and is delivery healthy?"

You should see one URL per installation, such as `https://shop.example.com/<unique-path>`. The host is your own store domain. The path is unique to your installation.

## Rules

1. **Your own domain.** The endpoint lives on your store's domain. Where it runs on each platform is in [Per platform](#per-platform).
2. **Auto-rotation.** If the endpoint is ever blocked, it auto-rotates to a fresh one.
3. **The shop confirms the order.** The browser links the visit to the order; the order itself comes from your shop's data.
4. **Consent first.** Getting through ad blockers never overrides a visitor's consent choice. See [Consent](/docs/concepts/consent).
5. **No tag to place.** There is no Google tag or pixel to add. Your existing tags can keep running next to it.

## Why it matters for bidding

Smart bidding learns only from the conversions it receives. Product Metrics sends conversions from a first-party endpoint, so it improves match rates and preserves click IDs.

```text
Visitor with uBlock Origin buys €108.00
  Standard Google Ads tag   → blocked, Google Ads never sees the sale
  Product Metrics           → gclid kept on your domain
                            → order confirmed from the shop
                            → Product Metrics - Revenue 108.00,
                              Profit 48.46 reach Google Ads
```

## What ad blockers do

We tested this in real browsers with real extensions on 30 September 2026. Product Metrics reached its endpoint in every run.

| Blocker            | Standard Google Ads tag | Google Ads conversion | Meta pixel            | Product Metrics                  |
| ------------------ | ----------------------- | --------------------- | --------------------- | -------------------------------- |
| uBlock Origin      | Blocked                 | Blocked               | Blocked               | Gets through                     |
| AdBlock            | Gets through            | Gets through          | Blocked               | Gets through                     |
| Brave              | Blocked                 | Blocked               | Blocked               | Gets through                     |
| AdGuard            | Blocked                 | Blocked               | Blocked               | Gets through                     |
| VPN / DNS blocking | Gets through            | Partly blocked        | Gets through          | Gets through                     |
| Safari ITP         | Cookies cut to 7 days   | Cookies cut to 7 days | Cookies cut to 7 days | First-party cookie lasts 30 days |

Ad blockers also block Google tag gateway and server-side Google Tag Manager setups; Product Metrics gets through.

See the full results in the [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking).

## Per platform

| Platform                                          | Where the tracking runs                                      |
| ------------------------------------------------- | ------------------------------------------------------------ |
| [Shopify](/docs/platforms/shopify)                     | Shopify's app proxy, under `/apps/` on your store domain     |
| [WooCommerce](/docs/platforms/woocommerce)             | The Product Metrics plugin, on your own WordPress domain     |
| [Magento](/docs/platforms/magento)                     | Random paths on your own domain, served by the module        |
| [Lightspeed](/docs/platforms/lightspeed)               | Cloudflare on your shop domain, approved once                |
| [Shopware](/docs/platforms/shopware)                   | A random path on your Shopware domain, served by the plugin  |
| [Any website (Cloudflare)](/docs/platforms/cloudflare) | Cloudflare on your domain: setup is signing in to Cloudflare |

Server-side tracking is included in the Product Metrics Pro subscription.

## Where next



* [Server-side tracking feature](/docs/features/ad-blocker-proof-tracking): every platform and channel, step by step
* [Conversion values](/docs/concepts/conversion-values): what is sent per order
* [Consent](/docs/concepts/consent): the consent signals, and what each one lets through
* [Ad blocker test results](https://www.productmetrics.io/ad-blocker-conversion-tracking): the ad blocker conversion tracking check, run in real browsers
