<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I think developers must build their own back-ends and keep track of what they do.</div><div><br></div><div>This will be always the more flexible solution.</div><div><br></div><div>IMHO you must focus on the core of building a reliable and powerful push send service (includind the documentation part).<br><br>Enviado do meu iPhone</div><div><br>No dia 07/04/2014, às 13:09, Burr Sutter <<a href="mailto:bsutter@redhat.com">bsutter@redhat.com</a>> escreveu:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><br><div><div>On Apr 7, 2014, at 1:17 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Hello,<br></div><div><br></div><div>for a first round of collection some more data around the usage of the push server (aka analytics/metrics), I'd propose we keep it very simple.</div><div><br></div>
<div>Overall, I see one major area of interest:</div><div>*metrics around push messages being sent:<br></div><div>- time of sending (using timezone of the server?)</div></div></blockquote></div><div><blockquote type="cite"><div dir="ltr"><div>- group of receivers (e.g. everyone or the provided cirterias(e.g. alias, categories,...))</div>
<div>- payload (the entire payload, including custom keys - not only alert, sound, badge etc)</div><div><br></div></div></blockquote>As a developer, I wish to know if my 3 test devices all registered properly.</div><div>As a developer, I wish to know if the push notification was sent to all 3 test devices properly (at least delivered to Apple/Google properly)</div><div>As a developer, I would like to know what were my past messages</div><div>As a push administrator, a business unit representative (e.g head of sales, warehouse manager) is going ask me if a particular message was sent to a particular user (alias) or user group (aliases or category).<br><blockquote type="cite"><div dir="ltr"><div><br></div><div>This is a nice feature, and would enrich the UPS.</div><div><br></div><div><br></div><div>
However, I can see also some interest around device specific metrics:</div><div><br></div><div>Today we obivously store all the registered devices, but we also remove them from the database table if needed (to not send messages to phones that would no longer receive them anyways).</div></div></blockquote>I can see people wanting to just archive instead of delete those records - interesting data points would be:</div><div>- any commonality in device type</div><div>- a trend in date/time of removal</div><div>- ratio of added/removed (user opted in vs out)</div><div><br></div><div>Is it possible to distinguish between app uninstall vs push notification disable (where the app remains installed)?</div><div><br></div><div><blockquote type="cite"><div dir="ltr">
<div><br></div><div>Something that would be interesting as well, might be the following data:</div><div>- how often was an app has reached the push server (note: every time the app starts, the metadata of the server is being updated (see [2])</div></div></blockquote>would this be a good proxy for letting me know how often an end-user is using the app?<br><blockquote type="cite"><div dir="ltr">
<div>- number of device-tokens / registrationIDs that have been removed, when receiving errors from Apple/Google (see [3] or [4])</div><div>- number of devices, that were activly removed using our APIs (supported only on Android/SimplePush due to Apple policy, see [5])</div>
<div><br></div><div><br></div><div>While the initial focus should be around the message related metrics, capturing some device data is nice too.</div><div><br></div><div><br></div><div>Any thoughts ? </div><div><br></div>
<div>-Matthias</div><div><br></div><div><br></div><div>PS: Oh, for the longer run(...), I'd also like to see metrics like "was mobile app opened due to a push notification". BUT that also requires some more work/reseach on the client Push SDKs. But seriously, this is not a priority for the next few months! </div>
<div><br></div><div><br></div><div><br></div><div><br></div><div>[1] <a href="https://issues.jboss.org/browse/AGPUSH-116">https://issues.jboss.org/browse/AGPUSH-116</a></div><div>[2] <a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L98-L112">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L98-L112</a></div>
<div>[3] <a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L87-L94">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L87-L94</a></div>
<div>[4] <a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L93-L94">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L93-L94</a></div>
<div>[5] <a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L117-L119">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L117-L119</a></div>
<div><br></div><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>aerogear-dev mailing list</span><br><span><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></body></html>