Contact

Meta Pixel & Conversion API Integration

< 10 downloads
Easy integration of Meta Pixel and the Conversion API for reliable tracking of shop events and optimisation of marketing campaigns through server-side and browser-side tracking.
Monthly
€9.99* / month
Cancelable monthly
Annual
16.67% discount
€8.33 / month
€119.88* €99.90* / year
Go to Shopware Store

Technical Information

Category Tracking, Evaluation & Analysis
Created At April 7, 2026
Last Updated July 18, 2026
Languages de_DE, en_GB
Keywords meta pixel, Meta Conversions API, conversion tracking, Tracking, Facebook Pixel
Technical name AcrisMetaPixel

Highlights

  • Easy integration of Meta Pixel and Conversion API
  • Automatic tracking of key shop events
  • Combined server-side and browser-side tracking
  • Debugging and testing functions for easy setup

Features

  • Integration of the Meta Pixel via Pixel ID directly in the admin panel
  • Server-side tracking via the Meta Conversion API
  • Parallel client and server tracking for higher data quality
  • Automatic tracking of standard events (e.g. PageView, AddToCart, Purchase)
  • Transmission of relevant shop data such as product, shopping basket and orders
  • Combination of client and server tracking for higher data quality
  • Debug mode for checking event transmission

Purpose of the plugin

This plugin enables simple and centralised integration of the Meta Pixel and the Meta Conversion API directly within the Shopware admin panel. This allows important shop events to be reliably tracked and used for analysis and marketing purposes.

Automatic tracking of shop events
Relevant events such as page views, product views, shopping basket interactions and orders are automatically recorded and sent to Meta. This enables precise analysis of user behaviour and the optimisation of campaigns.

Combination of Pixel and Conversion API
By combining browser-side tracking (Meta Pixel) and server-side tracking (Conversion API), significantly higher data quality is achieved. Events can be recorded more reliably, even when tracking is restricted by browsers or ad blockers.

Easy configuration and testing options
Set-up is carried out directly in the admin area by entering the Meta Pixel ID and the access token for the Conversion API. Debugging and testing functions are also available to verify that data is being transmitted correctly.

Installation

  • Open the Plugin Manager via Settings > System > Plugins
  • Upload, install and activate the plugin

Plugin Configuration

Extensions > My Extensions > Meta Pixel & Conversion API > Configure

  1. Sales Channel
    Select the sales channels for which tracking should be enabled
  2. Active
    Enables tracking
  3. Meta Pixel ID
    Enter the pixel ID from Meta Events Manager
  4. Conversion API access token
    Enter the token for server-side event transmission.
    (Meta Events Manager > Select Pixel > Settings > Conversion API > Set up manually > Generate access key)
  5. Debug mode
    Enables additional output to verify event transmission
  6. Test event code
    Enter a test code from the Meta Events Manager to validate the events

Frequently Asked Questions

Es wurden keine Fragen gefunden. Kontaktieren Sie uns, wenn Sie konkrete Fragen haben!
Version Date Compatibility Changelog
2.2.1 11 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Improved admin.
2.2.0 11 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Added a "Test Conversion API access token" button to the plugin configuration. It verifies the entered access token and Pixel ID directly against the Meta Graph API — including values that have not been saved yet.
  • - Fixed event deduplication IDs: ViewContent, Search and InitiateCheckout now use a unique event ID per page view, so repeated product views, searches and checkout starts within a session are no longer dropped by Meta's deduplication.
2.1.0 5 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Added sk-SK and sl-SI translations for snippet files, config.xml and composer.json.
  • - Fixed pixel rendering when plugin is not yet configured (active check).
  • - Fixed cookie consent to block tracking by default when consent framework is absent.
  • - Added event_id deduplication between browser pixel and Conversion API.
  • - Fixed billing address in checkout confirm to use the active address instead of the default.
  • - Fixed inconsistent content_ids identifier across CAPI events.
  • - Added value field to AddToCart CAPI event.
  • - Fixed null value handling in ViewContent CAPI event.
  • - Added connect_timeout to Guzzle client.
  • - Added shopware/storefront to composer.json require block.
2.0.4 19 April 2026 >=6.7.0.0 < 6.8.0.0
  • - Aligned plugin namespace with Acris naming convention.
2.0.3 17 April 2026 >=6.7.0.0 < 6.8.0.0
  • - Completed manufacturerLink and supportLink with all required language entries (including de-DE).
  • - Fixed composer.json schema compliance for Shopware Community Store review.
2.0.2 1 April 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed cookie consent integration to use CookieProviderInterface decorator pattern compatible with all Shopware 6.7.x versions.
1.1.0 11 June 2026 >=6.6.0.0 <6.7.0.0
  • - Added sk-SK and sl-SI translations for snippet files, config.xml and composer.json.
  • - Fixed pixel rendering when plugin is not yet configured (active check).
  • - Fixed cookie consent to block tracking by default when consent framework is absent.
  • - Added event_id deduplication between browser pixel and Conversion API.
  • - Fixed billing address in checkout confirm to use the active address instead of the default.
  • - Fixed inconsistent content_ids identifier across CAPI events.
  • - Added value field to AddToCart CAPI event.
  • - Fixed null value handling in ViewContent CAPI event.
  • - Added connect_timeout to Guzzle client.
  • - Added shopware/storefront to composer.json require block.
1.0.3 19 April 2026 >=6.6.0.0 <6.7.0.0
  • - Aligned plugin namespace with Acris naming convention.
1.0.2 17 April 2026 >=6.6.0.0 <6.7.0.0
  • - Completed manufacturerLink and supportLink with all required language entries (including de-DE).
  • - Fixed composer.json schema compliance for Shopware Community Store review.
1.0.1 1 April 2026 >=6.6.0.0 <6.7.0.0
  • - Set Shopware 6.6 minimum and maximum version constraints.
Reviews
Leave a review!

Share your experiences with other customers and leave a review via your Shopware account.

Write review