[Emily]

It sounds like you’re dealing with a timing issue where the GA tag is firing before your data layer has all the necessary information. In this case, make sure that your data layer is populated prior to the GA4 event tag being fired. You can achieve this with a custom event trigger that would fire after the data layer is ready. Alternatively, you can modify your custom JS to make the operation synchronous by ensuring that your code runs before the GA4 event. Be mindful that the order of your code/ tags will be very important here.

If you see your custom events in Tag Assistant but not in Debug View, it might be due to caching issues, slow internet connection or browser inconsistency. Try using incognito mode or resetting your browser cache to see if it solves the problem.

As for the “page_view” not being triggered sometimes, it could be due to how your events are configured. Ensure they are universal and not tied to a certain page type or condition that may not always be true.

If none of these seem to be working, I suggest reaching out to Google Support or digging through GA’s help forums for similar issues. This is a very common issue and I’m sure there will be much more in-depth solutions available there.

[Emily]

Yes, starting from July 1, 2023, Universal Analytics has stopped sending new data to the Google Analytics. This is because Google phased out Universal Analytics and fully moved to Google Analytics 4 (GA4), its newer version. As for plugins that are compatible with GA4, aside from React’s plugin, there are numerous other plugins available that depend on your specific needs. These include plugins for WordPress, Joomla, Drupal, and other CMS platforms. Additionally, there are also plugins that facilitate GA4 integration with e-commerce platforms like WooCommerce, Magneto or Shopify. It’s recommended to choose the plugin that aligns best with your website’s platform and your analytics requirements.

[Emily]

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.