Everything you'd want to know before you install.
A detailed look at how DataFirefly Server-Side — WooCommerce client + server tracking (free) works, why we built it the way we did, and the thinking behind the features above.
A free connector, a service that does the work
DataFirefly Server-Side is free and will stay free: it is the WooCommerce connector for the DataFirefly Server-Side Tracking service. The plugin captures your shop's events and signs them; the service delivers them server-side to your advertising and analytics platforms. You install the plugin at no cost, you subscribe to the service for ingestion and delivery. That split of roles is what makes installation trivial on the shop side and operation light on the server side.
One key, everything configured
From your DataFirefly client space, copy the connection key (it starts with dfss). Paste it into the plugin, click Connect: client and server tracking activate together, a test event goes to the dispatcher, and the client tags are put in place for the destinations you configured. An advanced mode lets you, if needed, enter the tenant, the secret and the endpoint manually.
Full funnel, client + server, without double counting
The plugin tracks the whole funnel in the browser: page view, product view, add to cart, checkout and add payment info. The purchase, meanwhile, fires server-side from WooCommerce. Both layers share the same event_id, keyed on the order, so Meta, GA4 and the rest deduplicate automatically. You recover the conversions the browser lets slip, without ever counting them twice.
The purchase fires from the server: neither blocked nor spoofable
The purchase conversion is triggered by the WooCommerce order hooks (payment complete, processing, completed), idempotently: the same purchase is never sent twice, even if several hooks fire. Because it comes from the server, no ad-blocker or ITP can prevent it. Conversely, the public collection endpoint deliberately refuses any purchase sent from the browser: no one can inject fake conversions to inflate your Meta or GA4 revenue.
Consent first — compatible with Cookie Consent v2
The consent gate is on by default: nothing fires until marketing consent is granted. The plugin natively detects our DataFirefly Cookie Consent — GDPR & Google Consent Mode v2 module and reads its consent cookie directly on the server: if the marketing category is refused, the event is discarded, whatever the browser claims. No banner yet? The plugin also supports WP Consent API, Complianz, Cookiebot and IAB TCF v2. Paired with Cookie Consent v2, you get a consistent chain: banner, Consent Mode v2 and server-side tracking that speak the same language.
Reliability and transparency
An event that could not be delivered is not lost: it is queued and redelivered automatically every 5 minutes. The activity panel shows you, live and without jargon, what has been delivered, what is queued and what has been rejected, with the HTTP code and the number of attempts. Your destination credentials and the signing secret never leave the server; only public identifiers reach the browser, and every event is HMAC-signed.
Move up to the DataFirefly Server-Side subscription
The plugin captures and signs; the DataFirefly Server-Side Tracking service ingests and delivers server-side to five destinations: Meta CAPI, GA4, TikTok Events API, Pinterest Conversions API and Google Ads. The dispatcher is hosted in Germany, ingestion is HMAC-signed, personal data is masked and firing respects consent. One integration, one consolidated invoice, several sites possible. Discover the plans and subscribe at server-side.datafirefly.com: Starter at 39 €/month (1 site, up to 500K events), Growth at 119 €/month (5 sites, up to 2M), Scale at 349 €/month (20 sites, up to 10M). The plugin is ready: all it needs is your key.
There are no reviews yet.