Analytics: Seats vs Ticket Counts

In this context a seat is inventory, essentially all the boxes you can see in the seatmap, sold or not. A ticket in this context is a sold sub-lineitem; it may be unpaid, partially paid, or completely paid (or a comp), but essentially someone has that seat in an order. Unseated slis will potentially also affect the ticket count if you have them. That's it in a nutshell. HTH.

Thank you!! Very much appreciate this explanation!

In this same/similar vein, what is the difference between ticket count and count of unique ticket ID? I get a slightly different number for the two and I'm not sure which one would be more accurate.

And after posting, I found the answer in the help system. Ticket ID will only count a printed sub line item, but Ticket Count will give me all sub line items.

Thanks for including this Michael. I've mainly been using ticket counts, but could see the possibility of using unique ticket IDs in the future.

Sometimes it is hard to locate in the documentation, so I appreciate you including it here.

Absolutely! Love it when I answer my own question, shortly after asking it. In case you were interested, here's where I found the answer.

https://www.tessituranetwork.com/Help_System/Content/Tessitura%20Analytics/Data%20Dictionary/Seats%20and%20Tickets%20Cube.htm?_ga=2.76737042.60213772.1599066223-552316895.1586979106

Does Ticket Count only count tickets that are in certain status, such as TPD or SPD? I'm trying to ascertain whether there's any double-counting due to returned SLI's that have been exchanged. Thank you!

Voided performance sub-lineitems are not included in Analytics. You can display sli status in your dashboard. If you're troubleshooting a bespoke dashboard, that may be helpful. It's in the Seat and Ticket Details dimension.