Analytics notification_open event is inaccurate

[Andy]

I am using firebase console to send push notifications to all the users by creating campaign in messaging section in firebase console. But the problem I am facing is, I can see notification_open count as 0, whereas it was sent to almost 8000 users. Please see attached screenshot as a reference.

[Joe Spiro]

Hello Andy,

Just to help us better understand:

1. How long did you wait after sending before checking this graph?
2. Have you previously sent messages? Did they produce a different open rate?
3. Do your standard Analytics events work? Have you debugged Google Analytics 4 Firebase? As mentioned in Understanding message delivery, "The reporting tools [...] all require Google Analytics in order to function."
4. Are you sending to Android? Have you looked over and tried to get Aggregated delivery data via the FCM Data API?

Try these out and tell us what you find.

Regards,

Joe

[Andy]

Hello Joe,

Thanks for checking the mentioned issue. In the meantime, I found one configuration was missing on the iOS side and one on Android side. After fixing that, with my flutter application I try to capture notification_open events. With the messaging campaign as well as in debugging mode in firebase console, I was getting the correct numbers except when notification clicked when the Android app was in background mode.

It means, notification open count is not captured by the firebase console when the Android app is in background state only. I confirm in the debug mode in firebase console multiple times and with messaging campaigns too. However with closed app state in  Android & in any state of iOS app, count is appearing properly. 

Please let me know if I need to share any code snippets. I followed the analytics implementation documentation for flutter.

1. How long did you wait after sending before checking this graph?

            - I am aware of the fact that it might take around 24 hours to reflect so I checked the graph after 72 hours to confirm.

           2. Have you previously sent messages? Did they produce a different open rate?

           - After configuration change getting correct rates except it is not capturing Android background state notification_open event counts.

           3. Do your standard Analytics events work? Have you debugged Google Analytics 4 Firebase? As mentioned in Understanding message delivery, "The reporting tools [...] all require Google Analytics in order to function."

          - Yes, other analytics events are being captured and I understand how the message delivery works.

          4. Are you sending to Android? Have you looked over and tried to get Aggregated delivery data via the FCM Data API?

          - Yes I am sending notifications to Android as well as iOS. I haven't gone for an aggregated delivery data option yet. Is it a mandatory step to do to capture events in the firebase console?

--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/rnnQMecC0YY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/6b573e02-a227-4c6e-b515-9cdf6b69453dn%40googlegroups.com.

[Joe Spiro]

Sorry for the delay but what device model are you testing this on?

[Andy]

Hello Joe, I tested this scenario with vivo v9 and Samsung s23 ultra.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/fec077aa-ae2c-495a-9b0d-9e6e4a76e621n%40googlegroups.com.

[Joe Spiro]

Have these metrics improved on Android?

Can you determine if the app had been terminated automatically? Try using logcat to determine whether the app is still up before you press it.

Also please try testing this on other devices and compare the results.

[Andy]

Hey Joe,

I'm sorry for not getting back to you sooner. I verified the app did not terminate while I was testing the app and nothing was recorded on the logcat. I also tried in 3 different Android devices but still no luck. I think something is missing on the configuration side. I need to make a small demo for this. I just wanted to verify if this is some known issue on the Firebase side.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/9ddb4cd5-2589-4815-a620-bb7ec5395178n%40googlegroups.com.