• Replies 10 replies
  • Subscribers 416 subscribers
  • Views 186 views
  • Users 0 members are here
Related

Age Old Mystery: First Time Buyers by Show and FTB at Venue

Michelle Wiesel
$organization
Hello to all the fantastic Tessitura minds out there! Our new Artistic Director would like to identify new buyers after each show/run. I've attempted to discern the following: Identify first-time ticket buyers by performance and/or Run Identify first-time buyers to the venue in general - could also be their only visit. I've scoured archives, found some excellent info on segmentation, tried and tried this pull, that extraction, etc but this seems to be a question that doesn't have a simple solution. So I ask - (OK, I beg!) Has anyone come upon a reliable T-Stats recipe / list / extraction combination, etc that is working for you? Many grateful thank yous to you all!!
Parents
  • $organization
    I wrote a custom view that extracted the first performance details attended from the ticket history so that a criteria for List Manager (and by extension, Extraction Segments) could be created. It might need some customising to exclude anything that isn't a performance - if you sell program vouchers, for example. It was based on first performance attended rather than purchased on purpose - we only wanted to report on subscribers once in the season. Creating a list based on a criteria created from this view would then allow you to use it as a filter in T-Stats. Happy to share - just let me know if you think this'd work for you. Martin
  • $organization in reply to Martin Keen (Past Member)
    Hi Martin: Fantastic! Thank you so much for your willingness to share your work! We do not sell program vouchers but do sell gala events that I would want to exclude from results. Did you find the need to do a good amount of cleanup after exporting? I utilize a number of macros in Excel to assist with that. Given output is firmly dependent on the initial setup I find we're a bit challenged. Each season I must rebuild shows, move entire houses due to too early on sales, wide-ranging sudden price changes, canceled shows, etc. It's a challenge! As you can imagine this creates a lot of duplication, new price types, etc. I would love to take a look!!! Thank you!!!
  • $organization in reply to Michelle Wiesel
    Michelle, I'm happy to email you the file - given the problem with formatting here in the forums, I can't attach it here - just drop me a line at martin.keen@nida.edu.au. The script I can send you creates a view that returns all the columns from the Ticket History - it may need a little tweaking to suit your environment but not much - do you have a DBA? The view has logic to exclude performances of a certain type - as defined in the System Table TR_PERF_TYPE. Drop me a line if you want the script. Martin
  • $organization in reply to Martin Keen (Past Member)
    Hi Martin, I'm the DBA, such as one exists, for the consortium Michelle's in. I'd love to see the script, as there are a lot of us here that could use it! svoigt@granadasb.org -- Thanks! Stacey
  • $organization in reply to Stacey Voigt
    Travis, My method was to have a view that will just return the first performance attended by the constituent - pretty basic coding really. In our world, we want to find those people for whom production A (or productions A, B or C) was their first attendance. I've also uploaded it to be a file attached to my account here. Stacey - I've emailed this script directly to your email. Martin
Reply
  • $organization in reply to Stacey Voigt
    Travis, My method was to have a view that will just return the first performance attended by the constituent - pretty basic coding really. In our world, we want to find those people for whom production A (or productions A, B or C) was their first attendance. I've also uploaded it to be a file attached to my account here. Stacey - I've emailed this script directly to your email. Martin
Children