For Anyone Who Got Shut Out of a Sale/Wants Tips for Upcomin

Rearviewrelease

Firstly, I'd like to say that I secured tickets for Boston this way...from my highschool's shitty internet. With a little luck and patience. Hopefully these tips will work for you.

1. Use Google Chrome

It's the fastest browser bar none.

2. Anticipate what the URL will be for event specific tickets.

What I mean by this, is every ticket link has had a specific 4 digit number at the end of their url.

Kansas was 7312
STL was 7313
Columbus was 7314
IN was 7315
Boston was 7320
MSG I was 7322

You can safely assume that

Cleveland will be 7316
Buffalo will be 7317
Bristow will be 7318
Hartford will be 7319
TBD will be 7321
NY II will be 7323

3. Now, by using this method, you can make an educated guess as to what the url for ALL ticket sales will be.

https://secure.pearljam.com/store/produ ... g?sku=7312

Use that URL and change around the numbers, and make that as a BOOKMARK on Google Chrome.

4. Bookmark the Ticket section of the Goods section.

https://secure.pearljam.com/store/produ ... tegoryId=3

Easy enough.

Now, about 10 minutes before the sale, make two tabs in Google Chrome. In one, bring up the Tickets Section. In the other, click on the Bookmarked FUTURE ticket link. It was will give you a message saying "That product is unavailable at this time"

However, when it gets closer and closer to the sale, keep refreshing both pages until one of them gets you to the tickets you want the fastest.

When the BUY button shows up, exit out of the tab that is NOT showing you the Buy button. No need to have internet power wasted.

5. BE PATIENT

It will stop loading on Checkout options 2 and 3. It's going to happen. However, if it is in your Cart...it SHOULD allow you to continuously refresh until you finalize the buying process.

I used this method to buy Boston tickets from horrible school internet, hopefully it will work for all of you

helplessdancer

u r kind for helping others

FirstExit

I can't say I agree 100% with using Google Chrome. I used both Firefox and Chrome when I bought tickets today, and BOTH times it was Firefox that got through first.

back9

Good for you bro, way to cheat the system!!!!

idreaminred

Wow. Good stuff.

polaris_x

thanks ... i used firefox cuz someone mentioned that to me last time ... and i got tix but this sounds like a good idea ...

Rearviewrelease

FirstExit wrote:

I can't say I agree 100% with using Google Chrome. I used both Firefox and Chrome when I bought tickets today, and BOTH times it was Firefox that got through first.

I just think that Google Chrome, especially if you just downloaded it, is a much sleeker system with less to weigh it down.

Just opinion

Ample Jar

You're giving away the secrets of the trade here....

...It's called "keeping time"...it's this thing they developed back in the '70's....

BeerBaron

The reason that they did not keep the sequential order with Boston and NYC is for this reason. They know that people look at the SKU numbers and gain an advantage when buying tickets. So, for the high demand shows, they don't use the next sequential number, as you saw with Boston and MSG.

The only thing that one can safely assume is that this trend will definitely continue for MSG2 and Harftord, at least. So there is no advantage to be gained...

Edit: I think I get what you are saying as far as a strategy goes, but be CAREFUL. People had ticket orders cancelled for the last tour because they bypassed the system and got tickets before the officeial on-sale.

Rearviewrelease

back9 wrote:

Good for you bro, way to cheat the system!!!!

Just called being smart. The only reason I am helping everyone else out is because I'm not going for anymore tickets for this tour

Except if May 18th is announced in Boston

Indifference

BeerBaron wrote:

The reason that they did not keep the sequential order with Boston and NYC is for this reason. They know that people look at the SKU numbers and gain an advantage when buying tickets. So, for the high demand shows, they don't use the next sequential number, as you saw with Boston and MSG.

The only thing that one can safely assume is that this trend will definitely continue for MSG2 and Harftord, at least. So there is no advantage to be gained...

I've heard of orders getting canceled do to getting tickets before they were released - via some backdoor ways like the SKU number. Buyer beware.

DreamOfAngels

You might want to be cautious with the "guess the URL of item" approach. It seems familiar that someone did this last fall and their order ended up being canceled because they were able to add it to their cart a few seconds prior to the on sale time and 10c thought they were trying to back-door a purchase or cheat the system. Anybody else recall this?

Rearviewrelease

BeerBaron wrote:

The reason that they did not keep the sequential order with Boston and NYC is for this reason. They know that people look at the SKU numbers and gain an advantage when buying tickets. So, for the high demand shows, they don't use the next sequential number, as you saw with Boston and MSG.

The only thing that one can safely assume is that this trend will definitely continue for MSG2 and Harftord, at least. So there is no advantage to be gained...

They weren't random. They went in order. Read my post. If you start from 7312 and count down all the way until MSG II, INCLUDING the TBD date, the SKU's all match up with the one's that were "out of order"

Rearviewrelease

DreamOfAngels wrote:

You might want to be cautious with the "guess the URL of item" approach. It seems familiar that someone did this last fall and their order ended up being canceled because they were able to add it to their cart a few seconds prior to the on sale time and 10c thought they were trying to back-door a purchase or cheat the system. Anybody else recall this?

But I did not get in early. I didn't get tickets until about 12:06. However, this made the entire process easier.

I don't think it's cheating the system, it's just being attentive.

BeerBaron

Rearviewrelease wrote:

BeerBaron wrote:

The reason that they did not keep the sequential order with Boston and NYC is for this reason. They know that people look at the SKU numbers and gain an advantage when buying tickets. So, for the high demand shows, they don't use the next sequential number, as you saw with Boston and MSG.

The only thing that one can safely assume is that this trend will definitely continue for MSG2 and Harftord, at least. So there is no advantage to be gained...

They weren't random. They went in order. Read my post. If you start from 7312 and count down all the way until MSG II, INCLUDING the TBD date, the SKU's all match up with the one's that were "out of order"

Gotcha. I missed that. They go in order of the date of the show.

Rearviewrelease

BeerBaron wrote:

Rearviewrelease wrote:

BeerBaron wrote:

The reason that they did not keep the sequential order with Boston and NYC is for this reason. They know that people look at the SKU numbers and gain an advantage when buying tickets. So, for the high demand shows, they don't use the next sequential number, as you saw with Boston and MSG.

The only thing that one can safely assume is that this trend will definitely continue for MSG2 and Harftord, at least. So there is no advantage to be gained...

They weren't random. They went in order. Read my post. If you start from 7312 and count down all the way until MSG II, INCLUDING the TBD date, the SKU's all match up with the one's that were "out of order"

Gotcha. I missed that. They go in order of the date of the show.

Exactly. So I don't think it's unfair to use the SKU codes to your advantage.

melva02

One thing you could do is wait until you see the show listed on the tickets page, then switch to the URL with the SKU in it. Some of the buttons (but not the ticket links? I think) are javascript rather than direct links, but when the page doesn't load completely because the server's hammered, you get links instead of buttons for things like checkout.

I had trouble with my checkout process sometimes resetting that browser tab to be loading the tickets section of the goods page, instead of the checkout process. Definitely good to save that link for once you get the tickets in your cart.

Melissa

URthekey

This is good advice.

Now how do I get the ticket icon to appear b4 they are TEMP OUT?

Dercheef

FirstExit wrote:

I can't say I agree 100% with using Google Chrome. I used both Firefox and Chrome when I bought tickets today, and BOTH times it was Firefox that got through first.

Same here.

Rearviewrelease

URthekey wrote:

This is good advice.

Now how do I get the ticket icon to appear b4 they are TEMP OUT?

If you use this method, I really think you will get them in your Cart fairly quickly.

MK50139

10C explicitly stated last time anyone trying to "backdoor" the system will have their tickets and membership revoked. Good luck.

Rearviewrelease

MK50139 wrote:

10C explicitly stated last time anyone trying to "backdoor" the system will have their tickets and membership revoked. Good luck.

How is this back-dooring the system? I only get to the URL once they OFFICIALLY put the tickets up.

If the tickets are not OFFICIALLY put up for EVERYONE to get, I cannot access that link.

So, I'm getting there once the link goes up. However, I need to deal 2 less menus to get to that link. Not back-dooring.

helplessdancer

melva02 wrote:

One thing you could do is wait until you see the show listed on the tickets page, then switch to the URL with the SKU in it. Some of the buttons (but not the ticket links? I think) are javascript rather than direct links, but when the page doesn't load completely because the server's hammered, you get links instead of buttons for things like checkout.

I had trouble with my checkout process sometimes resetting that browser tab to be loading the tickets section of the goods page, instead of the checkout process. Definitely good to save that link for once you get the tickets in your cart.

Melissa

good idea

thanks

Santos L. Halper

huh...wonder why so many people are having problems checking out....good thing folks aren't skipping steps to get to the checkout quicker, cause that would be REALLY REALLY BAD and cause a bottleneck at checkout. I'm sure I'll be talking to some folks soon about this.
slh

A satellite forever orbiting

Santos L. Halper wrote:

huh...wonder why so many people are having problems checking out....good thing folks aren't skipping steps to get to the checkout quicker, cause that would be REALLY REALLY BAD and cause a bottleneck at checkout. I'm sure I'll be talking to some folks soon about this.
slh

not again. that sucks that people are circumventing the system again.

melva02

Santos L. Halper wrote:

huh...wonder why so many people are having problems checking out....good thing folks aren't skipping steps to get to the checkout quicker, cause that would be REALLY REALLY BAD and cause a bottleneck at checkout. I'm sure I'll be talking to some folks soon about this.
slh

Santos, question...since the chances of getting through to the server two clicks in a row are slim to none, isn't it really just a matter of choosing which url to refresh? Guessing the sku in advance is sneaky, but keeping track of it once the link is up just means you're paying attention to what you're trying to do.

From a network traffic perspective, the more directly each user can get to what they want and get their purchase completed, the more bandwidth is freed up for other users. For example, if I add tickets to my cart and get the whoops/ripped our face off page, then my choices are (1) keep refreshing the goods page until it shows up for me to click the checkout button, or (2) know the link to the checkout page and refresh that directly. Using the second option can save dozens of requests to the server, which benefits everyone.

So then the corollary is, once the ticket link is up (assuming no sneaky guessing), when people share it on here, they're helping reduce server traffic from people trying to see the ticket landing page (which they don't need to do as part of the process), and the reduced traffic benefits everyone.

So please, serious question and not trying to be a smartass, besides posting the link before it's up, which parts are not permitted? I know I and probably most others are just trying to make it more efficient for everyone and give new users a fair chance against the people who've been through this many times but won't share their strategies.

Melissa

A satellite forever orbiting

melva02 wrote:

Santos L. Halper wrote:

huh...wonder why so many people are having problems checking out....good thing folks aren't skipping steps to get to the checkout quicker, cause that would be REALLY REALLY BAD and cause a bottleneck at checkout. I'm sure I'll be talking to some folks soon about this.
slh

Santos, question...since the chances of getting through to the server two clicks in a row are slim to none, isn't it really just a matter of choosing which url to refresh? Guessing the sku in advance is sneaky, but keeping track of it once the link is up just means you're paying attention to what you're trying to do.

From a network traffic perspective, the more directly each user can get to what they want and get their purchase completed, the more bandwidth is freed up for other users. For example, if I add tickets to my cart and get the whoops/ripped our face off page, then my choices are (1) keep refreshing the goods page until it shows up for me to click the checkout button, or (2) know the link to the checkout page and refresh that directly. Using the second option can save dozens of requests to the server, which benefits everyone.

So then the corollary is, once the ticket link is up (assuming no sneaky guessing), when people share it on here, they're helping reduce server traffic from people trying to see the ticket landing page (which they don't need to do as part of the process), and the reduced traffic benefits everyone.

So please, serious question and not trying to be a smartass, besides posting the link before it's up, which parts are not permitted? I know I and probably most others are just trying to make it more efficient for everyone and give new users a fair chance against the people who've been through this many times but won't share their strategies.

Melissa

last time someone was able to get in a couple of minutes before the ticket link was made public. santos may be referring to people that were able to get in early again.

melva02

A satellite forever orbiting wrote:

last time someone was able to get in a couple of minutes before the ticket link was made public. santos may be referring to people that were able to get in early again.

I hope that's what it is, because of course that's unfair. But using the URLs you see to try to get the page you want in between getting bounced around server timeouts and the whoops page, I mean come on. If they don't like that they can remove the need for it by getting enough server capacity that each click returns the page you want, and it would take each user 2 minutes to select tickets and click through check out. If they could sell 25% of all ticket pairs simultaneously, they'd sell out in way less than an hour.

Rearviewrelease

A satellite forever orbiting wrote:

melva02 wrote:

Santos L. Halper wrote:

huh...wonder why so many people are having problems checking out....good thing folks aren't skipping steps to get to the checkout quicker, cause that would be REALLY REALLY BAD and cause a bottleneck at checkout. I'm sure I'll be talking to some folks soon about this.
slh

Santos, question...since the chances of getting through to the server two clicks in a row are slim to none, isn't it really just a matter of choosing which url to refresh? Guessing the sku in advance is sneaky, but keeping track of it once the link is up just means you're paying attention to what you're trying to do.

From a network traffic perspective, the more directly each user can get to what they want and get their purchase completed, the more bandwidth is freed up for other users. For example, if I add tickets to my cart and get the whoops/ripped our face off page, then my choices are (1) keep refreshing the goods page until it shows up for me to click the checkout button, or (2) know the link to the checkout page and refresh that directly. Using the second option can save dozens of requests to the server, which benefits everyone.

So then the corollary is, once the ticket link is up (assuming no sneaky guessing), when people share it on here, they're helping reduce server traffic from people trying to see the ticket landing page (which they don't need to do as part of the process), and the reduced traffic benefits everyone.

So please, serious question and not trying to be a smartass, besides posting the link before it's up, which parts are not permitted? I know I and probably most others are just trying to make it more efficient for everyone and give new users a fair chance against the people who've been through this many times but won't share their strategies.

Melissa

last time someone was able to get in a couple of minutes before the ticket link was made public. santos may be referring to people that were able to get in early again.

As I said before, I DID NOT get in early. The Boston Tickets link did NOT show up on my computer until 12:06ish

A satellite forever orbiting

Rearviewrelease wrote:

As I said before, I DID NOT get in early. The Boston Tickets link did NOT show up on my computer until 12:06ish

relax...i wasnt pointing any fingers. just speculating on santos' post.

Rearviewrelease

A satellite forever orbiting wrote:

Rearviewrelease wrote:

As I said before, I DID NOT get in early. The Boston Tickets link did NOT show up on my computer until 12:06ish

relax...i wasnt pointing any fingers. just speculating on santos' post.

I'm not getting mad at you. I'm honestly just trying to defend my position, because I don't want my tickets ripped from me because I bookmarked a couple links, that did not get me anything earlier than anyone.