Robert
Forum Replies Created
-
From your description, it appears that indeed the vital data points like traffic name, source, and medium aren’t included in the streaming export, therefore making your analytics somewhat incomplete. The user-attribution data requires about ~24 hours to fully process and is recommended to be gathered from the full daily export, but you’ve stated you can’t run daily exports due to data size. So yes, it seems improbable that user-attribution data is going to be in the intraday tables. It’s also implied that if you want to analyse a high number of events per day, you’ll need to utilize both the streaming and daily exports. However, because of the limited functionality of streaming exports, some data might be missing or incomplete. To ensure you’re not missing out, it may be worth exploring different methods, or considering a consultation with an expert in Google Analytics and BigQuery to explore viable solutions for your specific needs.
-
Yes, it’s feasible to get the count of any named event using an API request in Google Analytics 4 (GA4), irrespective of whether it’s marked as a conversion. To retrieve data for a specific event like ‘events:online_enquiry’, you can make use of the Google Analytics Data API. It allows you to programmatically access report data in GA4 to count user events in your mobile apps and web. You’ll need to use the ‘runReport’ method with specified dimensions (for example, event name) and metrics (for example, event count). However, you’ll need to ensure you have the necessary permissions to access the relevant properties and that your request includes the correct parameters for your needs.
-
The location of the Google Analytics script in your HTML can vary depending on the specific needs of your website. However, in general, putting it just before the closing tag is often recommended. This is because the script is then loaded earlier on the page, giving it the best possible chance to track even the shortest visits. But as long as the script is somewhere in the , it should work properly. In other words, either way suggested by Google should be a right way to go. Without context, it’s hard to say which is the absolute best method for your specific case, but you won’t go wrong following either of these instructions.
-
Currently, Google Analytics 4 (GA4) may not automatically recognize page views when using HashRouter from React Router. This issue might be caused by GA4 not detecting changes in the URL fragment as new page views. GA4’s automatic page view tracking works based on the history API, that is, when the browser’s actual URL is changing, not the hash fragment. For single page applications (SPAs) that use the hash fragment to manage routing, like your setup, GA4 does not understand these as separate page views and does not automatically fire the page_view event.
While sending page view events manually might not be the ideal situation, it is currently the most effective way to get virtual page views tracked in GA4 when using HashRouter. You can do this by firing a custom page_view event whenever a route changes in your application by using available React Router functionality.
