Hi everyone!
It was so great to see all of you last week at the TUG meeting. We have some answers for you on the questions raised during the analytics presentation.
Will the heat mapping feature still exist? Specifically by postal code?
Heat mapping to me implies the shapes that are colored as hot or cold are geographic regions. If that specifically is what is meant, then Analytics has heat mapping down to the State grain only. However, Analytics can render postal code dots that are colored and sized based on the data.
Is transaction date a filterable item?
Yes, when using the Finance cube.
Is it possible to customize field labels on report output to be less performing arts specific (ie performances, tickets etc)?
Yes, any field name label can be renamed, and can be named instance of its use to another.
Currently unpaid order detail does not hit the GL in Tessitura. Will analytics be able to access this data?
Yes, when using the Seats and Tickets cube, unpaid order details are available. Optionally, unfulfilled rollover orders may also be included, but are not by default. Unposted transactions are available in the Finance cube, they have a GL Entry Type of Not Posted. If you were analyzing your data by GL Segment, the unposted transactions will show as (none)
The Zoo uses waitlists. Could the pulse feature be configured to send an alert when tickets are available in one area performance and purchased in another (ie waitlist)?
Yes. One would create a formula right in the front end to return either a flag that such a scenario exists and add that to Pulse. One might also put that in the context of a Waitlist dashboard that shows details of who has how many waitlist spots by performance along with how much available inventory there is to slot them into.
Please don't hesitate to reach out here or via a TASK ticket if we can answer any further questions. We anticipate that v15 will be released very soon and are excited for all of you to get started with Tessitura Analytics.
Thanks!
Patrick