-
There could be a number of issues causing these problems. Firstly, transaction ID’s not being recorded could be due to a break in the tracking or potentially an issue with the way your Ecommerce data is being sent to Google Analytics.
One Transaction ID linking to multiple purchases could be due to a technical glitch or could be the result of the way your website handles transactions – particularly if ID’s are not cleared and reissued correctly for each new purchase.
As for adding ‘payment type’ as a custom parameter to the purchase event, it should be possible as long as it’s included in your website’s data layer when the purchase action occurs. However, you would need to do some custom scripting to handle this in your tag manager.
In regards to your second image, it’s hard to make a precise conclusion without direct access to your data. However, seeing all transaction IDs and revenues showing as duplicated could definitely suggest that events are firing multiple times. If transaction and revenue data is duplicated, that suggests that your tags could be firing twice.
You could verify this by checking your tags’ firing status in Google Tag Manager’s preview mode. If you see the same tag firing twice, then that could be the issue. It might be worth looking into some of the Google Tag Manager forums, or indeed, Google’s own tutorials for more information on data layers in single-page web applications.
