George
Forum Replies Created
-
You’re having some trouble with Funnel Explorations in Google Analytics when user_id data comes into play. From your description and screenshots, it seems the user counts shown vary different reports. You were informed by Google Support that Funnel Explorations doesn’t show any events where a user_id is involved, which is quite confusing, considering you would expect all related data to be included. You’re trying to understand If it’s common for Funnel Exploration to exclude data linked with user_id and what kind of impact it may cause to other types of explorations. In addition, you’re interested in knowing how you can effectively use the Funnel Exploration despite this hiccup and create useful graphs for your team. You added that on cross-checking you found the data being received by your Google Analytics 4 (GA4) property is correct however, the number of users shown in the Funnel Exploration for the same period of time is not accurate.
-
The discrepancy you’re noticing can occur because Google Analytics and BigQuery can process and aggregate data differently. ‘A’ is using raw event data in BigQuery, whereas ‘B’ gets pre-aggregated data from the Google Analytics connector. It’s always important to remember any processing or aggregating nuances when comparing data from two different sources.
-
Sure thing! The UTM parameters bag the top priority. So for Q1, your Google Analytics report will display ‘linkedin/testsocialpost’. As for Q2, you’ve got it bang on!
-
To find out what keywords people are using when they stumble upon your website via Google, you need to use Google Search Console. This tool from Google allows you to understand and enhance your site’s presence in Google Search results. You can link it with your Google Analytics account, and it will show the keywords people used. You can also view this data based on the search date and time.
-
You are correct in your observation. By default, Google Analytics GA4 omits rows where values of the specified dimensions are null. However, you have incorporated the ‘keep_empty_rows’ argument in your RunReportRequest, and have set it to ‘True’. This should ideally prevent the exclusion of rows with null values. It looks like your code is correct.
If the problem persists, it may be due to internal GA4 settings or perhaps a bug. You might want to consider contacting GA4’s support team for further assistance. Since the code appears to be correctly asking for rows with null values to be included, the problem is likely rooted elsewhere.
