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

# Shopware server-side tracking with the Meta Conversions API (/docs/tracking/server-side/shopware-meta)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1954 · updated: 2026-11-16 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Magento server-side tracking for Google Ads](/docs/tracking/server-side/magento-google-ads.md), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md)

> Send every purchase from your Shopware sales channel to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.

Each purchase is confirmed from **your Shopware orders** and sent to your Meta pixel [from the server](/docs/concepts/server-side-tracking), through the **Meta Conversions API**. Nothing in the browser talks to Meta, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/shopware-meta).

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking).
* **Your Shopware sales channel connected**: Shopware 6.7 (this plugin build supports 6.7.14.0) with PHP 8.2+, an administrator who can upload extensions, Shopware's scheduled tasks and message workers running, and the channel's public HTTPS address under **Sales Channels → your channel → Domains**. You pair one sales channel with a one-time token; it reads **Active** before you link your property. See [Shopware](/docs/platforms/shopware).
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## 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 server-side conversion tracking for my Shopware store in Meta with Product Metrics. 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 server-side conversion tracking for my Shopware store in Meta with Product Metrics. 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), and tell me when a step needs me in a browser."

## In the app

### 1. Connect Shopware and Meta

* **Store:** install the Product Metrics plugin and pair your sales channel with a one-time token and link it to your property. See [Shopware](/docs/platforms/shopware).
* **Meta:** in Events Manager, copy your **Pixel or Dataset ID** and generate a Conversions API access token, then add both under **Tracking → Meta Conversions API → Connect Meta** and send a test event. See [Meta](/docs/channels/meta).



![The Add Meta destination form with Pixel or Dataset ID, Access token, Test event code (optional) and the Send events to Meta switch, then the saved Meta Conversions API destination showing Active, the access token Accepted by Meta and Sending On.](/docs/_assets/b8f3701ffab8399a9aad9788c63abe4161115d01a029732731a74012315454bb)

*Figure: Add Meta destination: paste the Pixel or Dataset ID and access token, keep Send events to Meta on.*

**You should see:** in Product Metrics, the store reads **Active** after **Verify connection**; Events Manager shows the test event under **Test events**.

### 2. Choose your consent banner

Using Shopware's own cookie manager? Leave **Tracking → Configure consent** on **Not configured**: the extension adds a **Product Metrics measurement** group with **Product Metrics analytics** and **Product Metrics advertising attribution**. Choose OneTrust, Cookiebot, Usercentrics or Osano only if your shop shows one of those banners instead. See [Consent](/docs/concepts/consent).



> **Warning:** Meta has no consent mode. Product Metrics sends an event only when the visitor allowed ad user data; the custom events also need analytics consent. A wrong banner here means nothing reaches Meta.

**You should see:** **Configure consent** names the banner your sales channel actually shows.

### 3. Create custom conversions

In Events Manager, create a custom conversion for each Product Metrics value you want to bid on, with the rule `pm_purpose` equals the purpose: `PMOrderRevenue` (`ORDER_REVENUE`) for revenue, `PMOrderProfit` (`ORDER_PROFIT`) for profit, every other event in [Meta events](/docs/concepts/conversion-actions-and-events#meta-events). Follow [Create custom conversions in Meta](/docs/using/conversion-actions#custom-conversions-in-meta) once a test order has reached Meta.

**You should see:** your custom conversions show in Events Manager.

### 4. Check it works

**Place a paid test order** through the paired sales channel with your payment provider's test mode, and give Shopware a few minutes to sync it.

**You should see:** your cookie banner lists **Product Metrics measurement** (with Shopware's own cookie manager); in Events Manager, the order shows as `Purchase`, plus the Product Metrics custom events your visitor's consent allows. More checks: [Check tracking works](/docs/using/check-tracking).



**How it works on Shopware**

* **Script and collector served by:** The Shopware extension, on a path generated for your sales channel (`/<random>/c/<token>`). No Cloudflare step, no script tag; one installation tracks one sales channel
* **Purchase confirmed from:** Your Shopware orders
* **Sent:** When the order from the paired sales channel is paid
* **Delivered:** Server-side, through the Meta Conversions API: `Purchase` plus the Product Metrics custom events
* **Refunds and cancellations:** Sent events aren't revised. Meta refuses events more than 7 days old
* **Consent read from:** Shopware's own cookie manager, or OneTrust, Cookiebot, Usercentrics or Osano

## Troubleshooting

### The event isn't in Meta's custom conversion selector

Meta lists an event only after it received it. Place a test order with all cookies accepted, then create the custom conversion.

### Nothing reaches Meta

Check that **Tracking → Configure consent** names the banner your store shows, or reads **Not configured** if it uses Shopware's own cookie manager.

## FAQ

### Can I keep the Meta pixel on Shopware?

Yes. Meta counts an event once when the pixel and the Meta Conversions API send the same event name and event ID within 48 hours. `Purchase` uses the order transaction ID, so it deduplicates on its own.

### Which Shopware sales channel is sent to Meta?

Only the one paired with the extension: one installation tracks one sales channel, and its paid orders go to Meta.

### Are past Shopware orders sent to Meta?

No. Meta refuses events more than 7 days old, so only orders paid after tracking is live are sent.

### What customer data does Advanced Matching send to Meta?

With marketing consent, each event carries the hashed email, name, postal code and country, plus IP address and browser, through the Meta Conversions API. See [Meta Conversions API on Shopware](/docs/tracking/enhanced-conversions/shopware-meta).

## Where next

* [Shopware](/docs/platforms/shopware): the full platform setup
* [Meta](/docs/channels/meta): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for Shopware in Google Ads](/docs/tracking/server-side/shopware-google-ads): the same sales channel, the other channel
* [Meta Conversions API on Shopware](/docs/tracking/enhanced-conversions/shopware-meta): the customer data each event carries
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [Product Metrics for Shopware](https://www.productmetrics.io/platforms/shopware)

Developers: do the same with the [CLI](/docs/cli/commands#destinations) or the [API](/docs/api/destinations/set-meta).
