Tessitura has a new TNEW 7.30.0 unreleased bug fix for Google Analytics ecommerce data duplication: TNEXWEB-21398 - "Google Analytics ecommerce data was being triggered everytime the receipt page was loaded or refreshed. This was causing over-reporting of transaction data in Google. This has been fixed."
Does anyone know if this is/was a problem in limited scenarios? In our current TNEW 7 production environment, I verified via GA User Explorer and eCommerce conversion data that we have cases of users revisiting the cart receipt page after a successful transaction in the same session for which the second visit to the cart receipt page did not cause duplicate ecommerce transaction. Thank you in advance for any insights!
I've posted this question in Slack "TN Web Share" workspace too. I'll update this thread if anything comes to light there.
Ref: https://www.tessituranetwork.com/TNEW_7/TNEW.htm#Topics/Release_Notes.htm
Hi Joshua Ause,
The e-commerce tag fires any time the receipt page is loaded, instead of only on the first time as a result of order completion. Any time the page was reloaded by a patron, through a refresh, a back button, or direct reload, it would have fired again.
Chris
Thanks for the feedback, Chris! Is it possible that Google Analytics is smart enough in certain circumstances to NOT log a second ecommerce transaction despite the fact that the transaction tag is fired again? I'm seeing GA User Explorer and eCommerce conversion transaction reporting data suggesting this is happening in at least certain cases. Does this sound impossible to you?
Thank you, again!
Josh
.
It doesn't sound impossible- I don't know for sure if and when they would prevent a duplicate record- perhaps by transaction ID, but i don't know for certain. This defect fix specifically addresses the TNEW piece where we may cause duplicates to be entered, so hopefully it circumvents any issues or reliance on Google fixing it for us.