[Huong]

You have expressed several concerns about your code implementation that reads data from UA and how future updates and changes may affect it. First, you’re worried whether the code would cease to function by July 2023 due to technological shifts. Secondly, you’re wondering whether having your UA connected to GA4 with the GA4 Setup Assistant, which has been running since April 2022, will be compatible with your current code. Thirdly, you also ponder if using Google.Apis.AnalyticsReporting.v4 as an alternative would allow you to still use the View ID from your UA beyond July 2023.

Additionally, you’ve brought up a concern about a prototype you built that needs a View ID, which GA4 doesn’t have. You’ve worked around this by using the View ID from your UA, which is also linked to your GA4. You’re uncertain whether this workaround will continue to function when July 2023 arrives, leading you to question if you should shift to another implementation.

For the experts to provide a more detailed response, please provide your existing code and the prototype code you’re referring to.

[Huong]

It seems like there might be an issue with the timing or the scope of variables in Google Tag Manager. Variables in GTM have different scopes and lifetimes depending on how they are used. For instance, if these variables are defined in a specific event and you are trying to retrieve them after the event has fired, they might not be available. Hence, the “undefined” or “null” values. This might explain why manually entering a string instead of the dataLayer variable for the “value” seems to work, as the string is available immediately.

To debug this issue, you should verify if the variables are correctly populated by means the GTM preview mode. This allows you to see how your tags, triggers and variables load and behave in real time on your site. You should also verify whether the variables are still present in the dataLayer at the time the UET tag fires. If the variables have been lost, you might need to revisit how you’re managing your dataLayer. Moreover, ensure that the UET tag fires after the dataLayer has been populated with the required variables.

Last but not least, always confirm your settings after making changes and conduct tests to ensure everything has been set up properly. The goal is to make sure your GTM setup fires and sends data as expected.

[Huong]

There could be several reasons why your Google Analytics 4 (GA4) may not be filtering out internal traffic properly. The issue might come from the configurations. Google Analytics 4 handles filters differently compared to Universal Analytics, so might be why the method of excluding an IP address isn’t working as expected. Also, if the IP address isn’t static and changes periodically, it could also cause inconsistencies in the filter. Furthermore, GA4 ‘Realtime’ report might also be displaying cached data, hence showing the same number of users for Internal Traffic and All Users. It would be a good idea to cross-check all the configurations and see if the issue persists.

[Huong]

Yes, that’s absolutely correct. You’re trying to offer Google Analytics with data on app screen visits from your .Net MAUI application. By utilizing the Plugin.Firebase package, you’ve managed to deliver event data successfully but still struggling with the ‘Pages and Screens’ section. This is imposed by the screen title and class division of your data, with the latter being contributed by you as a developer. Your current challenge is determining a suitable methodology for supplying a screen name where ‘Not Set’ is provided instead.