I’ve experimented with automation libraries like Playwright in both Python and Node, as well as alternative browser automation tools. Although I managed to bypass detection on a known bot-checking service, Ticketmaster still flagged the activity as bot-like. I also attempted to use modifications and different stealth plugins, adjusted executable paths, and even tested with another browser, yet the detection issue persisted. Switching off headless mode did not resolve the problem either.
hey, i tried something similar with puppeteer and kept gettin flagged. tinkering with user agents and proxies helped a bit, but ticketmaster detection stays agressive, so nothink is foolproof yet.
I have also faced significant challenges when attempting to scrape Ticketmaster with headless browsers. In my experiments using Selenium with a modified ChromeDriver, despite trying to mimic real user behavior through adjusting navigator properties and adding deliberate delays between actions, the detection was still persistent. My results indicate that Ticketmaster’s detection mechanisms are far more advanced than most standard anti-bot techniques. Ultimately, using a fully rendered browser session provided slightly better results but at the expense of efficiency and consistency.
In my attempts to scrape Ticketmaster with a headless browser, I noticed that even implementing advanced stealth techniques provided only limited success. Adjusting the browser settings, simulating user actions with delays and varying navigator properties did not fully bypass their detection. Running the session in non-headless mode resulted in slightly improved performance, yet it was a trade-off in terms of speed and automation reliability. My experience indicates that Ticketmaster employs sophisticated detection measures that can recognize and flag headless browsing behavior, making sustainable scraping a challenging task.