- Before creating tasks, a task group must first be created. To create a task group, navigate to the
Tasks Groupssection and click
New Task Group +
- From there, name your group and choose the site you want to run on.
Only one site can be ran per task group. To run multiple sites, you must make multiple task groups.
- The monitor section of a task group allows for easy mass-link-changing and allows users to get a better understanding of what their tasks are doing in real time.
- Monitor inputs are what PrismAIO uses when searching a website's sitemap to checkout a product. They are inputted under the "monitoring" section of the task group.
There are four types of monitor inputs accepted by PrismAIO: keywords, direct links, variants, and PID.
Some sites can only accept a specific type of monitor input so be sure to follow the module guides on how to properly setup those sites.
- If you are searching for the Yeezy 350 Zyon on a Shopify store, below is an example of a keyword group that you might run on a shopify store.
- Place a (+) before every word that you want the bot to search for and place a (-) before every word that you want the bot to ignore.
- You can also use keyword groups to search for multiple different keyword sets independently such as the picture below. In this case, the bot will go for the Yeezy 350 Zyon OR the Yeezy 700 Waverunner - whichever product the bot picks up first is what it will go for.
- If you have an early link or would like to run a link for restocks, you can input the full item link into the monitor input. PrismAIO will automatically recognize the product URL and indicate above.
- Variants are another monitor input used on sites like Shopify, Snipes USA, and Hibbett that match to a specific item and size.
- Variants are usually provided by cook groups and used to run restock tasks.
- To enable variants, navigate to
Task Group Settingsby clicking the three dots near the top-right section of the monitor section of the task group and click
- You can input multiple variants on separate lines such as the picture below and just indicate the size on each task that you create within that group.
- PID, short for product identification, is a monitor input that is tied to a specific product. It is most commonly used on footsites, Finish Line, JD Sports, and Yeezy Supply.
- In PrismAIO, you will notice there is the option for two separate proxy groups and delays. In the monitoring section of the task group, that proxy list and delay box are used for monitoring only. Where as the proxy list and delay box displayed when creating a task are used for adding to cart and checking out a product.
- The proxy list and delay in the monitor section are used for monitoring only. This means that the group itself is what will do the monitoring, TASKS DO NOT DO INDIVIDUAL MONITORING. For instance, if you see your bot on "Waiting for Product" that means that each individual task is waiting for the task group to find the product using the task group proxies. The only exception to this comes if your Shopify task becomes OOS while you are checking out, or if you are using variants. If this is the case, the bot will use the TASK proxies to monitor for that SPECIFIC size to come back in stock.
What are "threads" A.K.A "monitor workers"?
- Threads, in simpler terms, are like another monitoring task. The max threads the bot will use is 10. This is swiftly calculated by the bot to insure that your monitor proxies will not become banned. The bot takes into account a variety of factors, including how many proxies you have in the task group list, what your current task group delay is, and lastly what our "unbannable delay" is.
How much data do monitor "threads" use?
- Monitor threads use roughly the same amount of data as a single task. With this though, the task group monitor is only looking for the product and in-stock sizes, and it does add-to-cart or checkout attempts which saves on data.
If my tasks have residential (resi) proxies as the TASK proxies and datacenter (DC/ISP) proxies as the MONITOR proxies, will they use data if the tasks are on "Waiting for Product"?
- No, the tasks will not use the residential proxies to monitor for the product. If the tasks are on
Waiting for Productor
Waiting for Restock, they will use the DC proxies that are the monitor proxies to wait for the product to be live. The only case where the task will use the residential is if the site you are running is Shopify and the task proceeds to checkout but the product goes OOS. In that case, the task will CONTINUE to use the task proxies, in this case the residential ones.
How many monitor proxies do I need?
- There is no set amount, but the more the better. If you run very low monitor delays, it is best to have many (25+) proxies.
Can I use no proxies (localhost) as the task group proxies?
- You can, but it is not recommended to do it for more than 1 task group per site. So if you are running 5 task groups for Finish Line, don't run more that 1 task group without task group proxies.
Pro-tip: If you are running on a Shopify site with proxy protection and your datacenter proxies are throttled, run one task group on your localhost and your tasks with residential proxies. In this case, the bot should pickup the product faster rather than using residential proxies to monitor as they often are slower speeds.
Do the group proxies have to be the same as the task proxies?
- No they do not. You can use two different groups for both - it does not matter if they are the same or not.
- After a task group has been created, tasks can be created by click the
+icon at the top of the task group. Here, you can configure your tasks to what is needed to run the site. Depending on the site selected, different options will be available.
- Profile(s) used when creating the task.
- Delay the task will retry on (retry list)
- Proxy list used to checkout (checkout list)
- Size(s) of the item you are going for.
- Cart quantity
For almost all sites it is best to leave this at
- Used for Shopify only. Determines the mode the tasks will use to checkout. To learn about the differences between each mode, click here.
- The monitor input can be easily changed by pasting the new monitor input over the old monitor input. Once pasted, the new monitor input will automatically save and tasks will begin to run for that.
- Tasks can be easily edited by holding
CTRL + Ato highlight all tasks or
CTRL + left clickto select certain tasks to edit. Once you have the desired tasks selected, click Update All or Update Sel. in the top-right corner of the task group to update.