Alexander
Forum Replies Created
-
There could be a few reasons why your custom table is missing transaction data compared to the Google Analytics Ecommerce UI view. One possibility is that you might be omitting necessary dimensions or metrics in your code that capture the missing transaction data. For example, the ‘transactionId’ metric is usually crucial in order to account for all transactions in Google Analytics. There might also be a mismatch in the time period used for data collection between your custom table and the UI view. Additionally, data sampling could be affecting your reports if your Google Analytics property has a large volume of data. To ensure all transactions show up in your custom table, check to include all necessary dimensions and metrics and align the time period with the UI view. Make sure to adjust for data sampling and consider using resources, such as Google Analytics BigQuery, to handle larger data sets.
-
Your question sparks a key differentiation between Universal Analytics and GA4. With Universal Analytics, events will record category, label, and value information by default, directly through the actual call itself. For example, the gtag code you provided.
On the other hand, GA4 doesn’t inherently support this. If you want the event_category and event_label in GA4, they need to be defined as custom dimensions and then manually set by you. That’s why it doesn’t automatically work out of the box like with Universal Analytics. Now you know why you’re seeing the descrepancy in event data!
-
Totally get the struggle here. In GA4, you might want to check out the “+ Add Comparison” feature for this problem. Apparently, you can look for your filter names through this function which might help you differentiate internal and external traffic without wiping data. Do give this a shot, might just be the solution you’re looking for. I’d love to do a test run for you, but unfortunately, my setups don’t involve internal traffic filtering. Good luck!
-
It sounds like you’re having trouble getting the event tracking information you’re setting up in Avo to show up in Google Analytics 4, and you think the issue might be with the setup in Google Analytics 4 itself. Unfortunately, without seeing your actual code or having a clearer understanding of your setup, it’s hard to pinpoint what might be going wrong. There might be an issue with how your events are being sent from Avo to GA4, or perhaps some configurations in GA4 are not done properly. In order to prevent risks of making the situation worse, it’s recommended to reach out to a professional developer or someone familiar with both Avo and GA4.
-
Google Analytics 4 (GA4) does not currently have a built-in way to manually end a session like its predecessor, Universal Analytics, did. Sessions in GA4 are automatically ended after 30 minutes of inactivity or at midnight local time. While it’s possible to manually start a session using the session_start event, this doesn’t directly affect the session state in GA4 — it really only logs the event. For your specific situation with multiple users on a single device, you might consider alternative solutions since GA4 can’t manually end sessions. One possible workaround could be to use a unique user identifier for each transaction or interaction, so that each user on the terminal is considered separate regardless of the session count. It’s important to note though any solution might need some technical implementation and testing to ensure it provides the data you need.
-
Unfortunately, as of now, there’s no way to fetch the ‘user_pseudo_id’ through the GA4 API. While it’s true that the clientId for Universal Analytics (UA) wasn’t listed in the API documentation yet it was retrievable as a dimension, this isn’t the case for the ‘user_pseudo_id’ in GA4. If you have your GA4 data flowing into Google BigQuery, the ‘user_pseudo_id’ would normally be present there. However, you mentioned that you need to import GA4 data into BigQuery, but the missing dimensions are not available in the API which creates a troublesome situation. Unfortunately, this is a limitation set on GA4 API directly by Google.
-
I’m sorry but your question is missing the actual PHP source code you’re referring to. For me to be able to guide you properly, it would be necessary to include the code you’re working with. That being said, HTTP status code 204 indicates that the server has successfully processed the request and there is no additional content to send in the response payload body. This might suggest that your curl command is working as expected, but your server might not be providing any feedback because the Google Analytics Measurement Protocol doesn’t always provide explicit confirmation that an event has been logged. Make sure you provide the PHP source code for exact guidance.
-
In simpler terms, your solution lies with Google Tag Manager. All you gotta do is pass the ‘user_pseudo_id’ as a custom user parameter there, and you just need to do it once. After that, all your GA4 tags will follow the path you set. There’s a useful tutorial link in your message that explains how to do this, so give that a whirl. This should help you import the GA4 data you need into Google BigQuery.
-
Turns out, the issue was with scopes – specifically, mixing up session and event ones. The ‘transactions’ data is session scoped, while the other stuff I was pulling in was event scoped. So the numbers I was getting were basically useless, because they weren’t compatible. Weirdly, the API let me do this while the dashboard wouldn’t. To fix this, I’m now pulling the ‘conversions’ data, only for ‘purchase’ events.
-
So, this is a bit of an interesting puzzle you’ve got on your hands. Your issue is with Google Analytics 4 (GA4) where events keep repeating themselves a bit like a flashy disco light. I know, not exactly the greatest party, right? This happens for both automatic and custom events. Adding to the mix is the strange behaviour of these duplicates randomly disappearing and reappearing every time you reload the page.
Now, in theory, all should be working since your setup is pretty standard – Google Ads and Google Search Console both link directly to GA4, and every duplicate event even has the same parameters. But there’s always that one troublemaker in the bunch causing chaos, isn’t there?
You’ve tried all the right things – checking for multiple GA4 and GTM codes on the website, installing Google Analytics 4 directly onto the website, running it with and without filters, switching on (or off) “Collect Universal Analytics events” in GA4, and even attempting GTM installations through a Plugin and hard coding it into the header.php file. But no luck so far.
I’d definitely recommend taking a more technical approach to this problem. Start with the front-end tracking debugging and take the GA4 Debugger with a pinch of salt. It’s a rough product and well, a bit buggy to be honest. Instead, you may want to use the Network tab to see what’s being sent out with each page load and observe if any repeated events occur.
If you spot double events, it essentially points to a problem within GTM. You could disable it, reload the page and see if double tracking persists. If it does, you may have another culprit – possibly gtag.js doing some shadow tracking in parallel.
In short, figuring out duplicate event firing for your Google Analytics 4 is really a systematic process of elimination. The issue may not be as complicated as it seems but it does require some technical know-how. Hang in there and you’ll soon have it sorted.
