Hi all from New Zealand
We are in the process of redeveloping the purchase path on our website and we have a question about promo codes.
Here's what we ideally want to do. We display "event pages" on our website for each production season (eg a season of The Cherry Orchard), with information about the production and booking/ call-to-action details. We want the promo code entry box to sit on this page (rather than at point of login to the site as it currently does).
That isn't a problem, but we want to take it one step further. We are aware of easily customers can become confused if they see a promo code box, but know nothing about the offer and haven't been given a promo code. To help minimise this, we would ideally like the promo code entry box to ONLY display if there is an offer redeemable by a promo code related to that production season.
So, in summary, ideally if a production season did not have an offer and promo code attached to it, there would be no promo code entry box visible to the customer. Thereby eliminating any confusion.
However, our web developer, who was equally enthusiastic about this idea, has come back with the following:
"Unfortunately, we’ve been unable to find any way of determining whether an event has promotional offers available. There does not appear to be any methods for this within the tessitura API. The best I could offer is that the event has a keyword added to it which triggers the promo field. Myself, I don’t think the added admin overhead required is worthwhile, better to have the promo code entry field always available. Thoughts?"
Has anyone managed to achieve our ideal of having the promo code entry box/fields only appearing when there is an offer and promo code attached to the production season concerned?
Thanks,
Vicki
Hi, What you could do is create a stored proc that takes the performance number as a parameter. Then look in the T_MOS_OFFERS table to see if that performance exists. Then return a true or false from the stored procedure if the performance exists. You could call this procedure from the web api's ExecuteLocalProcedure method. Then use the results to display the promo box on your page.
You could also us the GetLocalData method to add this sort of information to all performances during update of the web content. That would save having to do an extra API call during the customer's session.
What about these API methods?
Validate Custom Offer (but user needs to be logged in)
or even better...
GetPromoCodeEx (session has to exist)
We are in the same boat you are but hadn't thought of putting the promo code on the show page. That is a great idea!!