rubait

Thank you for letting us know. It appears this may be a deduplication issue.

We appreciate you bringing this to our attention. We’ll investigate the issue thoroughly and work on a fix. Once it’s resolved, we’ll include the fix in an upcoming plugin update.

Thank you for your patience and support.

Thank you so much for your kind words and for taking the time to update the thread. We’re delighted to hear that the issues have been resolved and that everything is working as expected.

If you’re enjoying TrackSure, we’d greatly appreciate it if you could leave us a review on WordPress.org. Your feedback helps other users discover the plugin and motivates us to keep improving.

Thanks again for your support! 😊

Hi,

We’ve just released a new version of the plugin. Could you please update to the latest version and let us know if it resolves the issue you were experiencing?

We’d appreciate your feedback. Thank you!

Hi,

Thank you very much for taking the time to provide such a detailed report and for sharing the additional investigation from your developer. This information is extremely helpful and gives us a much clearer picture of what you’re experiencing.

Based on your findings, it does appear that both browser-side and server-side GA4 events are being recorded. We’ll thoroughly investigate whether the Measurement Protocol requests are correctly preserving the visitor’s client_id, session_id, and attribution data, as well as review how our WooCommerce integration handles these events.

Regarding event deduplication:

• For the Purchase event, Google Analytics 4 supports deduplication when duplicate purchase events share the same transaction_id.
• For most other GA4 events (such as view_item, add_to_cart, and begin_checkout), GA4 does not automatically deduplicate browser and server events. If both are sent independently, GA4 may record both events separately.
• Unlike Meta Pixel, which provides event deduplication using an event_id, GA4 relies on different mechanisms and does not automatically deduplicate most event types.

That said, the behavior you’re describing, particularly the large amount of Unassigned / (not set) traffic and duplicated ecommerce events suggests there may be an issue with how the server-side events are being sent or attributed. We’ll carefully review our implementation to ensure the correct identifiers and attribution data are being included wherever possible.

We’ll also investigate:

• The duplicated WooCommerce purchase events.
• The (not set) / Unassigned traffic attribution.
• The handling of client_id, session_id, and other GA4 identifiers.
• Overall compatibility and behavior of our server-side GA4 integration.

We appreciate you bringing this to our attention. Reports like yours help us identify edge cases that aren’t always reproducible in our own testing environment, and they play an important role in improving the plugin for everyone.

We’ll investigate this thoroughly and work on addressing any confirmed issues in an upcoming update. If we have any findings, workarounds, or require additional information during our investigation, we’ll update this support thread.

Thank you again for your patience and for helping us improve TrackSure Cloud.