Remove unspecified's from correlation reports

adierl

17-02-2010

When a correlation is used and there are not always values for all elements of the correlation, you have to deal with "Unspecified" in the report. While it might make sense for some reports (did not find anyone to far) it destroys reporting of many others. The totals is wrong as well as the chart is useless since Unspecified makes >90% in most cases.

 

E.g. if you have a variable to store a business unit (prop1) and have a 5 item-correlation (prop1, pages, downloads, exits, keywords)

The breakdown to see all exits for a single BU, will count all (page+download+keywords)-instances as "Unspecified".

 

 

corr_unspecifieds.png

 

No standard user can understand "Unspecified" here.

 

Or even easier, if you have a correlation Pages<->Keywords, you will see any PageViews without a keyword as "Unspecified". Makes sense?

4 Comments (4 New)
4 Comments

RobertBlakeley

21-02-2010

But we use this value for debugging.

pfg51073

10-03-2010

Make it an option, then.  I agree with this post.  I'm constantly creating custom reports that filter out the "Unspecified" values in these reports (which also messes up the totals), or having to explain to people looking at the correlated reports that 90% of the usage is "Unspecified" because that particular property isn't relevant in the case they're looking at.

xptr99210

26-05-2010

well, the filter does not even work anymore...I think it died after the last release.  It was nice but as pointed out above the total is still wrong.

pfg51073

01-09-2010

Yes, I noticed that, too.  So, no filtering and I'm back to having to explain the meaning of "unspecified" to everyone.