Catering for different stores about countly-server HOT 6 CLOSED

Just to be sync with what you are trying to see in the future releases, can you send an example of any use-case? Are there any other services providing this functionality?

from countly-server.

In terms of a use case, we are launching on a number of different sales platforms (shop fronts), so different offers may be available at different times on each store.

In terms of other people offering this service, mopapp and appfigures do a similar thing with sales figures. Effectively in the area of analytics no-one is offering this service (but also no analytics service allows the same API key to be used across platforms)

The brief behind it is that different platforms perform differently to pricing changes for in-app purchases, so each individual store needs to be seen effectively as either a different platform or a subcategory in a platform in order to evaluate performance efficiently.

from countly-server.

Do you think it's possible to understand within an application the origin of download (e.g Android Market, Appstore for Android, etc) - using the same API key, so you only generate the APK once and system will understand which market is used to download that app?

from countly-server.

Yes, that would be fine in most situations and with android especially it can be added into the build scripts to automate it.

from countly-server.

I'm not sure how to identify which store is used (if any - user may install the apk via adb shell), to download a particular application - without using different APP keys. Will dig in further.

from countly-server.

Pretty much every store will have a slightly different configuration, so
this could be passed back to countly as a parameter (dynamically updated by
a build script)

from countly-server.