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
New video guide coming soon...
Quick Start (Recommended Setup)
(For members who want the TL;DR)
Add your Target accounts under Identities → Sessions using Request Login.
Generate ATC Cookies using the Stellar Target Browser Extension.
Create one Tag Group containing all SKUs you want to run.
Run 1 Monitor task per Tag Group.
Run strictly 1 Checkout task per Target account:
Shipping Mode or Pickup Mode
Watch Task enabled
For Pickup, use the same ZIP code in both Monitor-Pickup and Pickup tasks.
Use ISP proxies and recommended delays.
Run Target locally, not on a server.
Before major drops, run a test task on an in-stock item.
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 should have saved address + payment unless you override it
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.
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 (recommended). Each login method will require shape cookies. The Target account email has to exactly match the email you have in your profile
Which is better, Access Token or Request Login?
Request Login → Recommended
Access Token Login → Backup option
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
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 (Recommended)
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 (Advanced)
How It Works
You generate a login token using the Stellar Shape Module
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
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
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
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
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 Overview
Monitor Mode
Monitors SKUs and pings checkout tasks.
No checkout occurs here.
Monitor-Pickup Mode
Monitor Mode specifically for Pickup.
Requires:
ZIP Code
Radius
Used to detect local store availability.
Shipping Mode (Checkout)
Used for shipped orders.
Handles login and checkout.
Pickup Mode (Checkout)
Used for in-store pickup.
Requires:
ZIP Code
Radius
Must match Monitor-Pickup ZIP Code.
Login Mode
Logs into accounts and refreshes sessions.
Reset Mode
Resets account passwords.
Account Gen Mode
Generates new Target accounts.
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
Endless Mode
Repeats checkout attempts after success
Endless Limit = max number of checkouts per task
Use Account Address (Recommended)
Uses Target account's saved address
Override Payment
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
Used for Reset mode
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
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
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?