TargetGO
Complete guide on our TargetGO module
Our Target module supports account-based checkout and requires proper session setup, ATC (Shape) cookies, and carefully structured task groups to run smoothly. Target is one of the more complex retail sites due to strict bot protection, one-checkout-per-account limitations, and frequent restock cycling.
Stellar simplifies this process through automated login handling, on-demand cookie generation, monitor-to-checkout workflows, and now Pickup-specific monitoring and checkout support. This module is ideal for retail restocks, collectibles, household items, and products that frequently go in and out of stock without notice.
Video Guide
Please subscribe to our Stellar AIO YouTube channel! You'll help us unlock more features that'll be beneficial to all Stellar members
Quick Start (Recommended Setup)
(For members who want the TL;DR)
Run Target locally, not on a server
Add your Target accounts under Identities → Sessions
Use Token Login for a small number of accounts OR Request Login + IMAP Session for scaling
Install the Stellar Target Browser Extension
Generate ATC cookies using the extension
Create a Tag Group containing all SKUs you want to run
Run 1 Monitor task per Tag Group
Run exactly 1 Checkout task per Target account
Shipping Mode or Pickup Mode
Watch Task enabled
For Pickup:
Use the same ZIP code in Monitor-Pickup and Pickup tasks
Use ISP proxies and recommended delays
Test on an in-stock item before major drops
Preliminary Checklist
Before setting up tasks on Target, make sure you have everything below prepared:
Profiles
Profile email must match the Target account email
Billing & shipping should mirror your Target account (unless using Override Payment)
Proxies
ISP proxies – Recommended for all of your tasks.
If you're looking for proxies, check out Stella Proxies for high quality ISP and Residential proxies.
Target Accounts
One checkout task per account
Accounts do not need pre-saved address or payment
Stellar handles matching or adding automatically
Stellar AIO Target Browser Extension
Download and install our browser extension app Stellar AIO Target Browser Extension V3. Please note this extension will be required to run our target module. Must remain open while tasks are running
Cook Group Access
Optional but recommended. Your cook group can help you find product URLs, SKUs and early restock alerts.
Test Task
Before big drops, run a test task on a random in stock product to confirm your profile, account, proxies and delays are functioning correctly.
Running on a Server
Warning Target is NOT recommended on servers because most IPs are flagged.
If you insist:
Your server IP must be clean
Test by logging in → add item → attempt checkout → ensure order remains for hours
If purchasing a server, confirm IP cleanliness with provider
Best performance = local PC
Login Methods & Sessions
For Target you'll need to go into the Identities tab, enter in your accounts so your checkout tasks can log in. There are two ways to log into your Target accounts, Access Token Login or Request Login. Each login method will require shape cookies. The Target account email has to exactly match the email you have in your profile
Recommended Login Strategy
Token Login
Best for small setups (a few accounts)
Most stable
Least Shape friction
Request Login + IMAP Session
Best for users running ~10–20 accounts
Enables automatic OTP handling
No manual login method selection needed
Regular Request Login without IMAP is not recommended.
Adding a Session
Go to Identities → Add Session
Fill:
Session Name
Email
Password
Access Token (if applicable)
Login Method (Request or Token)
Save — login occurs when checkout tasks begin
IMAP Sessions
IMAP Sessions are now supported in:
Checkout tasks
Login mode
Reset mode
When using Request Login, simply select an IMAP session:
Stellar will automatically handle OTP emails
No manual code entry required
No need to select or configure a login method
If you are using Token Login, IMAP is not required.
Mass Import Sessions
Import multiple accounts at once
Accounts do not log in until tasks run
Email must match the profile email or the login will fail
Go to Sessions tab
Click on Mass Import Sessions
On this window you will be inputting multiple accounts at once (one per line). The format is as follows:
Request Login
No extensions required.
1. Add or edit session
2. Choose Target
3. Select Request Login in the login method field. The Target account email has to exactly match the email you have in your profile
4. Click Save
5. Run a Shipping task (OOS or in-stock) to complete login + cookie steps
6 . If Request Login fails repeatedly, switch that account to Token Login
Access Token Login
How It Works
You generate a login token using the Stellar Shape Module or the Stellar Chrome Extension
Token lasts days/weeks but invalidates if you sign out
Still requires login cookies
Request login method is recommended more than Token login method
Downloading Access Token Harvester
1. Download: Stellar AIO Target Browser Extension V3
2. Extract the downloaded file
3. In Chrome, go to Manage Extensions
4. On the top right corner of the Manage Extensions page turn on Developer Mode and click Load Unpacked. Now select the folder that you extracted, it'll be located in Downloads
You can ignore the red "Errors" manage shown in the image above
5. Go to https://www.target.com/ and navigate to the login page. Enter your email address and password, (Before you sign in, check the 'Keep me signed in" box) then click sign in. You have to use your real email and password so you can successfully log into your account.
Do not sign out of the Target accounts. This will cause your login tokens to become invalid and you won't be able to log into your accounts in bot. You can simply close the window after copying the login token
6. Copy the Login Token
Paste the Login Token into the correct Target accounts session
Click Save and you're all set with that account. Your checkout tasks will log you into your Target accounts
Do not sign out of the Target accounts in the browser you created the login token. This will cause your login tokens to become invalid and you won't be able to log into your accounts in bot. You can simply close the window after downloading the login token. You can use a new incognito window or new Chrome profile per Target account
Repeat the same process for each Target account you have by either opening a New Incognito Window or use a new Google Chrome profile
You'll also want to switch the browser login IP so multiple Target accounts aren't using the same IP to login. You can use any proxy switcher chrome extension but we recommend BP Proxy Switcher
New Incognito Window
Open a New Incognito Window by clicking on the 3 dots on the top right corner of Chrome and click "New Incognito Window"
To use a Chrome extension in Incognito, copy and paste chrome://extensions into the URL bar in Incognito mode
Go to the Token Harvester extension > "Details" > Toggle ON "Allow in Incognito"
Google Chrome Profile
To create a new Google Chrome profile click on your Google account image on the top right corner and click on "Add"
Sign into your Gmail accounts. One Chrome profile per Target account you have
ATC Cookies Overview
ATC cookies are required for:
Add to cart
Passing bot protection
Checking out high demand items
Cookies are account-independent.
How do I generate ATC Cookies?
(Recommended) Stellar Target Browser Extension
Shape Blocks & Device Warnings (Very Important)
If you are experiencing full Shape blocks (not just a single failed ATC or captcha), this likely indicates device-level detection.
Recommended action:
Stop all Target tasks immediately
Close all captcha harvesters
Let your device rest for 24–48 hours with no Target activity
If after resting, Shape blocks continue:
This indicates a full device ban
Device bans are not fixable
This is a common outcome with Shape when limits are exceeded
Continuing to run tasks or harvesters while blocked will only make it worse.
Installing Stellar Target Browser Extension
This browser extension is needed if you don't want to use the Shape module to generate ATC cookies
Download: Stellar AIO Target Browser Extension V3
2. Extract the downloaded file
3. In Chrome, go to Manage Extensions
4. On the top right corner of the Manage Extensions page turn on Developer Mode and click Load Unpacked. Now select the folder that you extracted, it'll be located in Downloads
You can ingore the red "Errors" message shown in the image above
Generating ATC Cookies Using Extension
Go to https://www.target.com/ and navigate to any in stock item
Open your pinned Stellar browser extension
We recommend to enter your proxies you want to use when generating ATC cookies. These could be ISPs or residentials
Now toggle on both "Enable Extension" and "Enable Generator"
Your browser must remain open and visible so the extension can automatically generate cookies that'll automatically be used in the bot
Cookies are generated on demand when the bot needs them
Browser Extension & Proxy Conflicts (Important)
When using the Stellar Target Browser Extension, you must not have any other proxy-switching browser extensions enabled at the same time.
The Stellar extension handles proxy switching internally. If another extension (such as BP Proxy Switcher or similar tools) is active, both extensions will attempt to control the browser proxy at once. This causes a conflict where the proxy gets stuck switching indefinitely, preventing cookies from generating.
Before running Target tasks or generating ATC cookies:
Disable or remove all proxy switcher extensions in Chrome
Only keep the Stellar Target Browser Extension enabled
Do not use BP Proxy Switcher or similar tools while the Stellar extension is running
Failure to do this will result in:
ATC cookies not generating
Tasks stuck waiting for Shape cookies
Infinite proxy switching loops
This is a required step for the Target module to function correctly.
Tags (Required)
You must group SKUs using Tags because Target only allows one checkout task per account.
Navigate to the Tags tab of the bot
Click on the green + symbol to create a Tag group
Enter a Tag group name (Ex. Target)
Click on Manage SKUs button and you can start entering the product SKUs you're interested in
Maximum number of SKUs per task is 30. Avoid massive lists, only add SKUs that actually restock. You can select multiple tag groups in a task but you cannot exceed 30 SKUs in one task.
You can now select a Tag Group during task creation (Input List field)
Task Modes
Monitor Mode
Monitor-Pickup Mode
Shipping Mode (Checkout)
Pickup Mode
Login Mode
Reset Mode
Account Gen Mode
You can only run one checkout task per Target account. This ensures a smoother checkout process and helps prevent account locks. There is no limit on Monitor mode tasks
Task Modes
Monitor Mode
Monitors SKUs
Pings checkout tasks
No checkout occurs here
Monitor-Pickup Mode
Monitor Mode for in-store pickup
Requires ZIP Code and Radius
Detects local store inventory
Shipping Mode (Checkout)
Used for shipped orders
Handles login and checkout
Pickup Mode (Checkout)
Used for in-store pickup
Requires ZIP Code and Radius
ZIP must match Monitor-Pickup
Login Mode
Logs into accounts
Supports IMAP OTP
Reset Mode
Resets passwords
Recommended for scaling
Passes Shape more reliably than login
Account Gen Mode
Use Account Gen mode to generate new Target accounts
Very strict Shape protection
Not recommended to spam
Using Pickup & Monitor-Pickup Correctly
Monitor-Pickup tasks monitor local store inventory.
Pickup tasks checkout only after being pinged.
ZIP Code must match between monitor and checkout.
Radius determines how far from ZIP the bot checks stores.
Setup mirrors Shipping workflows, with added location fields.
Pickup is best for:
Low-key restocks
Household items
Non-hype products
Profiles
Override Payment = use Stellar profile card instead of Target account card
Leave unchecked if using Target’s saved payment
Email must match Target account email
Proxies
Use ISPs or strong DCs
Avoid burning resi data for monitoring
If you're looking for proxies, check out Stella Proxies for high quality ISP proxies
Input List
Select the Tag group you want to run which should have a full list of SKUs you entered when creating the Tag group
You can enter multiple SKUs in one tag group but the bot only purchases one SKU per checkout, it does not checkout multiple SKUs in one order
Maximum number of SKUs per task is 30. Avoid massive lists, only add SKUs that actually restock. You can select multiple tag groups in a task but you cannot exceed 30 SKUs in one task.
Delays
Monitoring Delay → 8000–15000 ms
Checkout Delay → ≤3000 ms
Reset Delay → ≤10000 ms
Always run at least 1 monitor per product
Quantity (QTY)
It's best to check with your cookgroup for quantity recommendations as different products may have different purchase limits set by the site
Stellar does not automatically adjust the quantity if you set a number higher than what's allowed
Monitor type
API → backend checking (Recommended)
ATC → frontend checking
Monitor High Stock (10+) Only
Enable this option if you want monitor tasks to only trigger when 10 or more units are available
This helps reduce false positives where items appear in stock but sell out immediately or are not actually available for checkout
Endless Mode
Repeats checkout attempts after success
Endless Limit = max number of checkouts per task
Override Payment (Pickup Mode)
Only check if adding a new card or intentionally bypassing Target account payment
Watch Task (Highly Recommended)
Checkout task waits for Monitor task to ping
Easier on proxies
Faster response time
Lower risk of Target throttling
Cashback Integrations
IMAP Sessions
IMAP will allow Stellar to automatically pull the account verification codes that Target emails you for a faster and smoother experience
Password
You can choose your new password or Stellar will create a safe one
Task Strategy & Timing
How Many Monitor Tasks Should I Create?
Run 1 Monitor task per Tag Group.
A single monitor can safely handle up to 30 SKUs within one Tag Group.
You can run multiple Monitor tasks if you want redundancy, but it’s not required and usually unnecessary.
Monitor tasks are lightweight and can run 24/7.
Recommended: 1 Monitor task per Tag Group is sufficient for most users.
How Many Checkout Tasks Per Account?
Strictly 1 checkout task per Target account.
This applies to Shipping Mode and Pickup Mode.
Running more than one checkout task on the same account can cause:
Account locks
Checkout failures
Login/session instability
Rule: 1 account = 1 checkout task (no exceptions).
When Should I Start Monitor Mode Tasks?
Start Monitor tasks early and let them run continuously.
For random restocks, monitors should already be running before the item restocks.
For known drops, start monitors 5–15 minutes before the expected restock time.
Best practice: Monitors should always be running first and waiting.
When Should I Start Checkout Tasks?
Checkout tasks should be started after monitors are running.
Checkout tasks should sit in Waiting / Watch mode until pinged.
For known drops, start checkout tasks at the same time or shortly after monitors.
For random restocks, checkout tasks can safely run 24/7 as Watch Tasks.
Important: Checkout tasks should never be your primary monitoring source. They rely on monitors to trigger clean, fast checkouts.
Recommended Flow
Start Monitor tasks first
Start 1 Checkout task per account (Watch Task enabled)
Let monitors ping checkout tasks on restock
Checkout tasks ATC and checkout immediately
This setup minimizes proxy usage, reduces Target throttling and keeps sessions stable.
Using Red Card on Target
A Red Card is a Target branded debit or credit card. You can apply for one here
Putting the RedCard into Stellar
1. In bot, go to the profile section of Target
2. Edit the profile you would like to add the Target RedCard to (or create a new profile)
3. When entering the credit/debit card information click the Visa card option
4. The CVV is the 4 digit pin the Red Card is issued with
5. Make sure your tasks have Override Payment? box checked
Error Messages & Fixes
Shape Ban
Cause: Target is not accepting the cookies being generated
Fix:
Try different proxies
Use a different browser
Increase task intervals
The address on the profile may be flagged. Use a new address or profile
Shape Blocks & Device Warnings (Very Important)
If you are experiencing full Shape blocks (not just a single failed ATC or captcha), this likely indicates device-level detection.
Recommended action:
Stop all Target tasks immediately
Close all captcha harvesters
Let your device rest for 24–48 hours with no Target activity
If after resting, Shape blocks continue:
This indicates a full device ban
Device bans are not fixable
This is a common outcome with Shape when limits are exceeded
Continuing to run tasks or harvesters while blocked will only make it worse.
Cart Item Manually – Restart Task
Cause: Session expired
Fix:
Stop the task
Go to the Sessions tab
Open the account session
Click Open Browser
Manually cart an item in that browser
Restart the task to revalidate the login
Waiting for Shape Cookie
Cause: Task requires at least one cookie to continue running
Fix:
For login: generate 1–2 login cookies using the Shape module
For ATC: continuously generate cookies while tasks are running
Last updated
Was this helpful?