Firebase Cloud Messagin:: Notification Delivery Delay

[Mehedi Hasan]

Dear Team,

We are seeing  delay in firebase notification delivery from February while using topic or targeting apps from cloud messaging notification composer and our legacy http delivery tool. Notification intended to topic which has smaller number of devices subscribed(for example 100k) are delivered instantly. But when number of subscribed devices are higher or we sent full base notification from composes, latency increases.  My last notification analytics is telling me that it had targeted 23M users, however I have monthly active users of 10M. 

We have some query in this regard:

1. We used to send all notifications as high priority. But our open rate is running low for past couple of months (3-6%). Does this have any negative impact?

2. According to docs, usual limit of concurrent fanout is 1000/sec and 10000/sec is not uncommon. But actual achievable fanout rate is dependent on the number of project requesting for fan out. In that case can we consider that, on average 1000/sec fanout rate will enable us to reach 100k customers in 100s or 1M customers in 1000s ?

3. Is there any we to check what is my current fanout rate and whether I should initiate another notification campaign? May be through some bigquery as shown in doc?

4. I am attaching an image of our report of FCM notification. It seems we have sent 3.3B notification in last 1 month and only 12M was received? I am not sure where the rest are lost? If I assume they have uninstalled/reinstalled the app or their FCM token has become invalid, aint this "sending" attempt eating up my available fanout bandwidth?

5. If this huge sent count is an issue, how to get rid of  this sent attempts? Is there any way to invalidate those FCM tokens (like attempting to send dummy notifications)

[Kato Richardson]

Hi Mehedi,

This looks like normal progression. You'll note that the sends also decrease circa March 6th. So the apps uninstalled or perhaps reinstalled and receiving new tokens received the March 3rd send, but were likely returned as invalid reg tokens, and then removed from the list. The follow-on sends didn't contain the invalid tokens.

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/c4aa9a57-5703-4e7c-b8e2-5e06439c986d%40googlegroups.com.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Mehedi Hasan]

Hi Kato,

Thanks for getting back to me. Could you kindly help me with the other queries?     

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CADypTEZFhVO04Rvi1M7BFzuL9CFFw4Z_-B9NgmxTAaTOv1zphw%40mail.gmail.com.

[Kato Richardson]

> 1. We used to send all notifications as high priority...

I don't know anything about how Android treats these, sorry.

> 2. According to docs, usual limit of concurrent fanout is 1000/sec and 10000/sec is not uncommon...

Math looks okay, but I don't know more here, sorry.

> 3. Is there any we to check what is my current fanout rate and whether I should initiate another notification campaign?

You already answered this. https://firebase.google.com/docs/cloud-messaging/understand-delivery#bigquery-data-export

> 4. ...It seems we have sent 3.3B notification in last 1 month and only 12M was received?...

Answered above

> 5. If this huge sent count is an issue, how to get rid of  this sent attempts?

Answered above. The invalid reg tokens are revoked (for others reading: unless you are manually managing device groups or lists of reg tokens, in which case you need to handle the invalid errors and do so).

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANVNL6ct7gi-BpCn2kyERqe%2BOohkcDVP3fU2Ra-dz0anJjGPSg%40mail.gmail.com.