[Emily]

If you’re looking to get a count of ‘notification_open’ events per message ID, you would first need to ensure that you’re logging the ‘message_id’ parameter with the ‘notification_open’ events. Assuming that you’re doing so, you should be able to access these logs on your Firebase Console.

If you navigate to the ‘Events’ tab under ‘Analytics’ in the Firebase Console, you will see a list of your logged events. Find the ‘notification_open’ event in this list and click on it. This will open a detailed view of the event, and from here, you want to look for the ‘Event Parameters’ section.

Within the ‘Event Parameters’ section, you should see the ‘message_id’ parameter (assuming it is being logged with the event). By clicking on this, you should be able to view a count of ‘notification_open’ events per each unique ‘message_id’ being logged with the event.

If you’re not seeing the ‘message_id’ parameter or not seeing the data you’re expecting, you may need to double-check your event logging code to ensure the ‘message_id’ is being correctly logged with each ‘notification_open’ event.

Remember that it may take up to 72 hours for event data to appear in the Firebase Console so if you’ve recently implemented this logging, you may need to wait a few more days to see the data.

[Emily]

Yes, you can send an app version through the Google Analytics Measurement Protocol API. However, it’s important to note that the way user properties are defined and utilized in Google Analytics 4 is different than previous versions. User properties in GA4 are typically registered and managed in the GA4 UI, so it appears they must be predefined before they can be attached to events or used in filters. To have the application name and version attached to the events, you need to first register these properties (app_name and app_version) in the GA4 UI. This is a change from previous versions where you could just send these properties with your hits without previously defining them. If you have already registered these properties and they are not showing up, it could be due to a data delay in GA4 or potential issues with the way these properties are defined in your code. There is also the chance of an error or delay with the Measurement Protocol API data being processed or appearing in your reports. It may take up to 24 hours for this data to appear.

[Emily]

It’s possible that there might be some compatibility issues between Google Analytics 4 (GA4), Chrome and Apple’s new M1 chip. This might be causing the lag observed on the website, particularly as you’ve noted issues with overall speed and responsiveness when scrolling or clicking. The fact that the issue has persisted despite trying scripts from other sites tends to implicate GA4 as the primary cause. It’s also insightful that the problem has only presented on Chrome and with M1 Apple machines, which narrows down the potential sources of the issue. However, to verify this, you might want to systematically disable and enable GA4 to rule it out as the root cause conclusively. If you’ve got an M2 machine available, you could also test on this – or alternatively ask users for their feedback – to see if the problem persists there too.

While the issue is frustrating, remember that Google Analytics is an intricate tool with numerous benefits, such as providing insights into user behavior that can help optimize your website. If the issue can’t be resolved, there are alternative analytical tools available like Matomo, Heap, and Mixpanel, to name a few, which could be a good switch, while keeping similar functionalities. Still, remember to engage a professional programmer to aid with the transition as these tools still involve a learning curve and will need to be smoothly integrated into your current website setup to avoid further issues.

Remember also to lodge a complaint with Google highlighting this issue. As a large company, they might not be aware of the specific problems affecting individual users or their sites. Your input will be helpful in flagging up and rectifying any compatibility issues between GA4, Chrome, and the Apple M1 chip.

[Emily]

It sounds like your Google Analytics 4 (GA4) isn’t receiving events from Universal Analytics due to a possible missing link between the two platforms. This could be due to a technical glitch or a setup error. Typically, these platforms should be able to communicate automatically once you have the Measurement ID in place. However, in some cases, you need to set up event tracking manually from Universal Analytics in GA4.
In terms of troubleshooting, it could be worthwhile to double-point check your setup, ensuring the Measurement ID is correctly installed, and the needed data streams are in place. It might be helpful to review Google’s guidance on setting up GA4 with Universal Analytics.
If you’ve done all these accurately, it might be a technical issue on the Google side, which could be addressed through the help forum or their support lines. It’s also worth noting that there is usually a delay before conversions start showing up in GA4, so it might be that you need to wait for a bit longer.

[Emily]

Hey buddy, were you looking for this?

Don’t sweat it, here’s how you can do it. Just follow these steps and you should be good to go:

First off, navigate through your GA4 like so:

Go to **’Reports’** -> **’Engagement’** -> **’Events’**.

Here, check out this screenshot to give you a better idea:


Now, to draw an example from my own website, I typically filter with dimension equal to “page path” and look for values that include “/it-IT”, because I operate a lot in Italian.

Oh, and my apologies – my settings are in Italian, but the English equivalents should be pretty straightforward. I tried translating the labels to English, but they just revert back after applying the filter. Hope you can still get the hang of it!

Here’s how it plays out on my end:


If you’re still stuck, just give me a shout. Always happy to help a fellow webmaster!

[Emily]

Setting your GA4 configuration tag to fire multiple times instead of just on the page load should not cause trouble. It’s actually quite common in single page apps to do so since users can easily navigate between sections without reloading the page. However, it seems like there’s an issue with ‘fields to set’ not working properly. The ‘fields to set’ is typically used to pass additional parameters onto hits that aren’t already included in GA4 Config and can be very specific to certain hits. Since they aren’t appearing on your GA debug view, it’s possible there’s a mismatch between the parameters being sent, the processing rules of GA4, and how they’re configured in Google Tag Manager. It would help to check if the parameters are correctly named and comply with the requirements of GA4 event parameters. Make sure the ‘fields to set’ parameters correspond correctly to what’s supposed to be captured in GA4. If all configurations are correct, reaching out to GA or GTM support may be your next step to resolve the issue.

[Emily]

Basically, your current tag will only log a page_view when the history (previous pages visited in the session) changes. If you want to manually log a page view yourself, you can, but you’d need to use a GA4 event tag – the screenshot linked shows an example of how to set it up. It’s also generally better to stop the automatic pageviews that the config tag registers, and instead manually push dataLayer events through your website’s frontend code.

[Emily]

Hey there! So, turns out it was a small hiccup really. I had granted access to my User, instead of the service account itself. But once I switched that around and gave the access to the service account, everything started working perfectly. Oh boy, it was right there all along!

[Emily]

From July 1, 2023, Google is discontinuing support for Universal Analytics, creating problems for those using custom dimensions with methodologies tied to the current system. Accordingly, if you have a code for custom dimensions that is not working following the transition to Google Analytics 4 (GA4), changes will need to be made. You may find some of these changes outlined in the provided guidelines on open-source that could be of use to you. This source discusses adding custom dimensions on GA4 and was added on August 13, 2022. Using this information will ensure your code continues to function properly after the switch.