Hello,
We are considering assigning a constituency code to ticket buyers. We currently pull lists based on ticket purchase history but wondering if a ticket buyer constituency may make list pulling, reporting, etc. easier. Does anyone currently use a constituency code for ticket buyers? I'd like to hear any feedback.
Thanks,
Chris
Hi Chris,
We don't build lists using a Ticket Buyer constituency as there's not really enough detail as to the tickets involved - which, I guess, may or may not be important to what you're trying to achieve. I guess it could be a very quick and simple way of adding the fact they're an active ticket buyer into a list - say of donors who are also ticket buyers.
More often than not, we pull lists based on the first performance that constituent purchased tickets for. I wrote a view to detail a constituents first ticket purchase upon which to base List Manager/Extraction criteria on. Happy to share this if it's of any use - email me at martin.keen@nida.edu.au.
Martin
Yes, I started doing this about 6 months ago. I applied a different constituency code for every year that someone has purchased tickets or attended any of our events.
For example, that means that you can see everyone who saw a performance in 2018 and 2016, but did not in 2017, or everyone who has codes for all of the last 5 years (if those sorts of things are important to you!).
So far I've found it really helpful!
Alison