Hello, we want to capture the Birth Date for all of our constituent but are in doubt what is the best way.
When do you capture this? and how do you do it? Is it mandatory? And if so, how is the data quality?
Thanks
Eva
Hi Eva - we have a youth discount program that requires you to provide your birth date to join. You age out of the program on your 30th birthday. We do ask them to provide proof of age when they pick up their tickets so it's fairly accurate. Other than that program, we don't ask for birth date.
We have something similar, but we do not ask for their birthday yet, we just trust them, but we would like to track it. Do you ask in the purchase flow? or how do you ask?
We track birthdays for anyone who will give them to us. We did an email to ticket buyers, subs, donors, etc. a few years ago asking them to give us their birthdays and ee got a good response. We also ask on raffle forms, for our student program, and random other times. Most people are comfortable giving us month and date. We use the data to send birthday emails on the first of the month; if they bring their email to a performance in their birthday month they get free chocolate. We also use it to target marketing for specific groups.
The discount price type is hidden online unless you are registered with an appropriate birth date on file. If you already have an account, you just need to contact the box office to have your birth date added to your file. We track birth date as an attribute. We then have a custom proc run that adds a constituency to your file with an end date of your 30th birthday. The constituency unlocks the pricing online. All orders containing these discounted tickets are set to HABO and you need to show valid ID to pick up the tickets.