I'm working on moving the reports I use regularly in T-Stats over to the new Analytics software and am having difficulties getting the data to match for the ticket counts.
In both T-Stats and Analytics, I've created a report that has the production in the rows and the price type category in the columns with the season and title as a filter. In T-Stats, I've been using "Num Tickets" to see how many tickets were sold by price type for each production, but I haven't been able to find a number that matches in Analytics and "Num Tickets" isn't an option for the values. I've tried "Total Ticket Count" and a handful of others. They all give me the same number, but none match our T-Stats reports. The revenue numbers do match in T-Stats and Analytics.
Does anyone know why the data for ticket counts in T-Stats and Analytics might be different?
Thanks!
I am curious about this as well!
You did not say what version of Tessitura you are using. Are you on version 15.0.x or 15.1.x
There is a difference in the unit of analysis or grain of the data between these two versions.
When you add pricing you may be getting duplicate counts if you are counting rows. "Total Ticket Count" should be accurate. However some pricing layer rows may have ticket counts of 0. (I think that it's only the base ticket layer that has the ticket count in version 15.1.x)
I believe that there is a conversation over in TAMATO group about these multiple like per ticket issues.
We are using version 15.1.4.54929. The data in the new analytics has fewer tickets than T-Stats or the other sales reports we're pulling out of Tessitura. I'm not sure why, for example, that the Performance Sales Summary and T-Stats would say that we sold 1,459 subscription tickets to a concert and Analytics says we only sold 1,199.
Jon Miles Just a guess is that you are filtering out some rows base price layer somehow.
I'd suggest that you start with a clean pivot table in a new dashboard. Use filtering to get to only a single performance. Make sure that attendance and dollars are showing up accurately. If not open a support ticket. Otherwise, check some more performances.
If on this very simple of filters then rather than filtering more break out by rows the things you might want to filter by and use column grand totals. To see what is going on. Then break out further. Only once you understand what is going on with the rows that you are breaking out. Then try filters.
Just my $0.02. Good luck.