Duplication of Data in GTM

[annatekl]

Context

Currently, events are being triggered multiple times within the data layer, causing double counting of user actions. This issue affects several events, not just wallet connect/disconnect. We need to audit the data layer to ensure that the events are being sent correctly and are not duplicated.

One of the example is below:

Wallet connect and disconnect events are being triggered multiple times on page refresh, causing duplication of data and double counting in analytics.

Steps to Reproduce:

• Open the page vortex pmf version
• Refresh the page without any action from the user.
• Observe the data layer firing events for wallet connect and disconnect without user interaction.

Screenshot

Expected Result:

The wallet connect and disconnect actions should only be captured when the user explicitly interacts with the wallet, and not on a page refresh.

Requirements

• [ ] There should be a check to prevent multiple firings of the same event.

[ebma]

Isn't this ticket somehow a duplicate of #132? Why would we need both tickets if this is supposed to remove all duplicates and the other tickets is about a specific one? It would be great if we can have a list of all the duplicates that you noticed in the description of the ticket though.

[annatekl]

let me rewrite the first with additional data

[annatekl]

closing as covered by the ticket