Meta sees what matters.

Meta Pixel in the browser and the Conversions API on the server – linked by a shared event ID so each event counts once.

Request a consultation See features

Meta Pixel

PageView
ViewContent
Search
AddToCart
InitiateCheckout
AddPaymentInfo

Features

Pixel and Conversions API with deduplication and hashed advanced matching.

Setup

System user token, queue worker and correct trusted-proxy settings.

Support

Personal support with setup questions and continuous development.

Sent twice. Counted once.

Our tracking extensions report key events such as the purchase along two paths: the pixel in the browser and the platform’s server API. If one path fails – ad blockers, late payment confirmations – the conversion still arrives.

Your shop

ViewContent
InitiateCheckout
Purchase

Browser

Meta Pixel

after consent

Server

Conversions API

Purchase only once paid

One ID, two paths

Browser and server share an ID – the platform recognises duplicates and counts the event once.

Paid first, then reported

The server-side purchase is only sent once the order is paid – including invoice, prepayment or late-confirmed PayPal.

Hashed, never plain

Email, phone and name are SHA-256 hashed on your server. Raw personal data never leaves the shop.

What the extension does

Tracked events

PageView
ViewContent
Search
AddToCart
InitiateCheckout
AddPaymentInfo
Purchase
CompleteRegistration

Meta Pixel in the browser plus the server-side Conversions API (CAPI).
Shared event ID – Meta counts each event only once.
Server-side Purchase once the order is paid.
Advanced matching (email, phone, name, address) SHA-256 hashed on the server.
Limited Data Use flag for US traffic (CCPA/CPRA).
Gated on marketing consent, with a noscript fallback and test event code.

Requirements & setup

Shopware 6.6 or 6.7, PHP 8.2+, configured per sales channel.
A Meta system user access token.
A running queue worker for server events.
Correct trusted-proxy settings for good match quality.

Status: Compatibility declared for Shopware 6.6 and 6.7. Availability on request.

Good to know

Honest limits – so you know exactly what you can rely on.

AddToCart is currently not deduplicated.
Full-page caching on product pages weakens ViewContent deduplication.
Unpaid orders keep their attribution for at most 7 days.

Works with the Consent Manager

Meta Pixel only loads after “Marketing” consent. Together with the Consent Manager, your shop gets an equally prominent “reject all” and blocks scripts reliably until consent is given.

See the Consent Manager

Questions about Meta Pixel

Question not listed? Free consultation

Does Meta count events twice?

No – the Pixel and Conversions API share an event ID, so Meta recognises duplicates. The one current exception: AddToCart is not deduplicated yet.

What do I need for the Conversions API?

A Meta system user access token, a running queue worker and correct trusted-proxy settings. Without the latter, match quality drops without any warning.

What is the Limited Data Use flag?

A Meta setting for US traffic under CCPA/CPRA. The extension can set it for affected visitors.