New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 606806 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

No view on push notification status

Reported by gaurava...@gmail.com, Apr 26 2016

Issue description

HI
I wanted to know is there is there anything in works that gives info on what happened to push notifications from service workers ? 

GCM has it in play console where exact journey of a push is given. 
We are getting message ids for most of the active subscribers but when we are not getting impressions in our analytics saying it reached the device. 

Can a system be built which explains what happened to push notification is given. 
Also can information be passed if there any cache clearing or anything that took away the device token of that device ? That would be really helpful as then we can understand what is causing that the device tokens to go away. 

Right now our stats are 400K active subscribers for which we get valid message ids and only 50K impressions for them even when the push expiry is 10 days. This is a really sad ratio. We also have put on our entire website https and have put a mechanism to get back their dev tokens if they visit again and we see we dont have their token even though they had subscribed earlier. 


Describe infrastructure request/issue:


If this is a new buildbot slave:
Example slave: an existing working slave name(s), if any
OS:
Version:
Bitness:
Waterfall:

If you need to contact the on-duty trooper, see: https://chromium.googlesou
rce.com/infra/infra/+/master/doc/users/contacting_troopers.md

 
Can you explain what an "impression" is in this context / how are you getting 50k?

Can you provide a link to the site you are referring to that is seeing these stats?
Hi Matt,

This is the site in context https://notify.buyhatke.com/. 

Impression is defined when a particular device tries to fetch the push data from an API. As soon as it hits our server we count it. 

Components: -Infra Blink>ServiceWorker

Comment 4 by horo@chromium.org, Apr 30 2016

Components: Blink>PushAPI
Components: -Blink>ServiceWorker
Labels: -Restrict-View-Google
I think this wouldn't directly be relevant to Service Worker, so let me remove the label.
Owner: peter@chromium.org
peter@, could you triage this?

Comment 7 by peter@chromium.org, May 10 2016

Cc: miguelg@chromium.org owe...@chromium.org
Hi Gaurav,

Matt has previously answered part of your question on http://stackoverflow.com/questions/36649838/push-notification-not-getting-delivered-via-service-workers.

You could send messages to GCM using the XMPP protocol and request delivery receipts. This enables you to further instrument how many messages reached the device.

https://developers.google.com/cloud-messaging/ccs

> Also can information be passed if there any cache clearing or anything that took away the device token of that device ?

Uses clearing their cache is deliberately not visible to the website, however, push subscriptions will be unsubscribed as part of this. When sending a message to GCM, your server can look at the return code to determine whether the message was accepted.

This does not apply to third-party "cache clearing" mechanisms that blow away Chrome's data. There isn't really a good solution for that situation.

Comment 8 by joh...@chromium.org, May 23 2016

Status: Archived (was: Untriaged)

Sign in to add a comment