Hello friends!
I am trying to create a widget that shows how many tickets were sold for all shows in our season each day 30 days before the season ends. This is currently what I have built and it is not giving me the numbers I’m looking for:
This is what I’m hoping to do in Analytics but have only been able to accomplish in Excel (all the data was extracted from Analytics):
Using Order Date > Date > Days in date gets me the correct number of tickets sold that I’m looking for. But I can’t compare seasons this way because it’s using the calendar year. In excel I can manually shift the numbers so that the last day of the festivals line up. Using any of the ‘Order Days Prior to…’ measures do not give me the results I’m looking for.
Does anyone have any ideas how I can manipulate the days/dates in Analytics so I’m able to do what I did in Excel? I appreciate any advice you might have!
Cristal
May I suggest that you duplicate your graph in Analytics and then change it to a pivot table? I noticed that your graph data does not seem to match what you show in your Excel version. Once you figure out the filters to get the data to match, duplicate it and then change it to a line chart.
Also, I'd suggest you add a column in your pivot table that counts unique SLI ID's and compare that number to the Ticket Count. If one of your performances has more than one price layer, the Ticket Count can be off. We only use 1 pricing layer and still run into that issue. Every so often we notice that a performance has more than one price layer even though within the application it only has one. As a result, I now always add a value that count unique SLI ID"s to every pivot table to compare to Ticket Count value. Basically, I've stopped using Ticket Count.Another option could be to delete the Break by part of the chart and then use Filtered Values for both seasons.Filtered Values (tessituranetwork.com)
Hi Cristal,
This idea might interest you: (+) Analytics Season Level Start/On-Sale Date - Ideas - Ideas - Tessitura Network. It sets the stage for relative order date from season start or end.
For now I think what you're doing will continue to be your best option without a customization, which is an option that could provide exactly what you'd like in Analytics.
Thanks, Neil. I used filtered values and it definitely got me closer.
This is exactly what I'm looking for! Thanks, Chris. It has definitely received my vote and I will look into customizations.