"Nothing is coming through"
The three causes, in order of probability:
- Consent. If the "Require consent" option is on and your site has no CMP banner, or the visitor has not consented, no event leaves: that is the expected behaviour, not an outage. The telltale sign: the Send test event button works (it bypasses consent) but nothing else arrives.
- The site was never activated. Destinations not saved, or the "Activate my tracking" button never clicked: the module receives 401s.
- Tracking is disabled in the module. On PrestaShop and Shopware, "Enable tracking" ships OFF by default.
401 errors
| Error | Cause and remedy |
|---|---|
unknown_tenant | Site awaiting activation, or wrong Site ID |
invalid_signature | The body was re-encoded between signing and sending: sign exactly the bytes you send |
timestamp_out_of_window | Timestamp in milliseconds instead of seconds, or unsynced server clock (NTP) |
After an HMAC key rotation
Collection stays down until the new key is pasted into the module. That is intended: rotation exists precisely to invalidate the old key.
Shopify
- Vanished webhook: deleted by Shopify after about 48 hours of failures. Check the Site ID in the URL and recreate the webhook.
- Duplicate orders: an "Order creation" webhook is left over next to "Order payment". Delete it.
WordPress / WooCommerce
After any configuration change, purge the site cache: LiteSpeed Cache and other caching plugins otherwise keep serving the old JavaScript.
GA4
- Duplicated purchases: update the module (PrestaShop 1.8.0+, WooCommerce 2.8.0+, Shopware 1.9.0+). GA4 only deduplicates
purchase, and only bytransaction_id: recent versions no longer send the purchase from the browser. - "Unassigned" conversions: events are sent with the session identifier and the referrer, which attaches conversions to their channel. History already recorded by GA4 does not reclassify: the fix applies to traffic going forward.
"Delivered" but little attribution
A delivered event is not necessarily attributed: attribution depends on match quality. Enrich the user data sent: e-mail, phone, IP and user agent, fbp and gclid cookies. DataFirefly modules pass them automatically when they are available and consent allows it.
Replay windows
Before sending an event to a platform, DataFirefly checks its age. The rule is the same for a live event, for an event replayed by a module and for an event released after a free plan quota pause.
- Meta, ChatGPT Ads (OpenAI) and Microsoft Advertising: 7 days.
- GA4: no limit on our side. GA4 accepts older events and gives them a new date; this is a deliberate choice.
- Google Ads, TikTok and Pinterest: no limit on our side, the platform decides.
An event past a destination's window is not sent to that destination. The Inspector shows it as Not sent: too late: at the time of sending, the event was already older than this platform's acceptance window.
The module queue
When the shop cannot reach DataFirefly, the module queues the events and replays them (see the PrestaShop, WooCommerce and Shopware guides). Your site page in the client area shows this queue: events waiting, age of the oldest one, time of the module's last report.
| State | Meaning |
|---|---|
| No report yet | The module has not reported anything yet. Versions older than PrestaShop 1.29.0, WooCommerce 2.30.0 and Shopware 1.23.0 stay in this state: update to see the queue. |
| OK | Nothing to report. |
| Late | The oldest event has been waiting for more than an hour. |
| Silent | Events were waiting and the module has sent no report for 2 hours. |
When the queue needs attention, you get an e-mail, at most one every 24 hours. If many sites fall behind at the same time, the incident is most likely on DataFirefly's side: client e-mails are then held back and only our operators are alerted.
Still stuck?
Write to us: [email protected], attaching the output of the "Diagnose my connection" button. We reply within one business day.
Updated: September 1, 2026