Ask or search…

Footsites (North America)

Task Creation

  • Before creating tasks, you must create a new task group for the footsite you want to run on. For help on creating a new task group, follow this guide.

Monitor Setup

  • Product ID: use the product PID provided by our release guides or a third-party. Using a direct link will not work.
  • Proxy List: used for monitoring only. Can be the same as your task list.
  • Delay: monitor delay. Recommended to be left at 5000

Captcha Settings

  • Captcha setting that will be used to solve any Queue-It captchas. Recommended to use any third party solution. For help on third party setup, follow this guide.
Captchas are required for Queue-It only! DataDome captchas are solved by Prism.

Task Creation

Required Fields
Optional Fields
  • Profiles: choose your profiles/profile group
  • Delay: task delay. Recommended to be left at 5000
  • Proxy List: proxy list used to checkout (leave blank for localhost)
  • Size: size(s) the task will go for. If selecting multiple sizes, it will go for any size in your range.
  • Account List: FLX accounts the tasks will use
  • Gift Card List: Gift card list the tasks will use


  • There is a common misconception that if the release uses Queue-It then Geetest will not be used and this is wrong. Regardless of the queue type, DataDome with Geetest will always be in use.
    • For those unfamiliar with Queue-It, it is another queue type that Footsites use. Queue-It requries a recaptcha V2 (standard captcha) to enter the queue.
    • DataDome is the anti-bot that Footsites use and when your proxy becomes blocked, a captcha will be needed. Prism will solve all GeeTest captcha automatically.

Status Codes

Status Codes
  • Some errors are simply unpredictable so they don't have a designated status in the bot. If you encounter one of those errors, you can search the error here to see what it means.
Waiting for Product:
  • The task is waiting for the monitor to pickup the product. If you are stuck here but the drop is live, change your monitor proxies.
Waiting xxhr xxm xxs:
  • This means that the task is waiting for the countdown on the site to end.
  • For most footsites drops, they will put up a queue and slowly let tasks/users through. This status is perfectly normal and you must let the bot run.
Queue (Perma):
  • During high-traffic periods, footsites will put up a permeant (perma) queue. This status means that they are not allowing anyone to pass the queue and access the product page.
  • Can also occur due to region locked releases. For example, US proxies will not work on some CA releases.
Out of Stock, retrying...:
  • This is the most important status and is what you want most of your tasks to be at. Footsites release stock over time, and not at once, so this status means that the task is continuing to try and add the product to cart until they add more stock.
Generating Session:
  • One of the first statuses you will see will be generating session. Each task must generate a session. If you find your tasks stuck on this status, you must change your proxies.
Solving Datadome:
  • Your tasks are waiting for you to solve the Datadome captcha. If you are stuck there, stop using third party solvers and solve the captcha.
IP Banned:
  • IP Banned means that the proxy or IP address you are using in the bot is banned and cannot access the product page. For the most part, the only way to fix this status is to change proxies.
Rate Limited:
  • Rate limit occurs when you are sending too many requests from a single IP address. Some proxies are rate limited by default so make sure to test your proxies before the drop.
Cart Expired:
  • This usually happens when one of your tasks has carted and another task using the same billing profile attempts to cart again. Both carts will be cleared and you will get this status. The only way to combat this is to run more unique billing profiles for your tasks.
Proxy Error:
  • Proxy error means bad proxy. Change your proxy list.
Request Timed Out:
  • This error means that the task could not establish a connection to the site. Causes for this include slow proxies and a site that is under a lot of traffic.
Error Adding to Cart:
  • Sometimes a size will give an error when you try to add to cart via the bot or even manually. If you see this error, just let it run.
Unknown Response [400]:
  • Usually means a bad prrofile if it occurs before a billing step
  • Can also be bot related.
Unknown Response [403]:
  • Another way to say rate limited. Change proxies if you encounter this.
Unknown Response [404]:
  • Means that the site or page is not found OR the bot is not working.
Unknown Response [418]:
  • This is normal as the site is experiencing heavy traffic. Just let your tasks run.
Unknown Response [421]:
  • This is normal as the site is experiencing heavy traffic. Just let your tasks run.
Unknown Response [502]:
  • Site error
Unknown Response [503]:
  • Site error
Task Crashed:
  • Rarely occurs but can happen. Open a ticket if you get this error.


General FAQ

What is Adyen?
  • Adyen is footsite's payment processor. They are very strict on checkout information so during footsite drops you might receive a lot of cancellation emails. This is not the bot's fault, but solely based off the information that was used to checkout.
Can I use the same profile multiple times?
  • You can, but it is not recommended.
What type of proxies are recommended?
  • For initial drops, a mix of residential and datacenter proxies are recommended.
What are cart holds?
  • Footsites use a cart hold system to try and make a release fair. When you add a product to cart during release time, theoretically the product will be held in your cart for around 10 minutes to give you time to checkout. With this, the product may show as out of stock very fast. Most of the time, this does not mean that it is actually out of stock! During footsite drops, people who were not successful in checking out will have their cart lost. This typically happens in waves of about 5 to 10 minutes. When these waves occur, you will see a heavy influx in checkouts.
Why am I getting payment declined?
  • Sometimes payment failures/declines are a result of your bank declining the transaction. But with the recent changes to footsites, your task will show payment declined if you have already checked out that product on one site using the same profile. With this, it is highly recommended to use as many profiles as possible.


If I use Residential proxies as my TASK proxies, will they use data while monitoring?
  • They will not as long as they are on "Waiting for Product" or "Waiting for Restock." But as soon as the product is picked up it will begin to use the proxies that are assigned to your tasks.
Why am I seeing "IP Banned"?
  • IP banned occurs when the bot continues to try and add a product to the cart but the product page has been pulled. It is just a page ban that can be resolved by restarting tasks.
Why am I seeing "Rate Limit"?
  • Rate limit occurs when you send too many requests from a single IP in a short amount of time. This can occur if you are running low delays or not enough proxies. The only way to fix this is too use a new set of proxies.
  • With this though, some footsite products are rate limited for everyone. If you try and add to cart manually and get an error, the bot showing "rate limit" is a reflection of that.


Can I use the same FLX accounts for multiple tasks?
  • No! Each task must be assigned one account as using the same account multiple times will cause lots of errors.