I'm having a block. I was trying to find First Time Buyers or those folks who have not attended in the last 5 years. So I did a simple list looking at the Ticket History Perf Date (and I've done with unique perf =>1 and another without).
I then take that list and create another list of this FY performances and ask for those that does not have the list of prior ticket buyers.
However, when I run it in T-stats, I'm still finding folks in the list that have prior ticket purchases in the 5 years I thought I was suppressing.
What am I missing? Is it because history doesn't have the future performance dates yet? Thanks
Leslie,
This is always a thorny one - I'm wondering if your results are being skewed by historical (or other) data being imported into your local Ticket History table. If it's historical, these rows very often have a perf_no value of 0 - the standard criterion in List Manager (Ticket History Unique Perfs) does a count based on the perf_no value and so if it IS historical date, people may have 5 or 6 rows all with the value of 0 - meaning that the criterion only views this as 1 perf!
In a previous incarnation, I was always asked if we could get a list of all people whose first attendance was <Production A> so I wrote a view that List Manager criteria could be based on it so we could tell whose first attendance was:
Happy to share if you're interested - email me at martin.keen@nida.edu.au
Martin
Leslie McKinley said:consistency also a problem
No kidding.
Finding FTBs can almost be considered an impossible task, imho, E.g. the topic always reminds me of my mother, a Guthrie theater patron since 1963, who didn't have the equivalent of a constituent record here until 1997. If she had received some sort of FTB acknowledgement at the time she would have laughed.
Not to mention dupes: how sure are you that this "new" patron doesn't already exist in your database in some form?
Food for thought...
Exactly! The dupes are where we always get tripped up. We do have some semblance of a "first time buyers" report- my notes on it read: "For given season and performance date, returns a list of customers who are new ticket buyers to the organization as of that performance date. " But, of course, someone who created a new account on our website to buy tickets will be considered an FTB by this report, unless our auto-merge procedure catches them first.
Hi Leslie & Martin,
I stumbled across this thread and was so hopeful that you'd solved our problem already...
Thanks for the great info and tip on the Ticket History; however I tired and this didn't work as I'd hoped (may in fact be due to some wriggly/incorrect data fields...).
We are aiming to capture First Time Buyers (FTB):
At this stage, I have tried to run an extraction suppressing all historical shows up until the show we are measuring but this has proved a jumble! Look forward to hearing any feedback or suggestions.
Many thanks,
Chantel
Hi Chantel,
When I have been asked to look at first timers to a particular production, I have created a suppression for perf date (set this to < day before the beginning of the production you are looking at), then add a new segment for attendees to that production. You can then use this figure to work out the percentage of first timers.
Hi Sanjay,Thanks for this feedback! This has been very helpful for my trials.
Many thanks, Chantel