Lucas
Forum Replies Created
-
Discrepancies between Google API numbers and dashboard data is common, often it’s because API includes more raw, real-time data before certain filters and adjustments are applied in other Google platforms. To verify if you’re querying the right field, cross-check with GA4’s documentation or Google’s API documentation.
As for the possibility of underreporting on the frontend, it’s critical to remember that GA4’s frontend dashboard applies certain beneficial adjustments to data representation such as sessionization and deduplication. The frontend is generally more user-friendly and accessible but can sometimes oversimplify the raw data or apply built-in filters that might exclude certain event-types.
In the case of API overreporting, realize that raw data can include duplicate events, spam, bot traffic or irrelevant events that frontend analytics platforms would adjust for. So, while API data might appear higher, it could be less refined or contain ‘noisy’ data.
It’s also worth checking and comparing the time zone settings between your API and Google Analytics. A substantial difference in the time zone could result in a discrepancy in the data being pulled and displayed.
Finally, make sure to take into account the natural data processing latency. GA4 data can take up to 48h to finalize, you might want to add a delay in your data analysis to account for this latency.
-
Yes, it would be best to prioritize updating your website’s core code to include the new G-XXXXX code; this is because Google plans to sunset the Universal Analytics (the UA-XXXX you’re referring to) and it’s being replaced by Google Analytics 4 (GA4). Even though your UA data is still flowing to GA4 for now, it’s not clear how long this support will last; hence updating to the new GA4 property ID is advisable. As per the transition, there’s no rush as Google also offers dual tracking to use both GA4 and UA till you fully migrate. It would be ideal to make this transition gradually and get accustomed to the new interface and data model of GA4.
-
In order to get extra dimensions in Google Analytics 4 (GA4) for platforms other than web or Android, you would need to set up custom dimensions. This involves sending custom parameters in your events that can be registered in GA4 as custom definitions. In the JSON message that you send for an event, you can include these custom parameters. For example, to add a custom dimension for user’s preferred language, you might include a field in your JSON message like “preferred_language”: “English”. After you’ve included these custom parameters in your events, you would need to go to the GA4 interface, navigate to ‘Custom Definitions’ under ‘Data’ in the left-hand menu, and then register these custom parameters as either custom dimensions or metrics, as appropriate. It’s important that the name of these custom definitions exactly matches the custom parameter names sent in your JSON messages. Once set up, these custom dimensions or metrics will be available for use in your reports. For further details, be sure to refer to the GA4 documentation or contact Google Support.
-
Yes, in this scenario where all the steps are located on the same URL, GA4’s standard funnel may not give you the insight you need. Instead, you’ll have to use events to gather this information. For each step in the form, create a distinct event that fires when the user completes that part of the form. This way, you’ll be able to track each step as its own event and create a funnel using those events. In essence, you’re creating your own custom markers within the same page and tracking movement between them. This method allows you to gain the fine detail within-page navigation that a typical pageview-based funnel analysis wouldn’t provide.
-
In this scenario, it seems like old properties from your previous event are recurring because you’re not setting these properties as null when they’re not in use. What you can do is while sending the data object include all properties, but for the ones that are not being used, just assign them as null. So when you’re sending ‘Zack’ and ‘Ryder’, also send hobby and age as null.
Also, you mentioned something about trying to reset through tag sequencing. The thing here is, you should call the reset after your event is pushed, not before. This way, the data you need doesn’t get wiped out prematurely.
Real quick though, keep in mind that although tag sequencing could work, it might affect the state of your data layer.
Now, if you can’t nullify fields from the frontend and still want to fix this using Google Tag Manager, you’ve got another option. This involves creating a custom JavaScript variable (CJS). Here, all your data layer variables go through this CJS variable. The function of this CJS variable would be to inspect what values each event has and pass them on as required. But remember, you’ll need to do this for each data layer field that you want to cleanse.
-
It sounds like there might be a misunderstanding in interpreting Google Analytics GA4. Typically, “Engagement Time” is recorded in seconds which is the raw data sent from your app to Google Analytics. However, when you observe the it in your analytics console, it might default display to days for the sake of simplicity. This could potentially happen if the overall time recorded is very large. Moreover, there might be some conversion or standardization applied when processing and displaying data. You might want to dive deeper into customizing your view settings or creating more specific segments to monitor the particular user engagement in seconds or minutes as required. If this is consistently problematic and doesn’t align with your expectation, contacting Google support or browsing forums may provide a solution.
-
It seems like your trouble might be rooted in the connection between your Google Analytics 4 (GA4) and Universal Analytics (UA) properties. Double-check to ensure that your GA4 property is linked to your UA property.
Alternatively, it could be that your UA property lacks goals. If there aren’t any goals set up in your UA property, then there’s nothing to import into GA4 which could explain the missing button.
Here’s a link that will guide you in checking what properties you’re connected to: [Find your connections](https://support.google.com/analytics/answer/13342757).
And if you’re unsure about the connection process, this link gives you a step-by-step description of how to connect your properties: [Connecting UA to GA4](https://support.google.com/analytics/answer/12938611).
