Analytics Workspace: Sort out the trending of percentages

A_Wathen

MVP

09-11-2016

If I have a table as below I can easily and quickly trend out the volumes [A] by right clicking and selecting "trend selection".

 

The is no equivalent for trending the percentages [B]

 

Trending percentages.png

This leaves creating calculated metrics as the only way to achieve the desired outcome.  As a result, we are facing a significant  proliferation in calculated metrics, which is quickly becoming unmanageable.

 

For instance, just to be able to trend the above requires the creation of 6 calculated metrics… (% IE, % Chrome, % firefox, % edge, % safari, % other browser)

 

We're heading into hundreds of calculated metrics that could be entirely avoided.  Please help!

4 Comments (4 New)
4 Comments

Brandon_George_

Employee

10-11-2016

I believe this is a duplicate of another idea on the Idea Exchange - trending by row instead of by column (very related).  We are actively considering that one - can you see if that would address your issue as well (I think it would).

A_Wathen

MVP

10-11-2016

Thanks for coming back and asking me to clarify - really appreciate the fact that you are not making assumptions.

 

 

It's not a duplicate.  I will try to explain...

 

The reason the other idea does not solve this is because of the denominator used in the calcuation is different. (row % vs column %)

 

In the screen shot (figure 1) below I've tried to illustrate the issue.  I've calculated row percentages in 'red'.  As you can see the 'row' percentage is not equivalent to the 'column' percentage calculation

 

Unfortunately, the far more useful calculation is the calculation that is done for the column.

 

The only way I could get the row percentage to work would be to insert an "other browsers" column by building a new segment.

 

Trying to use row percentage to fix this issue only swaps my calculated metric proliferation issue for a 'other' bucket segment proliferation issue

 

Figure 1:

 

column vs row.png

Brandon_George_

Employee

10-11-2016

Thank you for this clarification - we will definitely consider this.

A_Wathen

MVP

10-11-2016

Thanks, in my haste to reply I forgot a pontential 2nd reason why the % row approach doesn't necessarily work which is to do with dynamic vs static values.

 

Take the scenario where the requirement is to trend the percentages for the 'top 5' browsers for the last 90 days.

 

The 'row %' approach requires you to hard code the 5 items that are to be tracked as column headers (i.e. they won't dynamically update if the 'top 5' changes) so it can't be done.

 

However, the dimension placed down the left hand side of the freeform table dynamically updates to show the top 5 for whatever period is selected.

 

Hope this makes sense?