Hello @ototoporo, we have that logic configured, so the purchase event can only fire when a transaction is made, not when a user visits. Alternatively, it is possible to create a custom event and enable the option to fire the event once in ‘X’ hours (for example, 24 hours), but unfortunately, these features are not included in the free version of the plugin; they are available only in the Pro version.
My purchase event is triggering every time the order-received page is refreshed, not just on the transaction as you said. It’s very common for users to revisit the page after purchase, and this is causing an over-count. This makes it difficult to check conversions accurately. Could my plugin be misconfigured, since the event is set to trigger only on the transaction?
No, it is not. As previously mentioned, to avoid overcounting, you need to use the plugin’s Pro version. These features are not included in the free version.
