[Landon]

The issue you are experiencing is because the google_analytics_4_properties() function is not part of the googleAuthR or the googleAnalyticsR package. The Google Analytics 4 (GA4) API is not officially supported yet. The libraries you are using were built before GA4 was released, and they have not been updated yet to include these new functions. Therefore, the function you’ve tried to use doesn’t exist. For now, your best bet would be to keep using Universal Analytics until the libraries are updated or GA4 is officially supported by Google in their APIs.

[Landon]

Yes, there is a similar feature in GA4, but it’s presented in slightly different way owing to GA4’s event-based model. “All Pages” can be found under the “Engagement -> Pages and screens” report in GA4, which provides similar insights to the UA’s “Behavior -> Site Content -> All Pages” report. There, you’ll find data like page views, engagement time, and other valuable information mapped to each webpage of your site. Remember that the terminology in GA4 is quite different, but by exploring these reports you will be able to find most of the metrics available in Universal Analytics.

[Landon]

This user was having trouble getting accurate results in Google’s BigQuery for their GA4 report. The source/medium/campaign data for each event didn’t match the GA4 view. They tried several ways of querying the data, each time running into discrepancies. While they could find the number of ‘null’ and ‘organic’ users, these numbers were significantly different from what GA4 was showing. Eventually, they realized that BigQuery was incorrectly attributing their google / cpc sessions to google / organic. Upon further investigation, they discovered a key called ‘gclsrc’ in the event parameters that indicated whether a session came through Google Ads. By using that key, they were able to accurately identify and convert the google / cpc sessions that were wrongly recorded as organic.

[Landon]

Your current dilemma appears to be related to the way Google Analytics 4 (GA4) and your filters are set up. The Real-time report you mention may indeed be picking up on developer (dev) traffic. Normally, dev traffic and real user traffic can be differentiated by using a variety of filters, but your settings may not be allowing this. You are using a helpful GA debug extension on Google Chrome to examine your website, but you’re noticing discrepancies when the filters are toggled on and off. In terms of your code, it appears you’re correctly initializing GA4 and sending pageview hits. However, without knowledge of your entire setup, it’s hard to definitively uncover the root cause of your problem. A professional who is familiar with GA4 configuration and your specific website setup might be able to provide further advice but to truly separate your internal traffic from your users, consider setting up a separate property for your testing and development cases. Hope this helps!