[Noah]

The issue you’re experiencing may be due to one or a combination of a few potential factors. The “(not set)” field usually appears when there is data that Google Analytics 4 (GA4) could not identify or process, possibly due to missing or disregarded information. Elements such as ad-blockers, inconsistent UTM parameters, or lack of correct e-commerce setup may cause this.

For countries, it’s possible that Geo-IP exclusion filters are set in Google Analytics, preventing the data from displaying accurately. In terms of the device category showing only “Desktop”, it might be because the mobile version of the site does not have the correct GA tracking code embedded or your audience overwhelmingly uses Desktops.

You should verify the setup of GA4, making sure that all essential tracking codes are properly implemented across all versions and pages of your website, and also check your filter settings for possible obstructions to the data. Without a broader look at your GA4 setup, these are the most common issues that could be causing the trouble you’re experiencing. However, other individual or specific configurations can also be at play.

[Noah]

Considering the restrictions that you’re running into, one solution could be to consider tagging users as “new” when they first join, and keeping that tag over time, even when they no longer satisfy that condition. It might demand some workaround in your system’s setup, but it could be worth a try. For retrospect analysis, try digging into the historical data where you have initial capture point of the user (their sign-up or first interaction date for instance).

If a unique identifier exists, it could be easier to track a cohort of new users and their progression. If such options are not present in your analytics platform, you might want to consider external tools or even custom setups where users are tagged with their start date. Large scale data platforms often have tools for cohort analysis which allows you to exactly do that.

Remember, you’re trying to change your user data categorization into a permanent attribute, rather than a fluid state. This allows you to track the behaviour of this group over time, despite the changes they undergo.

[Noah]

Without knowing the exact nature of the problem, I would suggest we first cross-check all the configurations and credentials that you have inputted. Make sure to update everything needed for making a call. Check if the network connectivity is stable and there’s no issue from the server-side. Also, ensure that the number you’re dialing to is active and reachable. If the problem persists, it would be best to reach out for technical support, they could help identify if it’s a software or hardware issue.

[Noah]

The issue you are encountering is rooted in how Chrome Extensions handle the Content Security Policy. Google currently limits the resources that can be loaded by a Chrome extension to improve security. This poses a challenge though as direct access to the analytics script is blocked. This is done to protect extension users from inadvertently executing harmful scripts. One possible workaround to bypass the limitation does not involve directly calling the script. You can make use of the Measurement Protocol by Google Analytics to send HTTP requests. Here, you would instantiate an XMLHttpRequest (or fetch) in your JavaScript file and use it to send pageview or event data to Google Analytics. While it’s a more roundabout way as it requires forming and sending HTTP request instead of simply embedding the script tag, it gets around the CSP restrictions in the manifest.json file.

[Noah]

The user is seeking a solution whereby a series of custom events can be triggered on their website using the Google Analytic’s gtag (‘event’,…) protocol without having to initial with a gtag(‘config’,…). The issue they are experiencing is that the custom events aren’t populating without an initial config call and if they do use it then they end up with a duplicate page view.

Additionally, they wish to avoid a GTM (Google Tag Manager) setup for each event, because they require the ability to send any data from the site’s front end and have it integrate seamlessly with GA4. The question then is centered around finding a solution or guidance on being able to get gtag(‘event’,…) calls to function at the same level as if it has been called from gtag(‘config’,…), and whether they can set up a GTM trigger/tag that carries raw data directly to GA4.

[Noah]

The issue you’re experiencing might be due to Google continuously updating and making changes to GA4 functionalities, in contrast to the traditional GA. The “Page path + querystring” option may have been replaced or omitted in the recent updates. Currently, there is no known method to bring back the missing option. It would be prudent to keep your learning materials for GA4 updated and verify the functionalities with official Google Analytics documentation or certified GA experts. Generally, GA4 tends to focus more on events than on page views, so the information you used to find under “Page path + querystring” might be tied to events now.