Welcome to the Official BlackBerry® Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

BlackBerry Analytics Service

Reply
Developer
dkonigs
Posts: 122
Registered: 07-25-2008

Tracking app settings

My app has a lot of configuration options available to the user, and I'd like to be able to gather some data on which ones users are actually changing.  (and if so, what the most common settings are)  Given the limited action-oriented nature of the API, what is the best way to do this?

 

My initial gut reaction would be a custom event with a hashtable of key/value pairs, but I've gotten the impression that the hashtable parameter is really just a way of passing standard Webtrends API arguments that aren't directly exposed through your API.

Please use plain text.
BlackBerry Development Advisor
twindsor
Posts: 269
Registered: 07-15-2008
My Carrier: Bell

Re: Tracking app settings

The Hashtable is intended for custom events mostly, but the necessary reports are not included in the level of Webtrends account that you get for free with the BlackBerry Analytics Service. 

 

If you'd like to capture these options, I'd suggest using the Screen names, or ButtonClick events to capture your data. Or, perhaps you don't use one of the other types like Product Views and you could repurpose those methods.

Tim Windsor
Application Development Consultant
Please use plain text.
Developer
dkonigs
Posts: 122
Registered: 07-25-2008

Re: Tracking app settings

I'm basically looking for a way to track settings on a percentage-of-users basis.  (as opposed to overall event counts)

 

For example, I want to answer questions like:

"How many users enable option foo, versus disable option foo?"

"Which of the 4 possible values for bar is most common?"

"How many bazes do most users configure?"

 

(Most things are of a boolean nature, but not all of them.  But the key is that these are per-user stats, not per-session stats.)

Please use plain text.