So forgive me if I am wrong on this, but when you designate a Sub Mos in the LTR_TN_EXPRESS_WEB_DEFAULTS table, is TNEW not supposed to automatically shift users into this MOS when they are sent to TNEW using the /packages or /packages/renewals URLs? We are working on setting up our renewal campaign and need to test somethings but I can't get any published packages to display on the /packages URL. The /packages/renewals does the MOS shift and displays the applicable renewal orders. I don't remember us needing to use any sort of promo code triggered MOS shift other than for specific pre-sales but once those ended I think people were always sent to the generic link. I added the keyword, the MOS is currently active, its just not moving people into that MOS.
So I'm either misremembering how the package link is supposed to work, or there is some other detail I've forgotten?
v15 or v16? There's a bug in v16 around this. There's always been some weirdness in my experience, where the MOS seems to not be changed initially but is at some further point in the process.
2nded. Still V15, but I ALWAYS have difficulty trying to figure out what exact MOS a package is supposed to have, regardless of what settings I choose. We have some of our packages sold with a default promo code built into the links because that is the only way we were ever able to guarantee that it would actually load as on sale every time despite the fact that we just wanted it to be on sale in our normal web MOS. Nothing we did seemed to ensure that that would be the case, so we just created a second Web Education MOS for these education packages and just added that MOS to everything as well.
Ideally there would be a very clear way to control "this forces the flip to Subs MOS, and without that, it will not flip" or something. Heck, I would be fine with different URLs for something that tries to force the flip and something that does not. At any rate, I am always trying to figure out exactly what is going on there.
For my money, I want the "special package MOS" to go away. We can almost swing it, even our package-only season onsale. The problem is that we allow the purchase of "add on" tickets along with a package during that period, and there is no way to accomplish that without a special package MOS (currently). Frankly adding "add on" tickets to a package order is already a mess, so a fix here would be good anyway.
If that were the solution, I am sure we would be able to figure out a way to handle it well enough for our needs as well. Whatever the idea, I definitely would appreciate a solution, for sure.
I have long thought that one of the biggest hampers to this whole process was the lack of web publish start/end dates for packages. Seems like a simple enough add and would simplify the understanding on how a LOT of things work. They make perfect sense for performances. Why not packages, too?
Add-on tickets (AKA every package is super-special) has kept us away from TNEW for some time.