Hello,
Our organization recently finished a crowd-sourced Kickstarter project for our outdoor movie theater events. We were successfully funded and able to get a bigger screen, better audio equipment, and lighting. As part of our Kickstarter campaign, we are giving rewards to those who help fund the project. There are different levels of rewards, but basically, we wanted to give the people that funded it free tickets to a "Films on the Lawn" event of their choice. Based on how much they funded, they would get more or less "free tickets". Ideally, I would like to create promo codes for each reward tier.
For example:
Tier 1 = 2 tickets for any Films on the Lawn Event
Tier 2 = 4 Tickets
Tier 3 = 1 Season Pass
Tier 4 = 2 Season Pass
Tier 5 = 4 Season Pass
Some of these Backers may not be in our system yet. Which is good for us, because it forces them to create a constituent account. Which is sort of why I'm leaning towards promo codes in general and I think they would work great for tickets, it's another story for a Season Pass (not sure how to accomplish this). However, the biggest issue, is the sharing of these promo codes to people who may not necessarily deserve these rewards. So what are some measures we can take to minimize the sharing of these promo codes?
Heck, maybe we don't even use promo codes, there could be another way to do this.
Any advice is appreciated, thank you in advance.
Hey Cody, I guess since you are on TNEW, this sounds like a job for validate cart. Maybe create a attribute has the tier value. Force the login first test to see if they have the attribute. If so, allow them to get the comps, otherwise reset the MOS and dump them on the event listing page.
Or..
Create a local table of account numbers, login, tier, number passes (maybe some other stuff too) and use that to test against in validate cart. Should be a fun one.
Just a couple of quick ideas.
Travis