Forum Replies Created

  • While you could technically use one Google Analytics profile to manage all your sites, it’s probably a better idea to create separate accounts for each one. This way, you can avoid some potential complications down the road. For instance, when you’re extracting data via API, you would have to filter it by domain every time if all your sites were under one account.

    Also, Google Analytics has certain restrictions when it comes to creating custom dimensions and metrics, which might limit your data analysis capabilities if you’re juggling multiple sites under a single account. Overall, this structure is particularly beneficial if you’re dealing with separate businesses or different clients.

  • Yes, it is not unusual for there to be some discrepancies between ecommerce purchase data in Google Analytics 4 (GA4) and the actual database record. The level of discrepancy varies, but a difference of 20 to 30% can sometimes be observed. This discrepancy arises due to several reasons. Firstly, not all users enable cookies, which GA4 uses for tracking data. Secondly, GA4 might miss some transactions due to issues like website loading speed, Internet connectivity, or if a user leaves the page before the transaction is recorded. Additionally, GA4 may not accurately track purchases made on different devices. Also, database records usually capture every transaction in real-time, while GA4 often operates on sampled data, which could also contribute to a discrepancy. Lastly, it’s important to make sure all the ecommerce tracking codes are implemented correctly. Mistakes in tracking code setup can cause inaccuracies in GA4 data. So, while GA4 is a powerful tool for understanding user behavior and ecommerce trends, the exact purchase data might be more accurately reflected in the database records.

  • Unfortunately, you cannot directly change the ‘deviceCategory’ value in Google Analytics. This is a built-in field which is automatically populated by Google and it only supports ‘desktop’, ‘tablet’, and ‘mobile’ categories. The only way roundabout way would be to possibly create a separate segment or filter for Android devices specifically, or indeed use a custom dimension that could specify what type of mobile device is being used. But as for changing the ‘deviceCategory’ value directly, it is not possible.

  • Hey there! What you’re experiencing is completely normal. Google Analytics groups dimensions by unique values and then sums up the metrics. So, for example, if we have Report A with dimensions like country, region, and city, let’s say with values like South Africa, Western Cape, and Cape Town, respectively. Now, if there’s a Report B just with the country dimension, it will not have separate rows for each city in South Africa, but will just have one row for South Africa.

    In your case, you’ve got values like Lorem, elit, and Nunc that are shared between your two events. So, Google Analytics proceeds to put them all into one row. The good side of this is that by adding the metric eventCount to your reports, you can still see the number of events. Your first report will show 1 eventCount per row, and your second report will show 2 eventCount for the same row. I hope this clears it up!

  • Lucas

    Member
    13 January 2023 at 3:47 pm in reply to: What are the updated methods for batching POST requests in GA4?

    It sounds like you’re working hard to find an endpoint to batch data before sending it off, but you’re having a hard time finding a suitable replacement for the ‘/batch’ endpoint in GA4. Currently, it appears GA4 doesn’t directly support the batch endpoint as Universal Analytics did.

    As an alternative for bulk data transfer, you might consider using the Google Analytics Data API. While the realtime event might seem missing, the GA4 data API provides batch data functionality.

    Your exploration with the gtag.js solution you found on the Google developer site could be a good fallback, despite feeling like a shortcut. These tools are provided for this very reason – to streamline implementations and provide support for varying use cases.

    Remember, Google Analytics is an evolving platform and Google has been actively updating their GA4 offering. New functionalities are added often, so keeping an eye on their release notes and updates could prove helpful. Also, consider reaching out to Google’s support or community forums for more specific guidance on your task. You’re not alone in these challenges – others developing with Google Analytics might have encountered this and found workarounds or solutions.