Shopware 6 conversion tracking usually starts the same way. Someone adds a Meta pixel through a theme template or a plugin, orders start coming in, and a few weeks later the ad account shows fewer purchases than the Shopware admin. The cookie banner, browser privacy features and ad blockers all sit between the shopper and the pixel.
This guide explains what goes wrong with a browser-only setup on Shopware, how server-side tracking works for a Shopware 6 shop, how to set it up with SyncBeacon, and where the limits are. It is written for shop owners and agencies in DACH and the wider EU, but the mechanics apply anywhere.
What goes wrong with a Shopware Meta Pixel
A Shopware Meta Pixel is a script in the shopper's browser. It can be added in the theme, through a plugin or through a tag manager. In each case it has to survive the same conditions:
- Cookie consent. Shopware has its own cookie consent in the storefront. A marketing pixel should only run after the visitor accepts the matching cookie group. Declined visitors never fire it, so their purchases never reach Meta.
- Ad blockers and browser privacy. Blockers stop requests to known ad endpoints. Safari and other browsers limit how long script-written storage lives.
- The order-confirmation page. If the pixel fires only there, the purchase depends on the shopper landing on that page and the page loading fully.
None of this is a Shopware bug. It is the cost of reporting a sale from a place you do not control. Server-side tracking reports it from the order instead.
How server-side Shopware tracking works
Shopware tracking with SyncBeacon uses two parts, and they do different jobs.
| Part | What it does | Notes |
|---|---|---|
| Admin API order sync | SyncBeacon reads Shopware orders through the Admin API with an integration key and forwards purchases and cancellations. | Polling runs about every 2 minutes. |
| SyncBeacon storefront app | A free app loads the SyncBeacon browser script for PageView, ViewContent, AddToCart and InitiateCheckout. | Purchases do not come from the app. Behaviour depends on your theme. |
Cancelled, returned and refunded orders are forwarded as cancellations. That is a record of what happened. It does not mean ad platforms will show refund-adjusted numbers.
Instant webhooks are optional
If you want orders pushed to SyncBeacon the moment they happen instead of polled, Shopware's Flow Builder can call a URL. That "Call URL" action is only available in Shopware Commercial Evolve and Beyond, not in Community or Rise. Authentication for this path is an X-Shopware-Secret header, not an HMAC signature. If you are on a plan without it, polling covers you.
Which events come from where
| Event | Source | Depends on the browser? |
|---|---|---|
| Purchase | Admin API order sync (or Flow Builder webhook) | No |
| Cancellation, return, refund | Admin API order sync | No |
| PageView, ViewContent, AddToCart, InitiateCheckout | Storefront app and browser script | Yes, and it follows consent |
This split is the main design point. The events that carry revenue do not wait for a page to load in a browser. The events that describe browsing behaviour still do, because that is where the behaviour happens.
What to do with your existing pixel
You do not have to remove it on day one. A sensible order is to connect Shopware, confirm purchases arrive in the Conversions page, and then decide. If you keep a separate browser pixel for the same purchase, Meta only deduplicates when the pixel's event ID matches the server event ID. SyncBeacon merges its own browser and server events, but it cannot change the ID that a different pixel sends. If you cannot match the IDs, remove the duplicate source and check Events Manager for double counting.
Setup, step by step
The app is documented for Shopware 6.5, 6.6 and 6.7, on Shopware Cloud and self-hosted shops.
1. Install the storefront app
Download the app ZIP from your SyncBeacon dashboard and upload it in Shopware under Extensions > My extensions, then install and activate it. On a self-hosted shop you can also copy the app folder into custom/apps and run the usual app install commands.
2. Create a Shopware integration
In Settings > System > Integrations, add an integration named SyncBeacon with Administrator access. Copy the Access Key ID and the Secret Access Key. The secret is shown once.
3. Connect Shopware in SyncBeacon
Open Integrations in SyncBeacon, choose Shopware, and enter your shop URL and the two keys. This is a Shopware integration key, not an OAuth login. Then click Repair on the Shopware card. Repair writes your public tracking key into the app configuration.
4. Choose a plan and connect destinations
Pick a plan in billing. The Pilot is free for 14 days with no card and connects one ad platform. Then connect your destinations, for example Meta Conversions API or Google Ads. See the Shopware server-side tracking page for the platform overview.
Verify the setup
- Open your storefront (not the admin), view the page source and search for
sb.js. - Place a test order. Within a few minutes a purchase should appear in the SyncBeacon Conversions page.
- Check the delivery result for each connected destination and any forwarding errors. Failed deliveries retry automatically, up to 24 attempts per destination. Permanent errors such as bad credentials stop at once.
- In Meta Events Manager, confirm the purchase arrived as a server event.
Consent on a Shopware shop
SyncBeacon checks consent before it forwards anything. The browser tracker detects consent from Cookiebot, OneTrust, IAB TCF v2 strings and a manual window.SyncBeaconConsent override. Shopware's built-in cookie consent is not detected automatically, so if you rely on it, use the manual override to pass the visitor's choice.
- If a visitor explicitly denies marketing consent, SyncBeacon keeps the event for your records but does not forward it to ad platforms.
- Without any banner signal, the consent setting in your SyncBeacon account decides whether identifiers are used. Missing marketing consent strips identifiers, and some destinations then skip the event.
- Email and phone are SHA-256 hashed before events are stored or sent.
For the wider picture, see GDPR-ready tracking. SyncBeacon runs on infrastructure hosted in Germany. That does not remove your duties as controller, and ad platforms process data under their own terms.
Limits worth knowing
- Polling means a purchase can reach SyncBeacon a couple of minutes after the order. Add queueing and the ad platform's own processing time before it appears in reports.
- Browser events from the app depend on your theme. Check them on your own storefront before you rely on them.
- The app is installed from a ZIP in the SyncBeacon dashboard. It is not listed in the Shopware Store.
- Stock-based ad pause on Shopware uses a catalogue import with a daily refresh plus manual reload, not a live stock feed. Details are on the out-of-stock ad pause page.
- Platform numbers will still differ from the Shopware admin because of attribution windows and declined consent. See why Meta shows fewer conversions than your store. The same reasoning applies to Shopware.
Related reading
- Shopware server-side tracking
- How server-side conversion tracking works
- SyncBeacon vs Google Tag Manager for GDPR
- Ecommerce conversion tracking overview
Get started
Close your conversion gap today
Connect Meta CAPI, Google Enhanced Conversions, and more - in one setup, no developer required.
Shopware editions, features and admin menus change between versions. Check Shopware's current documentation for your version. Consent obligations depend on your jurisdiction; this post is not legal advice.