-
Unusual GA Behavior: SKU ID as Transaction ID with 0 Quantity
Hey folks, I’m wrestling with a bit of a head-scratcher here and I’d appreciate a fresh set of eyes on the problem. I’ve been doing my best to set up a data layer on the order confirmation page according to the Google Developer Guide instructions (https://developers.google.com/analytics/devguides/collection/ua/gtm/enhanced-ecommerce), but I’ve hit a stumbling block.
Here’s the strange part: some orders appear twice in the GA Report. Not total duplicates, but you can see the SKU ID gets listed as the transaction ID, minus any actual quantity (Check out the attached image: GA Conversion report). It’s intriguing because it’s only happening to some of the orders, not all of them.
I’ve run out of ideas to pin down the cause – at first I thought maybe it’s on the data layer setup, but I’ve triple-checked and I’ve been exactly following Google’s guide.
Has anyone seen anything like this before? Or better yet, know how to correct it?
Cheers in advance!
For reference, here’s the Purchase Event Data Layer: Purchase Event Data Layer
-
2 Replies
-
It could be possible that the transactions are being sent twice from your website to Google Analytics, hence the duplicates. This could occur if, for example, a user refreshes the order confirmation page, causing the data layer to be reshared. To resolve this issue, you may need to implement a solution that prevents the data layer from being shared again once the transaction is initially processed. Additionally, if you are unable to identify an issue with your data layer setup, it might be beneficial to seek assistance from someone well-versed with Google Tag Manager as they could better identify if your tags, triggers or variables are set up incorrectly.
-
The issue you’re facing, where some orders appear twice in the GA Report with the SKU ID listed as the transaction ID and no actual quantity, could be due to several reasons. It’s possible that the issue arises from analytics implementation – your codes may be firing twice due to page refresh or redirects. Another potential reason is that there could be a problem with the e-commerce tracking setup, meaning that a single purchase is being tracked as two different transactions. It would be beneficial if you go through your Google Tag Manager setup, analyze the triggers being used and ensure tag firing sequence is correct. Additionally, cross-check all aspects of your e-commerce tracking setup to spot any issues that might be causing this problem. Also, don’t forget to verify all settings in your GA admin panel to ensure it’s not contributing to the problem. If the problem persists, you might want to consult with a Google Analytics specialist or Google support.
Log in to reply.