[Vijay]

Google announced that support for Universal Analytics will stop after July 1, 2023, as shown in this post: https://support.google.com/analytics/answer/10759417?hl=en. Consequently, any code related to it, like the custom dimensions example given, might start malfunctioning. As a workaround, you will have to adjust to Google Analytics 4 (GA4) and learn how to add custom dimensions there. For those seeking guidance, you can refer to https://jaenal-leegenmao-1.gitbook.io/sakari/playground/upgrade-your-universal-analytics. Remember, this information was released on August 13, 2022. Keep this in mind to avoid confusion or outdated coding practices.

[Vijay]

This discrepancy could be due to several factors. Check if there are any purchase instances where the ecommerce value is exactly $250. Since your conditions specify above $250 for a wholesale purchase and below $250 for a regular purchase, a purchase exactly at $250 might not get categorised into either, hence creating a discrepancy. Additionally, consider checking your data for any incomplete or missing values. If the ecommerce value for a purchase event wasn’t tracked or recorded properly, then it wouldn’t fit into either of your categories and hence wouldn’t be counted in your new event tallies. It’s also important to note that there could be a lag in data processing. This might mean that recent purchase events might not have been added to your new event tallies yet. Lastly, it’s possible that your conditions for categorising the purchases aren’t working exactly as intended and might need adjusting.

[Vijay]

Unfortunately, without the actual code and images, it’s a bit hard to provide an exact solution. But I can still suggest possible reasons and solutions. The issue might come from a small calculation error, which can happen due to tax, fees, or round-off discrepancies while converting between currencies, if global transactions are involved. This might explain the slight discrepancy in monetary values. Please ensure that your calculation for total revenue and individual item totals match the formula used by Google Analytics 4 to calculate ‘total revenue’. Different measurement or rounding methodologies can result in slightly different numbers. Also, verify that tracking and taxes are handled consistently in both platforms. If all appears correct, try testing with a few different orders of varied item types and totals to see if the discrepancy follows a predictable pattern, that might provide additional clues. It’s also essential to check the portion of code which is suspected to make sure the numeric values aren’t being adjusted. If you’re still having trouble, reaching out to the support of both Shopify and Google Analytics 4 might be your best bet. They will likely have greater insight on specific settings or configurations that could be causing your issue.

[Vijay]

One possible reason for the discrepancy you’re seeing could be due to the different ways Google Analytics defines an “active user.” For instance, seeing 5 active users in UserGroup1, doesn’t necessarily mean that those users were active the same day or week that you’re looking at on your custom dashboard. The cumulative total for each user group might be covering a longer time span than the specific date or period you’ve selected on your dashboard. It’s quite possible that out of the 11 active users across your groups, only 6 of them were active within the timeframe displayed on your dashboard. Additionally, Google Analytics might be applying different filters or rules at the dashboard-level. Ensure that your dashboard’s settings match with individual user groups’ settings. If you are still facing issues, it might be a good idea to get in touch with Google Analytics Support for more detailed troubleshooting.

[Vijay]

It sounds like you’re having trouble with generating the public key. When you hit ‘Create & Generate Key’, the system should provide you with the key. The 500 error might be due to a server side issue. It could also be that the username ‘placeholder’ is not recognized by your SFTP server. Try checking your server settings again and make sure the username is correct. If the problem persists, it could be something to do with your Analytics setup.