We have a performance that should be available ONLY to FY24 subscribers, but have just learned that FY23 subscribers are able to access this performance. I feel like it has something to do with rank type and/or web ranking, but I don't know how to fix it.
Thanks for your help!
This is definitely a question to post in Online & Mobile. I suspect you are right: the three things to check are:
If there isn't a clear configuration error in the first two, but rather customers seem to be getting incorrect rankings, then you will have to dig much deeper. Rankings are always applied (to my knowledge) through custom procedures. Traditionally this code is then invoked from the SQL procedure LP_CUSTOMER_RANK. If this is correct for your organization, then in that code you will see how rankings are expected to be applied differently to FY23 vs FY24 subscribers. I will say that for us, we have traditionally stuck settings that we expect to change periodically (things like fiscal years or season ids) in custom entries to T_DEFAULTS, and when we have these issues it often goes back to those values not being updated at the right time.
On the off chance that the above appears to be a dead end, Mode of Sale can also, of course, be changed via promo code as defined in TR_WEB_SOURCE_NO: since a promotion is just a bit of text or a link that can "leak" it is also a possible source of "unqualified" customers receiving a benefit.