# Install the Shopware plugin

> Install and configure the DataFirefly Server-Side plugin on Shopware 6.5, 6.6 and 6.7: extension upload, connection key, consent cookie, CLI test.

- Original page: https://server-side.datafirefly.com/en/docs/shopware.html
- Language: en
- Updated: 2026-09-05
- Publisher: DataFirefly (Datafirefly Limited), https://server-side.datafirefly.com/en/

---

Compatible with Shopware 6.5, 6.6 and 6.7. Installed through the admin or the command line. A failed delivery is queued and replayed every five minutes by Shopware's own scheduler, so a passing outage costs nothing.

## Requirements

- Shopware 6.5, 6.6 or 6.7.
- The plugin zip, downloaded from the [**Modules**](https://admin.datafirefly.com/app/connectors) page of your client area.
- Your site's [connection key](https://server-side.datafirefly.com/en/docs/connect-your-site.html).

## Installation

1. Shopware admin: **Extensions > My extensions > Upload extension**, then install and activate the plugin.
2. Or by CLI: `bin/console plugin:install --activate DatafireflyServerSide`

## Configuration

1. Open the plugin configuration and paste the `dfss_...` connection key.
2. Enable **Enable tracking**.

The module recognises the common consent tools on its own (DataFirefly Cookie Consent, IAB TCF v2, Cookiebot, Didomi, Usercentrics, CookieYes, Iubenda, OneTrust, Cookiehub, Osano, Borlabs, Klaro, tarteaucitron), in the browser and on the server, the same list as the WooCommerce and PrestaShop modules. Leave **Consent cookie name** empty for that automatic detection; fill it in only to force a specific cookie (for example `CookieConsent` and `marketing:true`), which then takes priority.

## Verify

1. Run `bin/console datafirefly:serverside:test`.
2. The test event must show as **Delivered** in your client area's Monitoring.

## Retry queue

Applies to version 1.23.0 and later.

- A failed delivery is queued, then replayed every 5 minutes by a Shopware scheduled task.
- Purchases and refunds go first, then the most recent events.
- An event leaves the queue only when it is more than 7 days old **and** has been waiting for more than 7 days. It is then counted as expired: nothing disappears silently.
- If DataFirefly does not answer (network failure, HTTP 429 or 5xx), the shop stops sending directly for 60 seconds and puts events straight into the queue. An outage on our side therefore never slows down your shop or its checkout. The replay keeps trying, and as soon as it succeeds, direct sending resumes.
- Your site page in the client area shows the state of this queue. The states are explained in the [troubleshooting guide](https://server-side.datafirefly.com/en/docs/troubleshooting.html).

## If something goes wrong

- Logs in `var/log/`, prefix `[DataFirefly SS]`.
- If you run a plugin version older than 1.9.0, update: recent versions fix a possible double count of purchases in GA4.
- The other frequent causes are listed in the [troubleshooting guide](https://server-side.datafirefly.com/en/docs/troubleshooting.html).

Updated: September 1, 2026
