Requirements
- WordPress 5.8+, WooCommerce 5.0+, PHP 7.4+. HPOS compatible.
- The plugin zip, downloaded from the Modules page of your client area.
- Your site's connection key.
Installation
- WordPress admin: Plugins > Add New > Upload Plugin.
- Upload the zip, then click Activate.
Configuration
- Open Settings > DataFirefly Server-Side.
- Paste the
dfss_...connection key and click Connect: the button enables complete tracking and the consent option, and fires a test event on the spot.
The plugin auto-detects the following consent tools, with nothing to configure: WP Consent API, Complianz, DataFirefly Cookie Consent, IAB TCF v2, Cookiebot, Didomi, Usercentrics, CookieYes, Iubenda, OneTrust, Cookiehub, Osano, Borlabs, Klaro, tarteaucitron. The PrestaShop and Shopware modules use the same detection: a tool recognised here is recognised everywhere.
What the plugin covers
- The whole funnel: browsing, product view, cart, checkout, purchase.
- Deduplication by order identifier: no double counting between browser and server.
- Automatic retry queue: failed deliveries are replayed, purchases first (details below).
- The DataFirefly Activity panel in the admin shows the latest events sent.
Verify
- The test event must show as Delivered in your client area's Monitoring.
- Place a test order and find it in the DataFirefly Activity panel.
Retry queue
Applies to version 2.30.0 and later.
- A failed delivery is queued, then replayed every 5 minutes by WP-Cron.
- 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.
If something goes wrong
- After any configuration change, purge your site cache: LiteSpeed Cache and friends otherwise keep serving the old JavaScript.
- If you run a plugin version older than 2.8.0, update: recent versions fix a possible double count of purchases in GA4.
- The other frequent causes are listed in the troubleshooting guide.
Updated: September 1, 2026