Hi all,
First time posting here, and pretty new to all things Tessitura. I'm looking for some help finding a reliable way to identify a count of first time buyers for a given performance. The approach I've taken so far has been to recycle the approach from these threads:
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_shared_reports-9/30179/identifying-first-time-ticket-buyers/79981#79981
https://community.tessituranetwork.com/topical_groups/analytics-coffee/f/discussions/32632/first-time-vs-returning-ticket-buyers
In short, both of these discussions use the following formula within a Widget:
Count([Constituent ID],IF(MIN(DDIFF([Days in Date],[Years in First Performance Date]))=0, MAX([Constituent ID]),NULL))
The challenge I'm facing stems from a large lack of knowledge of how this formula is actually doing it's thing, but more to the point is that it doesn't seem to be reliably returning first time ticket purchasers upon validation. I should note that I understand this query won't be bullet proof given we have a lack of structured historical data from our pre-tessitura days, but we still want to build for the future.
My questions are to see if a) this is an effective direction to take, even if it has to shift to being a long term goal, and b) if there is a "quick and dirty" way to find what I'm looking for while I continue to work on learning analytics (perhaps pulling some simple lists/something from SSMS that would give me the same result even if it's less elegant?).
I'm sure this isn't the first time it's been asked outside of the threads already cited, so please redirect me to an answer if it's already out there.
Thanks for the help!
Hi Justin!
There's some rows in the TX_ANALYTICS_DIVISION_ELEMENT table that you can edit to select first show and first show date. You have to edit the sql to get it to function how you want it to but then you can use those custom elements in your Analytics widgets. It's really cool what you can look at with that info!
You can copy and paste the SQL into SSMS and run it as a select statement using your patron ID as a where clause to test that it works before adding it into the system table.
Hope that's helpful!
Desiree