Hi everyone,
A few of us had a chat about visitor figure tracking in Tessitura at TLCC London a few weeks back so I thought it might be helpful to throw this question out to the wider group.
As part of our visitor reporting, we monitor visitor attendance across a range of data points. Some of these are data we are already collecting in Tessitura (admission ticket purchases and attendance, exhibition and event ticket purchases and attendance) and others are data that is collected outside of Tessitura (people counting software, manual clickers, free school visits, etc).
We are embarking on a project to review the data points we report on and as part of this I would like to explore the potential of collecting more, if not all, in Tessitura. At present we have a number of spreadsheets where we plug in figures each day which risks human error and in users changing the figures regularly resulting in a lack of faith in the figures. Ideally we'd capture the data in Tessitura so we can use Analytics and reach a single source of truth for our visitor numbers and track our progress against targets.
I know that some ideas out there include hard coding data into Analytics, using custom tables or creating daily performances where people counting figures can be recorded through selling tickets. Can anyone share their experience of using Tessitura for visitor figures reporting and the strengths and weaknesses of their approach?
Many thanks
Hannah
Hi Hannah,
I think we had a pretty extensive chat re: Targets tracking in Tessitura. I'll write a few notes below:
We are using analytics functionality to import our footfall targets into a widget on a budget tracking dashboard. There are other less manual solutions, but this works fairly well for us, we just have to currently refresh the targets quarterly as Analytics isn't really built to hold this many manual case statements. I'm sure there might be a better way of doing it along the same lines but we are are just doing the best we can with the tools we've got!
Our widgets look like this sample below-- the gold line is the footfall targets that we have manually imported into Analytics and the red is a really simple Tickets Sold filtered by prod season:
The formulas I am using to import the targets are as follows, for example:
CASEWHEN [Total Calendar Day Of Year] = 203 THEN 7672WHEN [Total Calendar Day Of Year] = 204 THEN 7672WHEN [Total Calendar Day Of Year] = 205 THEN 7658WHEN [Total Calendar Day Of Year] = 206 THEN 8297WHEN [Total Calendar Day Of Year] = 209 THEN 7599WHEN [Total Calendar Day Of Year] = 210 THEN 8142WHEN [Total Calendar Day Of Year] = 211 THEN 7657WHEN [Total Calendar Day Of Year] = 212 THEN 7793WHEN [Total Calendar Day Of Year] = 213 THEN 9337WHEN [Total Calendar Day Of Year] = 216 THEN 8152WHEN [Total Calendar Day Of Year] = 217 THEN 9256WHEN [Total Calendar Day Of Year] = 218 THEN 8544WHEN [Total Calendar Day Of Year] = 219 THEN 8833WHEN [Total Calendar Day Of Year] = 220 THEN 9785WHEN [Total Calendar Day Of Year] = 223 THEN 9176WHEN [Total Calendar Day Of Year] = 224 THEN 9437WHEN [Total Calendar Day Of Year] = 225 THEN 8559WHEN [Total Calendar Day Of Year] = 226 THEN 9412WHEN [Total Calendar Day Of Year] = 227 THEN 9323WHEN [Total Calendar Day Of Year] = 230 THEN 9337WHEN [Total Calendar Day Of Year] = 231 THEN 9323WHEN [Total Calendar Day Of Year] = 232 THEN 9096WHEN [Total Calendar Day Of Year] = 233 THEN 9244WHEN [Total Calendar Day Of Year] = 234 THEN 9245WHEN [Total Calendar Day Of Year] = 237 THEN 8661WHEN [Total Calendar Day Of Year] = 238 THEN 9357WHEN [Total Calendar Day Of Year] = 239 THEN 7801
ELSE 0END
Total Calendar Day of Year is Performance Date, then the number of the date of the year, and then the footfall target after THEN.
This is done with a fairly rudimentary knowledge of SQL so feel free to improve upon what I've done here! But basically that is how we do it. I'm using an excel file to concatenate the values so that I'm not actually writing the lines myself.
Just another note that you can't use the break by function or it doesn't allow you to show more than one value. It took me ages to figure that out! So it is worth keeping the widget as simple as possible.
Best of luck and hope it helps!
Thank you so much for your notes! Yes we had a really good chat at TLCC so I appreciate you setting this all out as you have. Your formula will be really helpful, we're not yet at the point of having daily targets but I could certainly use something similar for monthly targets. I had considered using hold codes to show the target number (something the RA mention they do in the Analytics webinar this week) but that wouldn't work as well for monthly targets.
I've upvoted your idea! Thanks again,