The pixel needs a page the checkout may skip
A redirect payment can place the order while the customer is elsewhere. No finish page, no pixel event, and a real sale that Events Manager never records.
Shopware 6 plugin + Meta Conversions API, EU-hosted
Meta Conversions API for Shopware 6
A Shopware 6 plugin that sends the placed order to the Meta Conversions API from your server, sharing an event_id with the Storefront pixel so Meta merges the two. It hooks the order lifecycle rather than the finish page, and it rebuilds the click cookie from the fbclid when the pixel never wrote one.
The problem
Why Meta misses Shopware orders
The Meta pixel lives in the Storefront. The order lives in the order lifecycle. When the two part ways, the sale is the thing that goes missing.
A second integration counts the same sale twice
Adding a Conversions API call without sharing an event_id with the pixel makes Meta record two purchases. The reported figures rise and stop meaning anything.
Consent handled twice, or not at all
Two integrations with two ideas of consent produce either events that should not have left, or events that should have and did not. Both are hard to notice until an audit.
The fix
One event id, one consent gate, one order
The plugin sends the browser event and the server event with the same event_id, both gated on a single shared consent check, and the server one fires when Shopware places the order.
Deduplicated on the Shopware order
Both paths carry the same event_id derived from the order, so Meta merges them and keeps the more complete one. The purchase counts once.
One consent gate for both layers
The Storefront layer and the server layer read the same consent state, so the two can never disagree about whether an event was allowed to leave.
Click cookie rebuilt when missing
The plugin stores its own copy of the click id from the fbclid, so a store without a pixel, or a browser that dropped the cookie, still sends a usable _fbc with the purchase.
Setup
Three steps, and Meta CAPI starts receiving
-
Install the connector
A plugin uploaded in the Shopware administration, Extensions, then activated. Assets install themselves; the Storefront needs no template edit.
-
Paste your connection key
One key from your DataFirefly console identifies the site. It is the only thing your shop holds: no destination credential ever lives in your store.
-
Add Meta CAPI as a destination
Your Meta CAPI settings go into the console, stored encrypted on our side. Rotating them later touches nothing in the shop.
The same connector feeds every other destination from the same events, so Meta CAPI is a starting point rather than a silo. See the Shopware 6 connector in detail or the Meta Conversions API across all platforms.
Same connector
Your other destinations from Shopware 6
One installation, one key. The events you already send reach every destination you switch on.
Pricing
Included in every plan, free plan included
10,000 events a month free, no card. Paid plans from 39 €/month when your volume grows. Every destination is included in every plan: Meta CAPI is never an add-on.
FAQ
Frequently asked questions: Shopware 6 and Meta CAPI
Will the purchase be counted twice in Meta?
No, as long as both events share an event_id, and the plugin makes sure they do: the Storefront event and the server event are derived from the same Shopware order. Meta deduplicates them and keeps the richer one.
Which Shopware versions are supported?
Shopware 6.5 and 6.6. The plugin is uploaded in the administration under Extensions and activated; the Storefront needs no template change.
What happens if the finish page never renders?
The server event is bound to the order being placed, not to a page. A redirect payment that ends with a closed tab still produces a purchase in the Conversions API.
How is consent handled?
Both layers read the same consent state through a shared gate, and the dispatcher checks again before anything leaves for Meta. The plugin also declares its cookies in the Shopware consent registry, so the banner lists them.
Does it improve Event Match Quality?
Yes, because the placed order carries hashed email and phone that a Storefront event usually lacks, plus _fbp and an _fbc rebuilt from the fbclid. Hashing happens on your side before anything is sent.
Where does the Meta access token live?
Encrypted on our side. Your Shopware configuration holds only the connection key, so you can revoke access from the console without touching the plugin.
Send Meta the Shopware orders the pixel never saw
Install the plugin, paste one key, connect your pixel and access token. Orders placed away from the Storefront still reach Meta, deduplicated.