Try Ticket Count and Seat Unsold Count with a filter Seat Hold Code of None.
It depends on what holds you have (if any). The total seat count would be the ticket count + seat unsold count. Also, sometimes it displays the sum of something as the total. As in, the SUM(Ticket Count) is the same as [Total Ticket Count].
I'd start there and then start adding hold codes. Maybe someone has added some that you didn't know about.
Here is an example:
One more thing, remember that the data in Analytics is one day old (unless you are self-hosted and have it set to update more often). In other words, any changes you made today will not show up until tomorrow.
If you get close to the target, use the House View in Season Manager to look at an individual performance. Maybe something will jump out at you.
I know that one issue can be that if you have a seat on hold, but have rights to break that hold, means you can sell that ticket WITHOUT breaking the hold.
For our large fall event, I had to daily check the House View for any of seats with tickets sold but also still had a hold so that the counts would not be thrown off in Analytics. I would break the hold and then on the next day the numbers would add up properly in Analytics.
Sorry, I keep thinking of one more thing.
Sometimes tickets are in an in-between state (maybe in someone's cart?) at the time when Analytics is doing its update of your data. This can also throw off your numbers. This issue usually clears up the next day (and then you notice that another perf has that issue, lol).
Hi Anh,
If you talk to Support, please follow back here with the resolution for the thread. In the meantime, I'd expect a SUM of the value called [Seat Count] to give you that number. From help:
Seat Count: The number of seats (inventory) for a product. Only price layers in the Ticket Price price category are counted for this field. If multiple Ticket Price price layers exist for a performance, the Ticket Price price layer with the min start date and min price layer type rank is counted. If you break out counts by price layer, layers in all other categories will have a count of 0.
One caveat to that is this setting: Include Blacked Out Seats. When set to No (the default) seats that are held with a blackout hold code are not included in Tessitura Analytics. Setting this entry to Yes will include seats held with blackout hold codes in unsold seat counts and capacity calculations. If you include them, you can filter them out with a Hold Code filter on the widget or dashboard that is set to exclude the kill holds.
I would avoid using Ticket Count as a method of counting the sold segmentation of your seat capacity, as a single seat could be sold multiple times (benevolent returns), and a ticket could be unseated and still count toward an overall sold ticket count.
A similar issue can occur with distinct counts of Perf Seat Key, Seat Key, and Seat ID as tickets without seats will still have a placeholder value (e.g. -999999) that will contribute to the overall total unique count of values.
Best,Chris
Thanks for trying that for me Anh. That's not expected and a support ticket is in order. As a work around for non-GA seat maps, try:
( [# unique Perf Seat Key] , [Seat Key > 0] )