# Install the PrestaShop module

> Install and configure the DataFirefly Server-Side module on PrestaShop 1.7.6 and up: zip upload, connection key, tarteaucitron consent, test event.

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

---

Compatible with PrestaShop 1.7.6 and later. Installed in 5 minutes from the module manager. A failed delivery is queued and replayed, purchases first, so a passing outage costs nothing.

## Requirements

- PrestaShop 1.7.6 or later.
- The module 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. PrestaShop back office: **Modules > Module Manager > Upload a module**.
2. Upload the zip as is, without unzipping it.
3. Click **Configure**.

## Configuration

1. Fill in **Tenant ID**, **HMAC secret** and **Events endpoint**: the three values from your DataFirefly site page.
2. **Require consent** option: the module lets an event out only once the visitor has accepted advertising. It recognises these on its own, with nothing to configure: tarteaucitron, DataFirefly Cookie Consent, IAB TCF v2, Cookiebot, Didomi, Usercentrics, CookieYes, Iubenda, OneTrust, Cookiehub, Osano, Borlabs, Klaro, in the browser and on the server, the same list as the WooCommerce and Shopware modules. Recommended if your shop has a consent banner.
3. Set **Enable tracking** to Yes: it ships disabled by default.
4. Save, then click **Send test event**.

No consent banner on your store yet? The [Cookie Manager for PrestaShop](https://www.datafirefly.com/product/cookie-manager-tarteaucitron-conformite-rgpd-cle-en-main-pour-prestashop/) ships tarteaucitron ready to use, with Consent Mode v2.

## Verify

1. The test event must show as **Delivered** in your client area's Monitoring.
2. Place a test order: the module sends purchases on order validation.

## Retry queue

Applies to version 1.29.0 and later.

- A failed delivery is queued, then replayed as visitors browse the shop: at most every 30 seconds, never two replays at once, in batches of up to 20 events sent in parallel.
- Low-traffic shop: an optional cron URL, protected by a token and served over https only, triggers the replay without waiting for a visit.
- 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: **Advanced Parameters > Logs**, filter on the `[DataFirefly SS]` prefix.
- If you run a module version older than 1.8.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
