Monitor Mode
Monitor Mode allows you to automatically track stock for specific events and instantly alert your accounts when new tickets appear. It’s designed to run continuously in the background, scanning Ticketmaster events and triggering checkouts the moment stock is detected.
⚙️ How It Works
Add your accounts in
accounts.csv(you can use just one if you prefer).Each monitor will continuously check the event URL(s) you’ve added in your
monitors.csvWhen stock is found, all linked accounts will be pinged automatically to attempt checkout.
Running multiple monitors on the same event increases your chances of being the first to detect stock.
💡 Example: If you’re monitoring multiple regions or drops, you can run one monitor per event link to cover more ground.
🗂️ CSV Parameters
event_url
The full URL of the event you want to monitor.
polling_interval
Defines how often Fastix checks for stock. You can use a fixed number (e.g. 5) or a random range (e.g. 4-6).
numberOfTickets
Number of tickets to cart when stock is found.
maxNumberOfTickets
Maximum number of tickets to allow in the cart.
priceRange_enabled
Set to true to activate price filters.
priceRange_min / max
Define the minimum and maximum price for tickets.
includeResale
Set true to include resale tickets in the scan, false to skip them.
ticketTypePriority
Choose seated, standing, or a combination (e.g. seated,standing). The order defines the priority — for example, seated,standing will try seated first, then standing if none are available.
⏱️ Polling Interval Explained
The polling_interval controls how often the bot checks for new stock.
5→ checks every 5 seconds exactly.4-6→ checks every 4 to 6 seconds randomly.
💡 Tip: Use a small random range (4-6, 5-7) to stay fast and realistic.
Best Practices to Maximize Your Chances
To get the best results from Monitor Mode, configuration matters just as much as speed. Follow these recommendations to improve your success rate:
Number of Accounts
Using 5–10 accounts is strongly recommended.
More accounts = more checkout attempts the moment stock appears.
You can run with just one account, but success scales directly with the number of active accounts.
Monitors vs Polling Rate
When it comes to detecting stock quickly, strategy beats raw speed.
Recommended Setup
Run multiple monitors for the same event
Set each monitor with a polling_interval of 5–7 seconds
Example:
5–10 monitors
polling_interval:
5-7
This approach:
Increases the chance that one monitor catches the drop first
Keeps behavior more natural and consistent
Reduces the risk of blocks, bans, and request errors
Not Recommended
Running fewer monitors with very aggressive polling (
1-3seconds)
This often leads to:
Higher block rates
Lower stability
Worse long-term performance
General Rule
More monitors with moderate polling > fewer monitors with extreme polling
This setup provides the best balance between speed, reliability, and safety.
Last updated