> if (!globals.hideUrgencyMessage && SH.mbox.justSoldEvent && urgencyMessageListings && urgencyMessageListings.length) {
Have you considered that SH.mbox.justSoldEvent might be noting that there were recent sales, and while they weren't just sold as the page was loaded, the system may actually indicate that sales are happening and to be aware that the listings may not persist in the current state for long?
As of right now, SH.mbox.justSoldEvent is undefined for me, but they may have specifically disabled the system (or only use it if there are sales but not too many). Looking at the seller's interface on SH for this, the last three transactions happened within 10 minutes of when I loaded the sales data, and each were for a pair. Looking at the sales data I can see that the two you had shown to you were consecutive transactions at 2017-09-11T17:45:40.000Z and 2017-09-11T17:38:55.000Z, which I'm willing to bet were the two most recent sales when you loaded the page.
If that's what's going on, it's not only for SH's benefit. This also signals to buyers what's selling right now, and what migh be sold soon in case you are eyeing a particular listing but are holding off for some reason. If similar things have sold recently, maybe that set won't still be there if you wait a few minutes. This isn't necessarily simulated demand, but real demand, the same as if you were in a store and watching a particular item fly off the shelves. If the stock is depleted, you might not be able to get one, so knowing people are buying them might influence whether you feel secure in waiting for a bit or not.
(For what it's worth, I do not work for nor have ever worked for StubHub, but I do work in the event ticketing industry so are familiar with them and how to use them).
Have you considered that SH.mbox.justSoldEvent might be noting that there were recent sales, and while they weren't just sold as the page was loaded, the system may actually indicate that sales are happening and to be aware that the listings may not persist in the current state for long?
As of right now, SH.mbox.justSoldEvent is undefined for me, but they may have specifically disabled the system (or only use it if there are sales but not too many). Looking at the seller's interface on SH for this, the last three transactions happened within 10 minutes of when I loaded the sales data, and each were for a pair. Looking at the sales data I can see that the two you had shown to you were consecutive transactions at 2017-09-11T17:45:40.000Z and 2017-09-11T17:38:55.000Z, which I'm willing to bet were the two most recent sales when you loaded the page.
If that's what's going on, it's not only for SH's benefit. This also signals to buyers what's selling right now, and what migh be sold soon in case you are eyeing a particular listing but are holding off for some reason. If similar things have sold recently, maybe that set won't still be there if you wait a few minutes. This isn't necessarily simulated demand, but real demand, the same as if you were in a store and watching a particular item fly off the shelves. If the stock is depleted, you might not be able to get one, so knowing people are buying them might influence whether you feel secure in waiting for a bit or not.
(For what it's worth, I do not work for nor have ever worked for StubHub, but I do work in the event ticketing industry so are familiar with them and how to use them).