BlackBerry Analytics Service

[dnepr]

I've been using this method to denote certain content being viewed as follows:

 try {                   

WebtrendsDataCollector.getInstance().onContentView("MainScreen/",   "ScreenN", "Opened ScreenN", null, "Screen Content View");             

  }

catch (IllegalWebtrendsParameterValueException err)

{                   

WebtrendsDataCollector.getLog().e(err.getMessage());         

}

So whenever a content is screen is shown, a content view event is generated.  I have about 10 screens using this (Screen1-10 in example).

What I see in reports does not make sense:

1. "Categories by Screen" report shows the "Screen Content View" category, drilling down to it.. it only shows a single screen.   Nothing else.    All screens have been accessed multiple times, but only a single screen is shown under the category.

2. "Events" report shows ALL of the corresponding events with proper event names (i.e. "Opened Screen1")

3. "Categories" report simply shows some basic data without ability to drill down to see what events and their number have been fired under that category.   Not very useful.

1 and 3 sure don't look like expected behavior.

[twindsor]

Checking with Webtrends. I'll let you know if they need anything to figure this out.

[dnepr]

Thanks.

I am seeing the same thing with product views. Only a single Product SKU is being shown in the report out of about 8.

[twindsor · Accepted solution]

You'll want to change your Event Path so that it's unique. For example:

try {                   
WebtrendsDataCollector.getInstance().onContentView("MainScreen/N/",   "ScreenN", "Opened ScreenN", null, "Screen Content View");             
  }
catch (IllegalWebtrendsParameterValueException err)
{                   
WebtrendsDataCollector.getLog().e(err.getMessage());         
}

 Where N is either number or string or some kind of unique identifier.

For the categories, here is their explanation:

We would show one session for Category 1, but both Screen A and Screen B will each show one session.

The categories report is intended just to show the categories and not what is in each category.  One reason for this is that if we list sessions for each screen below the total number of sessions for the category, the numbers wouldn’t match.  This is because the number of sessions for categories is not simply an aggregate for the number of sessions for screens within that category.  For instance:

Screen A and Screen B are both visited in a session and are in Category 1.

We would show one session for Category 1, but both Screen A and Screen B will each show one session.

[dnepr]

Thank you, I will apply the fix and report after it is tested.