To open the Adidas extension in PD, type “Adidas” in the site type window and select your region. Adidas releases take place at different times for each region so you will have to go to your desired Adidas region website and check the time. In Discord, we will update any SKU for Hype releases in the #Adidas-setup channel.
(If you want a region added, put it in the suggestions channel on discord.)
Before we get started on Task Setup, let’s talk about Profiles. We highly Recommend using as many VCC as you can. Adidas uses 3D Secure checks for normal CC cards, which leads to very slow checkout times and errors. Using VCC will skip this step, save you time and get you more checkouts. Error and Monitor Delays at 2000 each is best.
Task creation screen
We Highly Recommend Using Basic View
Splash Release Checkbox
**If this is a Splash release you will need to add the splash page URL. You can get this by going to the Adidas.com site, it is the page with /yeezy at the end.
Auto Checkout Checkbox
When checked, the task will attempt to checkout as guest 3 times before creating an account with the catch all, logging in and sending the cart to your Discord webhook. From there, PD will attempt to checkout with the account.
When checked, you enter your Catch-All with no @ symbol. If your Catch-All is mycatchall.xyz, all you have to do is put that into to the field, nothing else. You cannot enter a Catch-All using Expert View.
When you have catch all checked, PD will create an account and send the cart to your Discord webhook. It will then open a browser window for you to attempt manual checkout.
- If you do not have a catch all leave this unchecked. You will have to checkout as a guest.
- If you do not have auto checkout checkbox enabled, the task will only send the cart to a browser window.
**If your webhook gives an error message after the item is carted, you can open adidas.com in your browser, copy/paste the Login:Password and checkout from there.**
How to Checkout Carts Manually
Method 1 - More Stable
Setup your tasks without Autocheckout checked. Once the item is carted, click the blue button on the right hand side of the task. A browser window will open for you to checkout.
Method 2 - Less Stable
First, make sure you have your Discord Webhook setup, enabled and saved in the Settings Tab. Second, you need to have an Incognito Chrome browser opened to https://www.adidas.com/us/myaccount-create-or-login You have to follow the steps in order, or it will not work.
- Wait for the task to send the Cart Info to your Webhook
- Copy the Proxy from the Webhook and paste into your Incognito Chrome Browser, you can do this in chrome://settings/?search=proxy+ Open the Proxy Settings > LAN Settings to input the Proxy info.
If you have User/Pass Proxies, once you Click OK to save, Refresh the page, you will be asked for the User/Pass info.
- Copy the HMAC Document Cookie from the Webhook
- On the https://www.adidas.com/us/myaccount-create-or-login page, right click anywhere and click Inspect.
- Open the Console Tab
- Paste the HMAC Cookie into the Console just like above.
- Login to the Cart here https://www.adidas.com/us/myaccount-create-or-login using the Adidas Login/Pass info from the Webhook and Checkout.
Monitor inputs for Adidas
URL - Enter the adidas product page link from the website. This can also be an early link, if you have one.
Example - https://www.adidas.com/us/pharrell-williams-solarhu-nmd-shoes/BB9531.html
SKU input for Adidas is very simple. Type SKU=SKU number here
Variants for Adidas are made up of the SKU (BB9531) and the size code (610). Combining them in this format: BB9531_610 creates the Adidas variant for the SKU in that size.
Here is the list of Adidas size codes for you to make your Variants.
1: 280 16: 760
1.5: 310 17: 780
2: 260 15: 750
2.5: 350 18: 790
3: 330 19: 800
4: 530 20: 810
4.5: 540 36: 530
5: 550 36 2/3: 540
5.5: 560 37 1/3: 550
6: 570 38: 560
6.5: 580 38 2/3: 570
7: 590 39 1/3: 580
7.5: 600 40: 590
8: 610 40 2/3: 600
8.5: 620 41 1/3: 610
9: 630 42: 620
9.5: 640 42 2/3: 630
10: 650 43 1/3: 640
10.5: 660 44: 650
11: 670 44 2/3: 660
11.5: 680 45 1/3: 670
12: 690 46: 680
12.5: 700 46 2/3: 690
13: 710 47 1/3: 700
13.5: 720 48: 710
14: 730 48 2/3: 720
14.5: 740 49 1/3: 730
Beginner View Adidas Task Setup
To prepare for an Adidas release, start with generating Cookies. Cookies for ADC are good for up to 5 days. Try to generate Cookies within 24 hours of the drop for best results. It’s recommended to have at least 5 times times the amount of Cookies per task. This means if there are 50 tasks, there should be at least 250 Cookies for that site. More Cookies is always better. Information on how to generate Cookies can be found in this guide:
First, select the region. The proxies MUST match the region or the site cannot be accessed. US = US proxies, UK = UK proxis, AU = AU proxies, etc.
Next, choose the monitor input to be used. SKU, Variant or URL.
Now, decide if there will be a Catch-All email used or not.
It is recommended to enter Adidas proxies into the Global pool, this allows the tasks to be made in the Basic View. The main reason is when Adidas is used with Proxy Groups, the Proxies don’t rotate, meaning a dead proxy will make that task useless. If other tasks are being run at the same time, enter those proxies into Proxy Groups.
Next, set Error & Monitor Delays between 2000-3000. Lastly, select Sizes or use Random sizing and select Profiles.
DO NOT START TASKS UNTIL PRODUCT IS LIVE!
To know when the product is live, open adidas.com in a browser and wait in the splash. Once you see the sizes pop-up on the page, that means the product is loaded. Now, you can start your tasks. Errors are normal, let your tasks run for the entire release.
Q: Will more Adidas regions be added?
A: Make a suggestion if you want your region added.
Q: How do I use my catchall?
A: Expert View will use Account Groups and with Beginner View you can enter the catchall in the task creation screen.
Q: What proxies do I use for Adidas?
A: Residential Proxies or Localhost (Your Home IP). You can run 10-15 tasks on your Home IP.
Q: How do I set up a cart webhook?
A: Watch this video https://www.youtube.com/watch?v=T1-onadkl1M&t=7s
Q: When do we start tasks?
A: Only start tasks when the product is loaded. We will try to announce when you should start all tasks. DO NOT start when the waitroom goes live, as the product usually isn't loaded immediately.
Q: What delays do I use for Error and Monitor:
A: 2000 for both. PD needs 1-5 requests to get past Akamai (Adidas anti bot), with at least a 2000 delay. After a few releases, we found that 2000 is best.
Q: What is Waiting Room, Splash and FCFS
A: Waiting Room and Splash are both Adidas queue methods. For both Waiting Room releases and Splash releases ensure the Splash Release checkbox is checked at task creation. FCFS is First Come First Served so there is no queue, ensure Splash Release checkbox is not checked at task creation.
Q: Does my region have Auto Check Out?
A: ACO is supported by all regions except AU and CA as of now.
Q: What is attempting to pass. (Splash)
A: This is the bot attempting to bypass the splash page. This a normal step in the procedure.
Q: What is 403 error & why did my browser open to that page?
A: You’ll receive 403 (Blocked) error when there are too many requests coming from your ip address to Adidas site. If your browser opens with this error use a mobile or incognito browser to login to the account and checkout manually. If you get 403 in browser you should fall back to carts if you can.
Q: Why are all of my tasks stuck on monitoring?
A: Adidas uses a system where they are able to load and remove stock at will. If a stock is not live yet or has been pulled you will see Monitoring on those tasks until stock is added once again. If you are 100% certain stock is live you are advised to double check your SKU, ensure there are no spaces between SKU=XXXXXX and confirm that your proxies are not banned on Adidas.
Q: What is Auth Failed?
A: Normal Error for getting past Akamai