Facebook Pixel (Meta Pixel) | Tracking & Conversions API

by Markus Michalski

Rating: no rating ( write a review )

Downloads: <10

Facebook Pixel (Meta Pixel) for Shopware 6.7 with full e-commerce events, server-side Conversions API (CAPI), event deduplication, and GDPR-compliant Klaro Consent integration.

Annually €3.40* /month €48.00 * €40.80* /year 15% discount In comparison to the regular monthly price

Monthly €4.00* /month Cancelable monthly

Compatible with:

6.7.0.0 - 6.7.10.2

Includes:

Free trial month

The subscription starts with a free trial month during which it can be canceled at any time.

All updates

During the subscription all released updates are included for free

Support from the Extension Partner

In case you have any questions or problems with your extension you can always ask the Extension Partner for help during the subscription.

Description

Highlights

- Full e-commerce tracking: PageView, ViewContent, AddToCart, Checkout & Purchase
- Meta Conversions API (CAPI) — server-side tracking for better data quality
- GDPR-compliant with Klaro Consent Manager integration and cookie consent check
- Async CAPI processing via Symfony Messenger — zero performance impact
- Multi-Sales-Channel with separate configuration per channel

Features

- PageView tracking on all storefront pages
- ViewContent event on product detail pages with product data
- ViewCategory event on category pages (custom event)
- AddToCart event when products are added to cart
- InitiateCheckout event on checkout confirmation page

- Purchase event on order completion with full order data
- Meta Conversions API (CAPI) — server-side event tracking
- Automatic event deduplication between client and server via event_id
- Async CAPI processing via Symfony Messenger
- SHA-256 PII hashing for GDPR-compliant data transfer (CAPI)
- Klaro Consent Manager integration for GDPR-compliant tracking
- Built-in cookie consent check as alternative to Klaro
- Gross/net price configuration for B2C and B2B
- Granular event control — toggle each event individually
- Multi-Sales-Channel with separate configuration per channel

Show more Show less

About the Extension

Why this plugin?

Running Meta Ads (Facebook/Instagram) requires reliable conversion tracking. Ad blockers, iOS restrictions, and browser limitations mean client-side tracking alone is no longer enough. This plugin implements Meta's recommended Redundant Setup: client-side Pixel plus server-side Conversions API — for maximum data quality and better ad attribution.

Core Features

PageView — Automatic tracking on all storefront pages
ViewContent — Product detail pages with product ID, name, price, and currency
ViewCategory — Category page tracking (custom event)
AddToCart — Event when products are added to cart
InitiateCheckout — Checkout confirmation page
Purchase — Order completion with order value, product IDs, and item count
Meta Conversions API (CAPI) — Server-side tracking alongside client-side Pixel
Event Deduplication — Automatic deduplication via event_id between client and server
Gross/Net Prices — Configurable for B2C and B2B shops
Granular Event Control — Enable or disable each event individually

How it works

After installation, simply configure your Pixel ID and enable tracking. Optionally, activate the Conversions API — you'll need an Access Token from Meta Events Manager. CAPI events are processed asynchronously via Symfony Messenger and do not affect page load times.

For GDPR compliance, two options are available: The built-in cookie consent check or Klaro Consent Manager integration (requires MmdKlaroConsent plugin). Tracking only starts after explicit user consent.

Requirements

Shopware 6.7.x
PHP 8.2 or higher
Facebook Pixel ID (from Meta Events Manager)
For CAPI: Access Token from Meta Events Manager
For CAPI: Running Symfony Messenger consumer (bin/console messenger:consume async)
Optional: MmdKlaroConsent plugin for Klaro Consent integration

Use Cases

Meta Ads Retargeting — Re-engage visitors with dynamic product ads
Conversion Tracking — Measure purchases, cart additions, and checkout starts
Custom Audiences — Build audiences based on shop interactions
Lookalike Audiences — Find new customers similar to your best buyers
ROAS Optimization — Improve ad performance with complete conversion data
iOS 14+ Compliance — Server-side events supplement limited browser tracking

Important Notes

Facebook Pixel sends data to Meta (Facebook). This must be disclosed in your privacy policy and cookie consent banner. I strongly recommend using the Klaro integration or the built-in consent check for GDPR compliance.

The Conversions API requires a running Symfony Messenger consumer. For production, this should be managed via Supervisor or systemd.

Documentation: Full documentation in the Wiki

Details

Available: English, German
Latest update: 1 June 2026
Publication date: 5 June 2026
Version: 1.2.0
Category: Social Commerce

Resources

Reviews (0)

Write a review

If you downloaded this extension you can write a review in the Shopware Account.

Write a review

No reviews found.

About the Extension Partner

Markus Michalski

See all extensions

Partner Status

Shopware
Extension Partner

Details

Partner since: 2026
Extensions: 3

Support

Based in: Germany
Speaks: German, English
Response time: Very quickly

German

Frontend:: Go to demo

Admin:: Go to demo
Name:: admin
Password:: shopware

1.2.0 30 April 2026

## [1.2.0] - 2026-04-30

### Added

- add API connection test button

### Fixed

- remove all plugin data on uninstall with delete all data

1.1.0 20 March 2026

## [1.1.0] - 2026-03-20

### Added
- auto-create Klaro service on plugin activate

## [1.0.2] - 2026-02-25

### Added
- add meta conversions api (capi) server-side event tracking
- implement Facebook Pixel tracking with CAPI-ready architecture

### Changed
- add GitHub Actions workflow for tests, coverage, and static analysis
- clean up CHANGELOG.md placeholder entries
- add CLAUDE.md to .gitignore
- prepared first release
- consolidate changelog for unreleased v1.0.0
- add README, commercial license, and license headers to test files
- add plugin icon (SVG + PNG) and update .gitignore
- update .gitignore to include additional cache and temporary files
- add CHANGELOG.md for v1.0.0 release
- add initial changelog file
- initial project setup

### Fixed
- clean up changelog by removing empty sections for v1.0.1
- use correct shopware config.xml option format for multi-select
- send client_ip_address and client_user_agent unhashed in CAPI
- make capi messages async via shopware message queue

### Security
- implement all findings from security audit 2026-02-20

## [1.0.1] - 2026-02-11

### Fixed
- use correct shopware config.xml option format for multi-select
- send client_ip_address and client_user_agent unhashed in CAPI

## [1.0.0] - 2026-02-11

### Added
- add meta conversions api (capi) server-side event tracking
- implement Facebook Pixel tracking with CAPI-ready architecture

### Changed
- prepared first release
- consolidate changelog for unreleased v1.0.0
- add README, commercial license, and license headers to test files
- add plugin icon (SVG + PNG) and update .gitignore
- update .gitignore to include additional cache and temporary files
- add CHANGELOG.md for v1.0.0 release
- add initial changelog file
- initial project setup

### Fixed
- make capi messages async via shopware message queue

### Added
- Facebook Pixel (Meta Pixel) base code injection with `fbq('init')` and `PageView` tracking
- `ViewContent` event on product detail pages (content_name, content_ids, value, currency)
- `ViewCategory` custom event on category/navigation pages (content_name, content_category)
- `AddToCart` event on cart page for all product line items
- `InitiateCheckout` event on checkout confirmation page
- `Purchase` event on order completion (content_ids, value, num_items, order_id)
- Configurable per sales channel (Pixel ID, 6 individual tracking toggles)
- Gross/net price toggle for B2B shops
- Klaro Consent Manager integration (`type="text/plain"` + `data-name` pattern)
- Migration creates Klaro cookie service entry (purpose: marketing, cookies: _fbp, _fbc, fr)
- ConsentChecker with marketing consent group support
- Plugin configuration with 3 cards (Pixel Options, Tracking Options, Klaro Integration)
- German and English translations for config labels
- Meta Conversions API (CAPI) server-side event tracking (redundant setup with event_id deduplication)
- Async CAPI dispatch via Symfony Messenger (`AsyncMessageInterface`)
- GDPR-compliant PII hashing (SHA-256) for email, phone, IP, user-agent
- Per-event CAPI selection (choose which events to send server-side)
- Test Event Code support for debugging in Meta Events Manager
- CAPI configuration card (capiEnabled, capiAccessToken, capiTestEventCode, capiEventSelection)
- Customer email and phone extraction for Purchase and InitiateCheckout events

### Technical
- CAPI architecture: Event Value Objects with `PixelEventRendererInterface`
- `event_id` (UUID) per event for Conversions API deduplication
- Central `EventDataExtractor` for all Shopware entity-to-event conversions
- `PixelJsRenderer` as swappable v1 renderer
- `PixelEventDispatched` internal event bridging subscribers to CAPI system
- `ConversionsApiClient` for `graph.facebook.com/v21.0` with fire-and-forget error handling
- `PiiHasher` with SHA-256 hashing for all PII fields
- `ServerEventContext` / `ServerEventContextFactory` for request context capture
- `SendCapiEventMessage` / `SendCapiEventHandler` for async message queue processing
- `CapiEventListener` for routing events to message queue with independent consent handling
- 139 unit tests, 369 assertions, PHPStan Level 8
- Strict types, `final readonly class` throughout

### Security
- Pixel ID validation: `ctype_digit()` only (no arbitrary strings)
- XSS prevention: `json_encode()` with `JSON_HEX_TAG | JSON_HEX_APOS | JSON_HEX_QUOT | JSON_HEX_AMP`
- No user input rendered directly in JavaScript
- HTTPS-only for `connect.facebook.net`
- Consent allowlist with explicit value validation
- PII never logged in plain text (CAPI error logs exclude response body)
- Access Token only used server-side, never exposed to client