Hi all,
We are wondering what is the Package Seat Key criteria in Analytics? and what does it represent?.
I tried to find it on TessituraNetwork.com, but could not find anything useful.
Could someone please explain what it is and how do I see those data in Tessitura?
Thank you,
Tom Nguyen
Literally, package Seat Key is the package lineitem ID concatenated with a ranking of the sublineitems within that pkg lineitem. The package lineitem id is not particularly accessible via the front end, and the second value is calculated. It does not exist independent of the data warehouse.
Functionally, the Package Seat Key is present in order to enable calculations related to package seats (as opposed to performance seats). So while you might have a package containing 6 performances, someone buying 2 seats to that package will end up with 2 unique Package Seat Keys. If your analysis were to look at how many tickets that constituent had, you'd end up with 12. However, if you were evaluating how many packages they'd purchased, you'd want to see 2, and consequently you'd want to be looking at a distinct count of Package Seat Key. I hope that helps shed some light on it.
Thank you Mr. Freeman. That helps a lot!
Hello, I am working with Package Seat Key in my season dashboard to count the number of packages, however, the count is inflated by 6. The sales is correct so I'm not sure where I have gone wrong. Do you have any ideas?
I should mention too that I am comparing the number to the Package Sales Report that runs automatically between 3-4am. My dashboard updates at 4:22am. I thought it could be because someone purchased when the two didn't overlap but not sure how to check that.
Amanda, were you able to get to the bottom of this? I'm experiencing the same issue. I can get the number to change slightly if I add a filter for "Order Paid Status" to eliminate orders with no payment, although that shouldn't be necessary since our default settings are already set to ignore unfulfilled rollovers.