Discount to segment but not using promo code?

Former Member
Former Member $organization

Hi friends,

We're developing a "trial subscription" offer that is deeply discounted. The offer is targeted at a specific segment of our patron base- about 100 hh. Because the offer is so good, we don't want to use a promo code so that we prevent it spreading too far and wide.

Any ideas on how to make this work? We thought through the use of rankings and constituency codes, but ran into problems. Here are more details:

 

Offer is being made to people in last season who were new to file and saw at least two shows.

Offer is x events for $x dollars.

Offer has expiration date.

We are on TNEW.

 

Thanks for your help! 

  • Just curious why you wouldn't use a promoted source code - that way it can only be redeemed by those who have it on their file and can't be used by anyone else.

  • Former Member
    Former Member $organization in reply to Michele Keutsch

    Hi Michele-

    Thanks for that idea. It may certainly be a solution. So if I understand it correctly, we'd use a promoted source code to mark the patrons that qualify for this offer. Then, there's a way to be sure that the promo code only works with those who have the source code on their record?

     

    Thanks,

    Will

  • Hi Will,

    Actually, promoting a source code (ie. making it an inside source) doesn't restrict people that happen to have the password from using it. We've definitely encountered that here in previous promo code offerings. I think the point of the inside source is moreso that you know who you're marketing to vs an outside source where it could be anybody and everybody - but at the end of the day all sources are fair game to people that know how to access them.

    We're not on TNEW so I can't quite speak to the limitations there. I'd perhaps speak to your TNEW contact and see if they have any out-of-the-box recommendations. Perhaps you could implement some sort of ranking for these specific people and use that instead of a promo code?

    Good luck!

  • Former Member
    Former Member $organization in reply to Beth Hawryluk

    Hi Beth-

     

    I think you're right about rankings. That's the conclusion we've come to here. We don't often use rankings so we're thinking through how that would look. 

     

    The ranking itself is not a problem, but how and when to "unrank" these people so that if they pass on this offer and want to buy regular tickets, they can. 

     

    Thanks for your reply!

  • We're new on TNEW, just been on for about a year. We offer our subscribers their standard discount through the whole season and wanted a way for them to access this online. When we converted last summer, we were handled by consultants from Klearsky. In the process, we created constituencies for all our subscribers. Then Klearsky wrote a procedure that will automatically add this constituency based on ticket history, Then that constituency triggers another custom procedure, that adds a Web Ranking. Depending on their constituency, they get either 100 points or 200 points. We set up that ranking to trigger a MOS shift in TNEW to one of 2 different MOS. Depending on MOS, they would then have access to the special discounted price type associated with their subscription.

    Obviously, we were paying through our conversion budget to have these procedures built. If you have IT or system admins who can handle that it shouldn't be too difficult. The rest can be setup through system tables. Obviously, all these MOS would have to be added to each show and be given access to price types for any event you might sell online. That way, these select few can still buy other performances when they log. Since you want the option of opting out, you may not want to automate the constituency, but rather add in by hand since its only 100 hh. Then you can delete or expire it if necessary.

    What kind of issues were you running into when using the rankings?

  • Former Member
    Former Member $organization in reply to Jesse Dillman

    When we did something similar, we also created a constituency and a unique price type, used the Manage Constituency utility to add it to our invited guests' records (and set an end date) and our DBA wrote some code that ensured that only people with that constituency could access that price type on the website.

    B