T-Stats Recipe

Conversely, you could create a dynamic list in Tessitura with "Unique Performances = 1" and then load that list into t-stats as a filter and be able to automatically look at each performance and how many new buyers/tickets/revenue you gained from that event.

You might need to narrow that list by season to stay within the filtering threshhold on T-Stats (our threshhold is now 25,000 but it started at 10,000, which was too limiting). You'd have to define what "first time" means -- is it first time ever? First time in five years? Three years?  But that would be another way to get at that info and not have to create a new list for each performance/production.

Hope that helps.

Sara Billmann, UMS

On Fri, Sep 30, 2016 at 12:42 PM, Christopher Cuhel <bounce-christophercuhel9903@tessituranetwork.com> wrote:

Hi Nicole.

As my brain thought about this, I think you may have to create a list in Tessitura first and then use that as a filter in T-STATS. You could create a list of patrons who only have that one performance run on their account. From there as you set up a tickets or seats cube, you could use that list as a filter and see how many tickets were sold and how much revenue you gained from them.

Sadly, I can't think of way to make a criteria (without some custom work) to be able to do all this right in T-STATS.

Best,

Christopher Cuhel, The 5th Avenue Theatre