[TIMOB-18851] TiAPI: Allow developers to opt-out of sending certain analytics events
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-06-20T00:22:05.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 4.1.0 |
| Components | TiAPI |
| Labels | analytics |
| Reporter | Ingo Muschenetz |
| Assignee | Hieu Pham |
| Created | 2015-04-24T17:55:47.000+0000 |
| Updated | 2017-03-20T20:18:21.000+0000 |
Description
There are occasions where app developers may not want to send certain events to the analytics server. One example use case is that the app needs to enable location services, but not send geo events to PEM.
Our proposal is that in tiapp.xml (and also at runtime), the developer is able to set a list of events to filter out:
.filter("ti.geo", "app.nav")
We may wish to _not_ allow them to filter some events like ti.enroll if that then breaks down the rest of the analytics system.
[~mgadiya] This was a request from Swire Beverage during the pre-sales phase. They wanted to be able to collect Analtyics Events but disable any location tracking event types. This is primarily due to privacy concerns.
If we have begun work, we should mark this as in progress.
Android https://github.com/appcelerator/titanium_mobile/pull/6921 iOS https://github.com/appcelerator/titanium_mobile/pull/6923
Swire may no longer be in the mix so unless we feel others need this I don't think we should consider it a priority now.
I think it's still worth doing to address the Gulfstream issue. Thanks!
Reviewed both PRs, and left some comments. Ti.Analytics.filterEvents(['eventName']) is tested to work on both platforms. *To note:* Currently on sdk, only *ti.geo* event is the only analytics event integrated in it. there is no nav events being sent to the server.
Both PRs merged.
Closing ticket as fixed.