Percent Change Year over Year column for metrics listed vertically | Community
Skip to main content
New Participant
September 28, 2021
New

Percent Change Year over Year column for metrics listed vertically

  • September 28, 2021
  • 2 replies
  • 881 views

There is a FUNDAMENTAL NEED to have a year over year percent change column for metrics listed vertically (in the order we want them listed) with current year first, prior year second, % change column third For example:

 

metric name:           Period A current year totals :              Period B prior year totals :             % change difference

metric name:           Period A current year totals :              Period B prior year totals :             % change difference

metric name:           Period A current year totals :              Period B prior year totals :             % change difference

metric name:           Period A current year totals :              Period B prior year totals :             % change difference

 

If anyone out there has achieved this please let me know how you did it.  

   

2 replies

Linda58Author
New Participant
November 3, 2021

@_bel_ Thank you for this but I do have the same in visitor based metrics. Adobe just needs to fix their calendar and give us the ability to do year over year comparisons with percent change that applies to the entire report and not one metric at time which is what it does now and is just asinine. As well the metrics need to have the ability to apply filters to them. And we also need to be able to schedule automated reports that will return the entire data set and not just a portion of up to 400 rows. If they did this we would have a pretty awesome tool, but the way workspaces functions now is almost to the point of being ludicrous to call it an analytics tool.

_bel_
New Participant
October 26, 2021

This isn't a perfect solution and won't work for all possible metrics, but you can create hit-based segments for each metric where the logic is "Metric X exists." 

 

You should be able to use occurrences as your metrics. If you want more precision, you can create a calculated metric - add each metric with its corresponding segment.

The final table will look like this 

There are some metrics that this doesn't work for, as mentioned. Visits/Unique visitors is a big one, because those metrics aren't hit based. If you have an event or evar you could use as a stand-in that could work, or you can also swap the whole approach to visits where x occurred and use visits as your only metric.