> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/retailers/target.md).
# Target
Stellar AIO 4.0 guide to Target accounts, Shape Harvesters, monitoring, and checkout.
Target is an account-based retailer protected by Shape. This guide covers the Stellar AIO 4.0 interface, account preparation, Shape Harvesters, monitoring, and checkout.
### Video Guide
This video shows an earlier Stellar interface. Use the written 4.0 instructions and screenshots below for current controls. The extension is used for Token Login; use Harvesters → Shape Harvesters for login and ATC cookies.
{% embed url="" %}
### What changed in Stellar 4.0
Use **Harvesters → Shape Harvesters** to generate Target cookies. A Target Shape Harvester produces cookies usable for both **login and add-to-cart (ATC)** automatically. There is no endpoint to select and no separate Shape or ShapeV2 task module to create.
Add Target credentials under **Accounts**. Target tasks now use the **Account** and **OTP Input** fields. The browser extension is only needed for the backup Token Login method.
Screenshots show the 4.0 forms. Blank fields and default switches are not a complete recommended setup; apply the settings described below and follow current Stellar release announcements.
### Quick Start: Recommended Setup
1. **Prepare accounts and profiles.** Use one Target account per active Shipping or Pickup task. Match the account email to its Stellar profile, and verify the intended address and payment method. Do not run Shipping and Pickup simultaneously on the same account.
2. **Add accounts.** Open Accounts, choose Target and the appropriate account group, then select Add Account. Enter the account name, email, and password. Select Request Login and save.
3. **Prepare verification codes.** Configure your email connection in IMAP if using automatic email retrieval, then select IMAP in the task’s OTP Input field. Manual and AYCD are also available; choose the method you have configured.
4. **Add products.** Create a group in Tags and use Manage SKUs. Select that group through Input List on both the Monitor and checkout tasks.
5. **Start Shape Harvesters.** Open Harvesters → Shape Harvesters → Create Shape Harvester(s). Select Target, configure the browser and proxy group, and confirm successful cookie generation. The same cookies support login and ATC.
6. **Prepare login.** Create Target Login tasks with the matching Profile, Account, Checkout Proxy, and OTP Input. Start them after cookies are available and confirm successful sign-in. Stop the Login tasks when preparation is complete, but keep Shape Harvesters running for checkout.
7. **Start monitoring.** Use Monitor for Shipping, or Monitor Pickup for Pickup. Start with one Monitor per Tag Group and a Monitoring Delay of 8000–15000 milliseconds, adjusted for current release guidance.
8. **Start checkout tasks.** Select the matching account, profile, and Input List. Enable Watch Task. For Shipping, start with Delay 3000 or lower according to current drop guidance. Set product quantity to the release limit.
9. **Check the setup.** Confirm accounts are signed in, harvesters are supplying cookies, Monitors are active, and checkout tasks are waiting for the correct Monitor. Keep Shape Harvesters running during the drop.
Shipping tasks can also initialize login. Dedicated Login tasks make it easier to prepare and verify accounts before a release.
### Accounts and Login
#### Add a Target Account
Open **Accounts → Target**, select or create an account group, and choose **Add Account**. Fill in Account Name, Account Email, and Account Password. Use **Request Login** for the standard setup. The Access Token field is for the backup Token Login method.
The email on the Target account must match the selected Stellar profile. Use a unique account for each active checkout task, and verify the account manually before an important release.
#### Request Login and OTP Input
Request Login uses the saved account credentials. Have Target Shape Harvesters producing cookies before you start login. Keep the harvesters running afterward because checkout uses the same cookie supply.
Target may email a one-time verification code. In the task’s **OTP Input** menu, choose **IMAP** for your configured email retrieval, **Manual** to enter codes when prompted, or **AYCD** if you have configured that integration. The 4.0 task form does not use the old IMAP Session selector.
For IMAP, check the mailbox connection and any forwarding rules before the release. Make sure verification emails for the selected account reach the expected inbox.
#### Token Login (Backup Method)
Use Token Login when Request Login is unavailable or Stellar staff recommends it. The Stellar Target Browser Extension supplies the login token; it does not replace Shape Harvesters.
1. Download the [Stellar AIO Target Browser Extension V3](https://drive.google.com/drive/folders/136nPcGwzFRLuLvtgaQyK1kVKf02QcQe9?usp=drive_link) and extract the archive.
2. In Chrome, open Manage Extensions, enable Developer Mode, and choose Load Unpacked. Select the extracted extension folder.
3. Use a separate browser profile for the intended Target account. Sign in and keep Keep Me Signed In enabled.
4. Open the Stellar Target Browser Extension and use **Target Login Token**.
5. Open the matching account in Stellar, select **Token Login**, paste the token into **Access Token**, and save.
Do not sign out of the browser session used to obtain the token; doing so may invalidate it. Keep accounts separated. Leave the extension’s cookie generator off and continue using Target Shape Harvesters for checkout.
#### Install the Target Browser Extension for Token Login
1\. Download Stellar AIO Target Browser Extension V3 using the link above.
2\. Extract the downloaded archive.
3\. In Chrome, open Manage Extensions.
4\. Enable Developer Mode, select Load Unpacked, and choose the extracted extension folder.
5\. Confirm the Stellar Target extension appears in Chrome, then follow the Token Login steps above.
### Shape Harvesters
**What is Shape?** Shape is the anti-bot protection used by Target. It evaluates browser, device, and behavior signals to help distinguish normal visitors from automated traffic and decide whether to allow a request.
**What is a Shape Harvester?** A Shape Harvester is a tool inside Stellar that uses a browser to generate the Shape data your Target tasks need. It supplies this data in the background while your tasks handle login and checkout.
**What is a cookie (also called a header)?** A cookie is a small piece of data a website stores in a browser and receives back with later requests. In Stellar’s Target setup, members commonly call the generated Shape data “cookies” or “headers.” These terms refer to the data supplied by the harvester here, although cookies and HTTP headers are technically different things. This data helps Target evaluate the request; it is separate from your account password or login token.
**Why are these cookies required?** Target checks protected requests, including login and add-to-cart (ATC), for valid Shape data. Without a usable supply, Stellar may show “Waiting for Shape Cookie,” or Target may reject the request. In Stellar 4.0, the same Target Shape Harvester supplies both login and ATC cookies automatically. Keep harvesters running while your tasks need them because cookies expire. Having cookies does not guarantee a successful login or checkout.
Open **Harvesters → Shape Harvesters → Create Shape Harvester(s)**. These harvesters replace the old separate cookie-generator task workflows.
* **Site:** Target.
* **Cookies Per Task:** Start with 3.
* **Cookie Expiration:** Start with 300000 milliseconds (five minutes).
* **Browser:** Start with a small mix of supported browsers such as Edge, Brave, Firefox, or Safari where available. Aloha is another option for variety.
* **Proxy Group:** Use clean, high-quality ISP or residential proxies and compare results with your setup.
* **Start Time / End Time:** Optional scheduling controls.
* **Qty:** Number of harvesters to create. Start small and scale based on usable cookie production and computer performance.
**No Login/ATC endpoint selection is needed.** Cookies from these Target harvesters can be used for either operation. Confirm successful generation before starting Target tasks, then keep harvesters running while Shipping or Pickup tasks are active. Cookies expire, so generating a batch long before a drop is not a substitute for maintaining a supply during it.
#### Browser Choice and Harvester Count
There is no fixed ratio of harvesters to checkout tasks. Increase gradually only when tasks consume usable cookies faster than you produce them. You do not need one harvester for every browser.
The existing starting recommendation favors Edge, Brave, Firefox, and Safari over Chrome for Shape generation. Compare results on your own device, operating system, and proxies; browser performance can change with Target’s protection. Chrome used for the Token Login extension is separate from the browser selected in a Shape Harvester.
Too many harvesters can increase CPU, memory, and proxy usage, slow the browsers, and contribute to bans. Keep reliable combinations, avoid repeatedly restarting a failing setup, and allow your device and proxies to rest after repeated blocks.
### Target Tag Groups
1. Open **Tags** and create a recognizable group.
2. Open **Manage SKUs** and add the products you intend to monitor.
3. Save the group and select it through **Input List** on the paired Monitor and checkout tasks.
Enter each product using **TCIN;Product Name;Max Price**. For example:
```
12345678;Product Name;500
```
The TCIN identifies the product, the name helps you recognize it, and Max Price limits the price the task should pay. A task supports up to 29 products across its selected Tag Groups. Selecting multiple products does not make a multicart order; a checkout task purchases one monitored product per checkout.
Restart affected checkout tasks after changing a Tag Group so they load the updated products.
#### **Example: Pair a Monitor with a Shipping Task**
This example uses one Monitor task and one Shipping task with a Tag Group named **Target**. The Monitor checks for stock. The Shipping task uses your account and profile to attempt the purchase when the Monitor signals stock.
**1. Prepare one shared product list.** In **Tags**, create a group named **Target** (or use your own name). Open **Manage SKUs**, add the intended products using the format above, and save. Both tasks below must select this same group in **Input List**.
**2. Create the Monitor.** In your Target task group, click **Create Task**. Select **monitor**, name it **Target - Monitor Example**, and select **Target** in **Input List**. Choose your Monitor Proxy group and set **Monitoring Delay** to **10000** milliseconds (10 seconds), a starting example within the recommended 8000–15000 range. Leave the bottom task **Qty** at **1** and click **Create**. Follow newer release guidance if it recommends different settings.
The Monitor example below shows the shared Input List and delay. Select your own Monitor Proxy group before creating it.
**3. Create the Shipping task.** Click **Create Task** again and select **shipping**. Name it **Target - Shipping Example**. Select the matching **Profile** and **Account**, your **Checkout Proxy** group, and the **OTP Input** method you have configured. Select **Target** in **Input List** and enable **Watch Task** so this task waits for the Monitor’s stock signal.
For this example, use **Delay 3000** and product **Qty 1**, adjusted to current drop guidance and the retailer’s quantity limit. Leave the bottom task **Qty** at **1** to create one Shipping task. Use only one active checkout task per account. Click **Create** after completing the required fields.
The Shipping example below highlights the same Input List and Watch Task enabled. The Profile, Account, Checkout Proxy and OTP Input fields are blank only for illustration; select your own before creating the task.
**4. Prepare login, then run the pair.** Start your Target Shape Harvesters and confirm they are generating cookies. Complete the login preparation above and confirm the selected account is signed in. Start the Monitor and Shipping tasks, keeping Shape Harvesters running throughout the drop. The Monitor checks the products in Target; the Shipping task waits for a stock signal and then attempts checkout using its selected account and profile.
**Check the connection:** If Shipping is not responding as expected, confirm both tasks are running, both select the same Input List, Watch Task is enabled on Shipping, the account is signed in, and Shape cookies are available. Waiting for stock is normal when the monitored products are unavailable. If you change the Tag Group’s products later, restart affected checkout tasks so they load the updated list.
### Task Fields and Modes
Create a Target task group and select the mode appropriate for the task. The 4.0 modes are **shipping, pickup, monitor, monitor-pickup, login, reset, account-gen, and cancel-last-order**.
#### Common Fields
* **Name:** Optional task label.
* **Profile:** The profile matching the Target account.
* **Checkout Proxy:** Proxy used for login and checkout; start with clean residential or ISP proxies.
* **Monitor Proxy:** Proxy group used to watch inventory; high-quality ISP proxies are the starting recommendation.
* **Input List:** Your Target Tag Group.
* **Account:** The saved Target account assigned to the task.
* **OTP Input:** IMAP, Manual, or AYCD for verification codes.
* **Delay:** Request timing. Follow the guidance for the selected mode and release.
* **Start Time / End Time:** Optional timing controls. Setting a Start Time does not itself start a task.
* **Qty at the bottom of the form:** Number of task copies to create. This is separate from the product quantity field.
Check the purchase limit before running checkout tasks. Stellar does not automatically correct an invalid product quantity.
#### Shipping
Select **shipping**, the matching Profile and Account, a Checkout Proxy, and the same Input List as your Monitor. Use the configured OTP Input method, set product quantity to the release limit, and follow current drop guidance for Delay (3000 or lower is the existing starting recommendation).
* **Watch Task:** Enable for the recommended setup so Shipping waits for a Monitor signal.
* **Extra Item TCIN:** Optional additional item. Leave blank unless intentionally needed.
* **Endless:** Allows further checkouts after success; use the available limit to control how many successful checkouts are allowed.
* **Rakuten / TopCashback:** Optional integrations configured in Stellar’s Settings.
Use one active Shipping or Pickup task per account. Keep Shape Harvesters running throughout checkout.
#### Pickup
Select **pickup** and configure the matching Profile, Account, Checkout Proxy, Input List, and OTP Input. Set **ZIP Code** and **Radius** for the intended pickup area. Pair with Monitor Pickup using the same Tag Group and ZIP Code, with an appropriate matching search area.
Enable **Watch Task**. Extra Item TCIN, Endless, and the cashback integrations are optional. Verify the intended payment method before the release. Do not run Shipping simultaneously on the same account.
#### Monitor
Select **monitor**, a high-quality Monitor Proxy group, and the Input List shared with Shipping. Start with **Monitoring Delay 8000–15000 milliseconds** and one Monitor per Tag Group; add a second only if needed.
**Monitor High Stock (10+) Only** filters out smaller restocks and may miss inventory you would otherwise want. **Reset Delay** controls the pause before another trigger. Start Time, End Time, and the bottom Qty field are also available. Monitor tasks detect stock; they do not place orders.
#### Monitor Pickup
Select **monitor-pickup**, your Monitor Proxy group, and the Input List shared with Pickup. Set the required **ZIP Code** and intended **Radius**. Match the paired Pickup setup. Start with a Monitoring Delay of 8000–15000 milliseconds and adjust for current guidance. Reset Delay and scheduling controls are available.
#### Login
Select **login**, the matching Profile and Account, a clean Checkout Proxy, and the appropriate OTP Input. Configure Delay and optional scheduling. Enable **Add Address** or **Add Payment** only when you intend to add the selected profile’s details to the account.
Start after Target Shape Harvesters have produced cookies. Once sign-in is complete, stop Login tasks. Keep Shape Harvesters running for the subsequent checkout tasks.
#### Reset
Select **reset**, the matching Profile and Account, a Checkout Proxy, the intended new Password, and the appropriate OTP Input. Configure Delay and optional scheduling. The form uses OTP Input rather than the old IMAP Session selector.
This mode changes the account password. Confirm the intended account and retain the new credentials before using it. Use current Stellar support guidance when troubleshooting a login problem.
#### Account Gen
Select **account-gen**, the Profile containing the intended email and account information, a clean Checkout Proxy, and the desired Password. Configure Delay, scheduling, and task Qty. Add Address and Add Payment are optional.
Account generation is heavily Shape-protected. Start with a small setup and avoid repeatedly sending failed requests through the same proxy pool.
#### Cancel Last Order
Select **cancel-last-order**, the associated Profile and Account, the required Checkout Proxy and TCIN, and the appropriate Delay. Optional scheduling and task Qty are available.
Use this mode only when you intend to cancel an order. Confirm the account and TCIN before starting; cancellation may be difficult or impossible to reverse.
### Common Errors and Fixes
#### Waiting for Shape Cookie
Check **Harvesters → Shape Harvesters**. Confirm Target is selected, harvesters are running, and usable cookies are being generated. The same pool supports login and ATC, so there is no endpoint to switch.
Check Cookie Expiration and Cookies Per Task, then review browser and proxy performance. Test another clean proxy group or supported browser if generation fails. Restart failed harvesters selectively and reduce excessive counts. Increase the number only when successful cookie production cannot keep up with consumption. Do not use the extension’s cookie generator as a replacement.
#### Waiting for a Verification Code
Check the task’s OTP Input selection. For IMAP, verify the connection, inbox, account email, and forwarding rules. For Manual, retrieve and enter the code when prompted. For AYCD, check the configured integration.
#### Account Will Not Log In
Check the account and profile emails, credentials, login method, verification-code retrieval, and Checkout Proxy. Confirm that Target Shape Harvesters are producing fresh cookies. Use a Login task to prepare the intended account, and try a clean proxy if the current one fails.
#### Token Login Is Not Working
Confirm the token came from the intended Target account and is saved in that account’s Access Token field with Token Login selected. Signing out of the originating browser session may invalidate it. Obtain a fresh token if needed, or use Request Login when available. Ask Stellar support if the problem persists.
#### Shape Ban or Full Device Block
Target can reject cookies, proxies, browser or device characteristics, or account/profile information. Reduce excessive harvesters, try a clean proxy pool or supported browser, and avoid repeatedly restarting the same failing setup.
For repeated full blocks or device warnings, stop Target tasks and cookie generation and allow the device and proxies to rest. Existing troubleshooting guidance suggests 24–48 hours before testing a smaller setup with different proxies; follow newer staff guidance if provided.
#### Monitor Does Not Trigger Checkout
Confirm the Monitor is active, the paired tasks share the intended Input List, the TCIN and Max Price are correct, and Watch Task is enabled. Check stock and any high-stock filter. After Tag Group edits, restart affected checkout tasks.
For Pickup, also check matching ZIP Codes, the intended Radius, and local store inventory.
#### Queue, Rate Limit, or Submitting Checkout
These statuses can occur during busy releases. Allow tasks to progress while checking the account, payment, profile, proxies, and cookie supply. Avoid restarting every task unless Stellar staff announces that a restart is needed.
#### Account Instability or Wrong Payment
Check for duplicate active checkout tasks using one account. Keep only one active Shipping or Pickup task per account. Confirm the assigned Account and Profile and the intended payment details before running.
#### Additional Factor Required
Check the affected account and current Stellar login guidance. Contact support before changing authentication settings or resetting credentials; use Reset only when that is the intended troubleshooting action.
### Before the Drop
* Update Stellar and read the latest release instructions.
* Confirm accounts are signed in and match their profiles.
* Confirm Target Shape Harvesters are producing cookies and remain running for login and checkout.
* Check Input Lists, product limits, Monitors, and Watch Task.
* Use one active checkout task per account.
* Monitor computer load, usable cookie availability, and proxy performance before scaling.
* Keep watching for later stock waves.
### Video Reference
[Watch the earlier Target setup video](https://www.youtube.com/watch?v=pfYNamA1GeY). It shows an older interface. Follow this written 4.0 guide for Accounts, OTP Input, and Shape Harvesters; older separate-generator and extension cookie-generation instructions no longer apply.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guides.stellaraio.com/stellar/retailers/target.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
