Hello,
Our price points have a large variance such that our AOV doesn't well represent the bulk of our transactions. I did create segments of order value buckets so that I can us to directionally make conclusions, but I was hoping there was a way to achieve true Median Order Value for a date range. Is there any way I can do this?
Solved! Go to Solution.
Views
Replies
Total Likes
ok so I think you need to provide the Mdian as a metrics breakdown of something else.
Raw in a free form like that may just sum.
If you do by
product -> revenue -> median revenue
I would expect
product1 -> revenueX -> median revenueAA
product2 -> revenueY -> median revenueAA
product3 -> revenueZ -> median revenueAA
What if you tried to make a calculated value? Use math function against a revenue dimension.
Yes, but when I create that and add it to a table it seems to simply provide a SUM of the date range selected for revenue and not a median at all.
These 2 values are the same:
Views
Replies
Total Likes
ok so I think you need to provide the Mdian as a metrics breakdown of something else.
Raw in a free form like that may just sum.
If you do by
product -> revenue -> median revenue
I would expect
product1 -> revenueX -> median revenueAA
product2 -> revenueY -> median revenueAA
product3 -> revenueZ -> median revenueAA
Ok, so that worked when I used my Purchase dimension so I did get a static number for the date range - which is a lot better than nothing. Unfortunately it doesn't let me trend that value over time in a time series. Not sure if that's possible.
Views
Replies
Total Likes
Hey @JFN1 - Are you capturing order value in a prop or evar ? Do you capture Revenue or Order value ?
Do you have a calculated metric ? You need to disable the "include_zeroes option" as shown below and then you would be able to see the median revenue :
Views
Replies
Total Likes
Views
Likes
Replies