We have an Android application that consists of two main components: The main user interface (several types of activities) and the background service work endlessly without direct interaction with the user interface (both for writing and reading from one database). The user interface is often used by users, but not so much. The background service should always work.
We are currently using Flurry, but we did everything wrong. Since events come from both actions and the background service, this distorts the settings for the session, active users, etc. We want to improve the situation.
We decided to replace Flurry with Google Analytics (SDK v3 has improved significantly since the last study). We created two different properties with different tracking identifiers (one for the user interface and one for the service). Our plan is to use EasyTracker with a user interface (much easier to measure session time and screen flow) and use a manual tracker for maintenance ( https://developers.google.com/analytics/devguides/collection/android/v3/advanced#multiple -trackers )
We have two main problems:
- Is it possible to separate an interface and a service from two different properties?
- Should we measure session time for a service? We want to know how many users actually start the service, but the session time does not matter in this case. Is there any other event that we can use to find out how many active users of the service exist?
Any thoughts, comments, suggestions or ideas will be greatly appreciated.
Thanks Alik
source share