Attendance analysis

We have two custom reports that looks at attendance by Geo area by performance or performance date range, but nothing that looks over an order date range.

As I said they are both custom reports, one that references custom tables where the geo areas are set up at postal, county and town level and the other pulls from the info in TR_GEO_AREA, which isn't as granular.

I'd be happy to share either if you think they'd work for you.

Caryl

This should give you an idea at least. Try something like this, in the list manager in manual edit. Just replace  ## with appropriate id for the geo area from tr_geo_area system table and adjust the getdate () for the appropriate range.

select distinct a.customer_no
from
V_CUSTOMER_WITH_PRIMARY_GROUP a (Nolock)
join LVS_NSCAN_ATTENDANCE b(Nolock) on b.customer_no = a.customer_no
join T_ADDRESS c on b.customer_no = c.customer_no and c.primary_ind = 'Y'
join TR_GEO_AREA d on c.geo_area = d.id
where b.perf_dt between GETDATE()-7 and GETDATE() and d.id = ##   -- past 7 days

Please test it. I only rattled if off quick and did not really check the results in quick test.

Travis

Thanks Caryl

It would be great to share those reports.

Mandy

Hi Travis

I'll give this a go.

Thanks very much

Mandy

Hi Mandy,

Geo Area is a standard attribute in T-Stats, so assuming it is populated for you in Tessitura, you should be able to do this report in T-Stats without customization. As of T-Stats v4.5, there is a new measure called Num Attended in both the Seats and Tickets cubes. Num Attended reflects both ticketed attendance and non-ticketed member scans. If you are using earlier versions of T-Stats there is not a measure that shows the number of attendees, but in the Tickets or Seats cubes, but you can filter down to show just sold tickets or sold seats that were scanned using the Ticket Order Details - Attendance attribute. You can look at specific date ranges by filtering on the performance date or the order date. If the time period you're after is not a date range, but, for example, the minutes prior to performance when the ticket were scanned, that would require a customization.

Could you clarify: is your interest specifically only regarding the constituents in a specific list? The report as you described it should not require a list-based filter, however it should be possible to use one if desired. However, extremely large lists or filtering-not-in-list for very small lists can both have a significant performance impact on T-Stats. Especially if the list is dynamic, it will regenerate before the filter is applied, which for very large lists can take several minutes. There is also generally a limit to the size of the lists available for filtering (this is editable so your exact limit may be different than other organizations'). The purpose of this limit is to prevent performance issues such as what I described. If your organization has increased this limit and your list is very large, that may be the source of what you describe. Depending on your report criteria, there are also some other possibilities as to why the report in question might not be quick to render.

All that said, while complex criteria can sometimes take a T-Stats report longer to render, the application should not crash under these circumstances. If you are receiving errors or the application quits suddenly when applying a list based filter, please have one of your organization's designated support contacts email T-Stats@jcainc.com with details so that the T-Stats Support Team can assist.