Allow Global Shared Calculated Metrics using Instances and participation/visits for props

Avatar

Avatar

RobertBlakeley

Avatar

RobertBlakeley

RobertBlakeley

05-07-2012

Issue:
Calculated metrics for Instances and Participation are available for props at the report suite level to be created by each user individually for each report suite. However, they are not available for Global Shared Calculated Metrics. This diminishes to some extend the utility of Shared Calculated metrics.

 

1. Although Instances in v15 is the equivalent of PV in v14 and the Custom Traffic (prop) default metric in v15, v15 does not support creating any Global Shared Calculated metrics for props using Instances through Admin. (Individual users can create the metric for each report suite). This should be available as an option for Global Shared Calculated metrics.

 

Instance based calculated metrics (e.g. instances/visits) for props can be created in a given report suite and marked as Global. The metric will then be visible in the Global Shared Calculated Metric list. However, for any given report suite the metric will be available only for Evars and the Pages report (and Pages does not have Instances by definition). This is just confusing.

 

2. Additionally, metrics using participation are not supported by Global Shared Calculated metrics for props. E.g. As a media site one of our KPI metrics is prop based Page Velocity, participation/visits using the recommended Omniture approach for this metric. Individual users can create the metric for each report suite. This should be available as an option for Global Shared Calculated metrics.

 

This metric for props can be created in a given report suite and marked as Global. The metric will then be visible in the Global Shared Calculated Metric list. However, for any given report suite the metric will be available only for Evars and the Pages report and not an Custom Traffic reports.

 

 

My guess is that both issues stem from participation and instances being evar based rather than prop based. For example, in the pvc calculation, evar visits and prop visits are likely different columns in their DB. That is where the system is failing. It can see participation in props, but not the correct visit. The individual report suites can figure out what visit version to use based on what report you are looking at. The Global calculated metrics cannot.

1 Comment (1 New)
1 Comment

Avatar

Avatar

justin_grover

Employee

Avatar

justin_grover

Employee

justin_grover
Employee

22-06-2015

This should now be resolved with the latest release.