Closed nin9creative closed 11 years ago
@nin9creative - This is exactly what i've been thinking and trying to implement with countly. With this type of information from your apps and games you can make really big decisions by having all the right information at your finger tips in a flash, because Countly presents this information instantly. I'm playing around with the code now...And thanks for pointing me in the right direction. :+1:
Not sure if you saw I posted a bit in the other thread.
This is an excellent thread @nin9creative! :)
I'll just cross reference the issue where we track the feature. #332 ;)
@fturner19 What's great about using a self hosted solution such as Count.ly is that if you are a developer working on different magazines for different clients - you can sell the analytics as part as a value added option to your service.
Countly has the ability to create users that have read only and or admin access to specific applications that Countly is tracking. You could provide the login information to your client contact, and they could see in real time the use of their magazine and gather metrics around it. Pretty powerful.
Some events related to pages would be useful to know where the reading time is spend in an issue. For example: time spend on the page, how often the page was displayed, ...
For a website, we can track also some interaction inside a page with appropriate trackers. Can it work inside an app?
@nin9creative - True indeed! I've already set up a couple logins for clients that i'm currently working with. What I like about Countly is it's seamless integration with Baker. Just add a few lines of code and you're off to the races. Being able to add custom Events and get instant results is what gets me excited. The Baker community should be adding countly to their builds to track their apps stats. And thanks again Andrew for pointing me in the right direction.
@nin9creative - Looks like The Countly Team added your installation video to their support section and pushed it out to all self-hosted versions. Take a look at it:
Ha :) Cool.
Ok, a first implementation is now on master, let's keep the discussion consolidated on the feature tracking issue, here: #332.
Awesome!
Andrew
From: Davide Casali notifications@github.com To: Simbul/baker baker@noreply.github.com Cc: Andrew andrew@nin9creative.com Sent: Wednesday, August 7, 2013 11:15 AM Subject: Re: [baker] Important Metrics to Track for Baker Applications? (#1058)
Ok, a first implementation is now on master, let's keep the discussion consolidated on the feature tracking issue, here: #332. — Reply to this email directly or view it on GitHub.
I was just curious what types of Analytics and event tracking would be useful for those publishing apps.
I know the basics would be nice, events such as... Some of these would probably be more accurate by using the iTunes Connect reports (for In App Purchases) however it may be useful to aggregate in a single view for reporting purposes.
Opening an Issue Downloading an Issue Archiving an Issue Refreshing the Shelf Making a Single Issue In App Purchase Making a Subscription Purchase (Paid or Free) *etc...
Just curious what people think.