> 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/targetgo.md). # TargetGO
Target is an account-based retailer with strict protection known as **Shape**. Successful Target setups require several components to work together Target is one of the more advanced modules in Stellar. Most problems come from missing cookies, mismatched accounts and profiles, poor proxies, or running too many tasks and cookie generators *** ## Video Guide Watch the complete Target setup {% embed url="" %} *** ### Quick Start: Recommended Setup This is the standard Target Shipping setup. Members should follow these steps in order. #### 1. Prepare Your Accounts and Profiles * Create one Target account for each checkout task. * Save a valid shipping address and payment method on each Target account. * Create one matching Stellar profile for each account. * Make sure the Target account, Target session, and Stellar profile use the exact same email. * Do not run the same Target account on multiple active checkout tasks. The rule is: ``` 1 Target account = 1 active Shipping or Pickup task ``` #### 2. Add Your Target Sessions 1. Open **Identities**. 2. Open **Sessions**. 3. Select **Add Session**. 4. Choose **Target**. 5. Enter the account email and password. 6. Select [**Request Login**](#request-login-and-imap). 7. Save the session. **Request Login is the recommended login method.** [Token Login](#token-login-backup-method) is a backup method and should only be used when Request Login is unavailable or Stellar staff recommends it. #### 3. Generate Login Cookies Use the regular [Shape module](https://guides.stellaraio.com/stellar/retailers/shape) to generate the cookies Stellar needs to sign into the Target accounts. Recommended starting setup: * **Mode:** Gen * **Site:** Target * **Endpoint:** Login * **Shape Interval:** `10000–15000` * **Proxy:** High-quality ISP or residential proxies * **Browser:** Use Edge, Brave, Firefox, or Safari when available. Add Aloha if additional variety is needed. Avoid Chrome unless it has proven successful for your setup. Generate approximately **1–2 successful Login cookies per Target account**. #### 4. Sign In Your Target Sessions 1. Create Target tasks using **Login mode**. 2. Select the matching profile and Target session. 3. Select an IMAP session if you want Stellar to retrieve emailed login codes automatically. 4. Start the Login tasks. 5. Wait until every Target session is successfully signed in. 6. Stop the Target Login tasks. 7. Stop the regular Shape tasks using the Login endpoint. You do not need to continue generating Login cookies after the sessions are signed in. #### 5. Prepare Your Target Products 1. Open **Tags**. 2. Create a clearly named Target Tag Group. 3. Select **Manage SKUs**. 4. Add the products you want to monitor. 5. Save the Tag Group. Use this product format: ``` TCIN;Product Name;Max Price ``` Example: ``` 12345678;Product Name;500 ``` Target supports up to **29 products per task** through selected Tag Groups. #### 6. Start ATC-Cookie Generation Target checkout tasks require continuously generated add-to-cart cookies. Run both: * Stellar AIO Target [Browser Extension V3](#stellar-target-browser-extension) * [ShapeV2](https://guides.stellaraio.com/stellar/retailers/shapev2) Recommended ShapeV2 starting setup: * **Site:** Target * **Modes:** Mix Gen and Gen Experimental * **Cookie Expiration:** `300000` * **Cookies Per Task:** `3` * **Proxy:** High-quality ISP or residential proxies * **Browser:** Mix supported browsers ``` Gen using Edge Gen using Firefox Gen Experimental using Brave Gen Experimental using Safari ``` If Safari is unavailable, redistribute that generator to Edge, Brave, or Firefox. Add Aloha only when additional browser variety is needed. **Browser recommendation:** Use a mixture of: * Edge * Brave * Firefox * Safari, when available Add Aloha if additional browser variety is needed. Chrome has produced the lowest pass rate in current Stellar testing and is not recommended for Shape or ShapeV2. Only test Chrome if it has already produced reliable cookies for your specific setup. Chromium and Opera may remain available in the browser menu, but they are not part of the current recommended starting setup. Keep the Target Browser Extension and ShapeV2 running while Shipping or Pickup tasks are active. #### 7. Create the Monitor Tasks Recommended setup: * **Mode:** Monitor * **Monitor Proxy:** High-quality ISP proxies * **Input List:** Your Target Tag Group * **Monitoring Delay:** `8000–15000` * **Task Count:** One to Two Monitors per Tag Group A Monitor detects online stock and sends the product information to your Shipping tasks. #### 8. Create the Shipping Tasks Recommended setup: * **Mode:** Shipping * **Profile:** Matching Target profile * **Checkout Proxy:** High-quality residential or ISP proxies * **Input List:** Target Tag Group * **Delay:** `3000` or lower * **Product Quantity:** Follow the product limit announced by your cook group * **Session:** Matching signed-in Target session * **IMAP Session:** Recommended when using Request Login * **Watch Task:** On * **Task Count:** One Shipping task per Target account #### 9. Start the Drop Setup in This Order ``` 1. Regular Shape for Login cookies 2. Target Login tasks 3. Stop Login tasks and regular Shape after sessions sign in 4. Target Browser Extension 5. ShapeV2 Gen and Gen Experimental 6. Target Monitor 7. Target Shipping tasks ``` Before leaving the setup running, confirm: * Every Target session is signed in. * ShapeV2 is generating ATC cookies. * The Target Browser Extension is connected and generating cookies. * The Monitor is actively monitoring. * Shipping tasks are waiting for the Monitor. * Watch Task is enabled. * No account is assigned to more than one active checkout task. *** ## Preliminary Checklist Before creating Target tasks, confirm that you have completed the following: * [ ] Updated StellarAIO to the latest version * [ ] Created one Target account for every checkout task * [ ] Created a Stellar profile for each account * [ ] Confirmed that each profile email exactly matches its Target account email * [ ] Added each Target account under **Identities → Sessions** * [ ] Selected **Request Login** for the sessions (Token Login is a backup) * [ ] Configured an IMAP session for automatic login codes, or prepared to enter verification codes manually * [ ] Added high-quality ISP and residential proxies. You should have multiple proxy providers and/or proxy pools * [ ] Installed **Stellar AIO Target Browser Extension V3** * [ ] Created [Shape](/stellar/retailers/shape.md) tasks for Login cookies * [ ] Created [Shapev2](/stellar/retailers/shapev2.md) tasks for add-to-cart cookies * [ ] Prepared multiple supported browsers for cookie generation * [ ] Created a Target Tag Group containing your SKUs * [ ] Created one or two Monitor task for the Tag Group * [ ] Created one Shipping or Pickup task per Target account * [ ] Enabled **Watch Task** * [ ] Tested the complete setup on an in-stock item * [ ] Enabled cook group notifications for SKUs, restocks, and drop updates *** ## Accounts and Sessions ### Target Account Requirements Use one unique Target account for every checkout task. Recommended account preparation: * Confirm the account email * Avoid signing out after the account is prepared * Test the account manually before an important drop Do not run both a Shipping and Pickup task simultaneously on the same account. The rule is: ``` 1 Target account = 1 active checkout task ``` #### Adding Target Sessions Target is account-based. Add every Target account under **Identities → Sessions** before creating checkout tasks. 1. Open **Identities**. 2. Open **Sessions**. 3. Select **Add Session**. 4. Choose **Target**. 5. Enter the Target account email and password.
6. Select **Request Login**. 7. Save the session. 8. Confirm that the session email exactly matches the email on its assigned Stellar profile. The recommended method is: ``` Request Login ``` Token Login is a backup method and should not be used as the default setup. #### How Request Login Works Request Login tells Stellar to sign in using the email and password saved in the Target session. Request Login does not generate the cookies required to sign in. Before starting the login process, generate Login cookies using the regular [Shape](/stellar/retailers/shape.md) module. The complete Request Login process is: 1. Create the Target session with Request Login selected. 2. Create regular [Shape](/stellar/retailers/shape.md) tasks using the Target `Login` endpoint. 3. Start the Shape tasks and generate approximately one or two Login cookies per Target account. 4. Create Target tasks using Login mode. 5. Select the matching Target profile and session. 6. Select an IMAP session if you want Stellar to retrieve emailed verification codes automatically. 7. Start the Target Login tasks. (Shipping mode tasks) 8. Wait for every Target session to sign in successfully. 9. Stop the Target Login tasks. 10. Stop the regular Shape tasks using the Login endpoint. Once a Target session is successfully signed in, you do not need to continue generating Login cookies for that account. Do not confuse Login cookies with ATC cookies. Login cookies are used to sign the account in. ATC cookies are generated separately by [ShapeV2](/stellar/retailers/shapev2.md) and the Target Browser Extension while checkout tasks are running. #### Request Login and IMAP Target may email a one-time verification code while Stellar is signing an account in. Selecting an IMAP session allows Stellar to retrieve that code automatically. IMAP is supported in: * Shipping tasks * Pickup tasks * Login mode * Reset mode The recommended setup is to select an IMAP session when using Request Login. Without IMAP, you may need to retrieve and enter the emailed verification code manually. See the IMAP Overview Guide for instructions on creating an IMAP session and forwarding account emails to a master Gmail IMAP session. #### Recommended Initial Login Setup Before an important Target drop: 1. Add every Target account under Identities → Sessions. 2. Select Request Login for every session. 3. Confirm that each session email matches its Stellar profile email. 4. Prepare an IMAP session. 5. Create regular [Shape](/stellar/retailers/shape.md) tasks with: * Site: `Target` * Endpoint: `Login` * Shape Interval: `10000-15000` * High-quality proxies * A mixture of supported browsers 6. Generate approximately one or two Login cookies per account. 7. Run Target Login tasks. (Shipping mode tasks) 8. Confirm that every session successfully signs in. 9. Stop the Login tasks. 10. Stop the regular Shape Login tasks. After completing this process, prepare ShapeV2 and the Target Browser Extension for ATC-cookie generation. #### Token Login — Backup Method Token Login is an alternate login method. It should only be used when Request Login is not working or Stellar staff recommends it. If you are instructed to use Token Login: 1. Open a separate browser profile or private window for the Target account. 2. Sign in to the Target account. 3. Keep **Keep Me Signed In** enabled. 4. Use the Target Browser Extension’s **Target Login Token** function.
5. Copy the generated token. 6. Open the corresponding Target session in Stellar. 7. Change the Login Method to Token Login. 8. Paste the token into the Access Token field. 9. Save the session. Do not sign out of the browser session used to generate the token. Signing out may invalidate it. Keep every Target account separated using different browser profiles or private windows. Use different login proxies when managing multiple accounts. Token Login does not replace ATC-cookie generation. ShapeV2 and the Target Browser Extension must still generate ATC cookies while Shipping or Pickup tasks are running. *** ## Understanding Shape, ShapeV2, and the Browser Extension Target requires two different types of cookies: * **Login cookies** are used to sign Target sessions in. * **ATC cookies** are used when Shipping or Pickup tasks attempt to add a product to cart and checkout. Different tools generate these cookies. #### Regular [Shape](/stellar/retailers/shape.md) Module The regular Shape module generates Target Login cookies. Use the following starting setup: * **Mode:** `Gen` * **Site:** `Target` * **Endpoint:** `Login` * **Shape Interval:** `10000-15000` * **Proxy:** High-quality ISP or residential proxy * **Browser:** Edge, Brave, Firefox, or Safari when available. Add Aloha if more browser variety is needed. Avoid Chrome unless it has proven successful for your setup. * **Invisible:** Optional Generate approximately one or two successful Login cookies per Target account. Use these cookies while running Target Login tasks with sessions configured for Request Login. Once every Target session is successfully signed in: 1. Stop the Target Login tasks. 2. Stop the regular Shape tasks using the Login endpoint. Do not keep the regular Shape Login tasks running throughout the drop. See the regular Shape guide for its complete field breakdown and troubleshooting instructions. #### [ShapeV2](#shapev2-module) Module ShapeV2 continuously generates Target ATC cookies. ATC cookies expire quickly and are required while Shipping or Pickup tasks are attempting to add products to cart and checkout. Use the following starting setup: * **Site:** `Target` * **Modes:** A mixture of `Gen` and `Gen Experimental` * **Cookie Expiration:** `300000` * **Cookies Per Task:** `3` * **Proxy:** High-quality ISP or residential proxy * **Browser:** Use a mixture of supported browsers * **Invisible:** Optional when available `300000` milliseconds equals five minutes. Start ShapeV2 before starting Target checkout tasks. Keep it running while Shipping or Pickup tasks are active. Begin with fewer ShapeV2 tasks and increase them only if checkout tasks are consistently running out of ATC cookies. See the ShapeV2 guide for its complete field breakdown and troubleshooting instructions. ### Stellar Target Browser Extension The Stellar AIO Target Browser Extension V3 generates additional Target ATC cookies. **Important:** Chrome is still used to install and run the Stellar Target Browser Extension. The recommendation to avoid Chrome applies to the browser selected inside regular Shape and ShapeV2 tasks, not the Target Browser Extension itself. The Browser Extension should run alongside ShapeV2. It does not replace [ShapeV2](/stellar/retailers/shapev2.md). 1. Download [Stellar AIO Target Browser Extension V3](https://drive.google.com/drive/folders/136nPcGwzFRLuLvtgaQyK1kVKf02QcQe9?usp=drive_link)
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
{% hint style="info" %} You can ingore the red "Errors" message shown in the image above {% endhint %} After installing the extension: 1. Open Target.com in a supported browser. 2. Navigate to an in-stock product. 3. Open the Stellar extension.
4. Add high-quality proxies. Some members don't use proxies but this is extremely risky 5. Enable the extension using the toggle. 6. Enable the generator using the toggle. 7. Keep the browser open and visible. 8. Keep the extension running while your Target tasks are active. Recommended extension settings: | Setting | Recommended starting point | | ---------------- | --------------------------------------- | | Cookies Per Task | `3` | | Cookie Expiry | `5` minutes | | Proxies | High-quality ISP or residential proxies | | Enable Extension | On | | Enable Generator | On | ### Use Different Browsers ShapeV2 supports the following browsers: * Chrome * Chromium * Edge * Opera * Brave * Aloha * Firefox * Safari These browser options are available in both ShapeV2 modes: * Gen * Gen Experimental Do not run every ShapeV2 task with the same browser. Spread your generators across multiple supported browsers to create more variety and compare pass rates. For example, a Target setup could include: * Gen using Chrome * Gen using Edge * Gen using Firefox * Gen Experimental using Brave * Gen Experimental using Safari This is only an example. You do not need to run every supported browser. Browser performance can vary based on your operating system, device, proxy provider, and current Target protection. Test different combinations and keep the browsers that perform best for your setup. Stellar may also allow compatible custom Chromium-based browsers to be configured under Settings. ### Avoid Excessive Cookie Generators More generators do not automatically improve performance. Excessive generators may: * Increase CPU and memory usage. * Slow down your computer. * Burn proxies. * Increase browser failures. * Increase the risk of device-level Shape bans. * Reduce the overall cookie pass rate. Begin with fewer generators and increase them only when ATC cookies are being consumed faster than they are produced. ### Proxy Extension Conflict Do not leave another proxy-switching extension enabled in the same browser as the Stellar Target extension. The Stellar extension handles its own proxy rotation. Running another proxy switcher at the same time can cause: * Infinite proxy-switching loops * Cookies failing to generate * Tasks remaining on Waiting for Shape Cookie * The browser proxy becoming stuck Disable BP Proxy Switcher and similar extensions while the Stellar Target extension is running. *** ## **Notes from Devs** We highly recommend testing how many Shape Tasks you actually need for your checkout tasks. There isn't a fixed ratio, so start with fewer and only scale up if you're running out of cookies. Running 20 Shape Tasks for just 2 checkout tasks doesn't help - you're much more likely to flag your device or proxies. For example, if you're running 10 checkout tasks, start with 3 experimental Shape Tasks and increase them during the drop only if needed. Current Stellar testing shows that Chrome has the lowest Shape pass rate. For regular Shape and ShapeV2, start with Edge, Brave, Firefox, and Safari when available. Add Aloha if more browser variety is needed. Chrome is not required and should only be used when it has already produced reliable results for your setup. 1. If you're getting excessive Shape bans, give your device a break before trying again. Ideally, don't generate any Shape Tasks over the weekend and start fresh for the next drop. 2. We recommend using a mix of US ISP and Residential proxies instead of only ISPs. Since Target usually drops around similar times, you can prepare your Shape Tasks beforehand and test what works best with your setup. 3. There isn't one setup that works for everyone. Every device, proxy provider, network, and setup behaves differently. Keep testing, monitor your tasks during drops, and make adjustments until you find what works best. We can give general recommendations, but you'll get the best results by experimenting with your own setup. 4. If you have access to a macOS device, it's definitely worth testing on Target. In our testing, macOS has consistently performed better for Shape than Windows. 5. Getting rate limited or seeing tasks "stuck" on submitting checkout is completely normal during Target drops. That's just Target handling the traffic. There isn't any magic fix - just let your tasks run and the bot will handle the rest. 6. Start with a smaller setup and scale up as needed. Don't overdo it from the start. Target has become much more competitive, but that doesn't mean running 80 accounts and 25 ISP proxies will give you better results. In most cases, it just makes things worse. 7. Target is well known for releasing stock in waves, so don't stop your tasks after the first wave. If you're new to Target botting, we highly recommend testing your setup on "worse" releases first to learn how everything works. Keep in mind that only drop items are Shape-protected - off-drop products are often not." *** ## Creating Target Tag Groups Target tasks use Tag Groups instead of entering one product directly into each task. ### Creating a Tag Group 1. Open the **Tags** tab in Stellar. 2. Create a new Tag Group.
3. Give the group a recognizable name. Example: ``` Target Pokémon ``` 4. Select **Manage SKUs**. 5. Add the Target products you want to monitor. 6. Save the Tag Group. 7. Select the Tag Group through the task’s **Input List** field. ### Product Format Use the following format: ``` TCIN;Product Name;Max Price ``` Example: ``` 12345678;Product Name;500 ``` The product name and maximum price make the list easier to identify and protect you from checking out above your intended price. ### Tag Group Limits A Target task can monitor up to 29 **products** through its selected Tag Groups. Avoid filling Tag Groups with unrelated products that do not actively restock. Changes made to a Tag Group do not immediately update running checkout tasks. Restart the affected tasks after editing the Tag Group. Target checkout tasks purchase only one monitored product per checkout. Selecting multiple products does not create a multicart order. *** ## Supported Modes ### Shipping The primary Target checkout mode for shipped orders. Shipping tasks log into the selected account and wait for a Monitor task to detect stock.
### Pickup Checkout mode for Target in-store pickup. Pickup requires a ZIP Code and should be paired with a Monitor Pickup task using the same ZIP Code.
### Monitor Monitors products for online shipping availability and pings Shipping tasks. Monitor tasks do not place orders.
### Monitor Pickup Monitors store inventory around a ZIP Code and pings Pickup tasks.
### Login Logs Target accounts into Stellar and can optionally add the profile address or payment method to the account.
### Reset Resets the password for a Target account. An IMAP session is required in the current Reset-mode interface.
### Account Gen Creates new Target accounts using Stellar profiles. Account generation is heavily protected by Shape. Do not create excessive Account Gen tasks or repeatedly spam failed requests.
### Cancel Last Order Attempts to cancel the most recent Target order associated with the selected session and matching TCIN. Only use this mode when you intentionally want to cancel an order.
*** ## Common Fields These fields appear in several Target modes. ### Name Optional task name used for organization. ### Profile The Stellar profile containing the billing, shipping, email, and payment information used by the task. The profile email must exactly match the Target account and Stellar session email. ### Checkout Proxy The proxy used for login and checkout actions. Use high-quality residential or ISP proxies. Test multiple pools and providers because Target performance can vary by setup. ### Monitor Proxy The proxy used to monitor inventory. ISP proxies are recommended for Monitor and Monitor Pickup tasks. ### Input List Select the Target Tag Group containing the products you want the task to monitor or purchase. ### Delay Controls the time between applicable task requests. Lower delays respond faster but may increase Shape blocks or rate limits. Higher delays reduce request frequency but may react more slowly. ### Product Qty The quantity of the product the task attempts to purchase. Check product-specific limits with your cook group. Stellar does not automatically reduce an invalid quantity. ### Session Select the Target session matching the account and profile assigned to the task. ### IMAP Session [IMAP](#imap-session) Allows Stellar to retrieve emailed Target login codes automatically. ### Start Time and End Time Optional scheduling controls. The task must still be started for a scheduled time to take effect. ### Task Qty The Qty field at the bottom determines how many copies of the configured task Stellar creates. This is separate from Product Qty. *** ## Shipping Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Shipping** for shipped Target orders. ### Profile Select the profile matching the Target account and session. ### Checkout Proxy Select a high-quality residential or ISP proxy group. ### Input List Select one or more Target Tag Groups containing the products you want to purchase. Do not exceed the current product limit of 29 products per task. ### Delay Recommended starting point: ``` 3000 or lower ``` Adjust based on current Target traffic, proxy performance, and Stellar announcements. ### Product Qty Enter the quantity the task should attempt to purchase. ### Session Select the Target account assigned to this checkout task. Strictly use one active checkout task per Target account. ### IMAP Session (Login) Select your IMAP session when using Request Login so Stellar can retrieve login codes. ### Extra Item TCIN Optional TCIN for an additional item used by the checkout flow. Leave this blank unless you intentionally want to add an extra item. ### Auto Cancel Extra TCIN When enabled, Stellar attempts to cancel the additional item after the order is placed. Only enable this when using Extra Item TCIN and you intentionally want the extra item canceled. ### Watch Task Recommended: **On** The Shipping task waits for a Monitor task to detect stock and ping it. ### Endless Mode When enabled, the task can restart after a successful checkout. ### Endless Limit Sets the maximum number of successful checkouts allowed when Endless Mode is enabled. ### Use Rakuten Uses the Rakuten integration configured in Stellar. See the [Rakuten Cashback Guide](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-do-i-set-up-rakuten-cashback). ### Use TopCashback Uses the TopCashback integration configured in Stellar. See the [TopCashback Guide](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-do-i-set-up-topcashback). *** ## Pickup Mode Field Breakdown ### Name, Profile, Checkout Proxy and Input List Configure these fields the same way as Shipping mode. ### ZIP Code Enter the ZIP Code around which the task should attempt pickup. The ZIP Code must match the paired Monitor Pickup task. ### Radius Controls how far from the entered ZIP Code Stellar should search for pickup locations. ### Session and IMAP Session Select the session matching the profile and an IMAP session when using Request Login. ### Extra Item TCIN Optional additional item TCIN. ### Watch Task Recommended: **On** The Pickup task waits for a Monitor Pickup task to detect local inventory. ### Override Payment Enable this if you want Stellar to use the payment method stored in the selected profile instead of the payment method already saved on the Target account. Leave this disabled when using the Target account’s saved payment method. ### Endless Mode and Endless Limit Control whether the Pickup task continues after checkout and how many successful checkouts are allowed. ### Rakuten and TopCashback Optional cashback integrations configured through Stellar’s Settings. *** ## Monitor Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Monitor** to watch products for shipping availability. ### Monitor Proxy Select an ISP proxy group. ### Input List Select the Target Tag Group containing the products you want monitored. ### Monitoring Delay Recommended range: ``` 8000–15000 ``` Adjust based on proxy quality, current traffic, and drop-specific recommendations. ### Monitor High Stock (10+) Only When enabled, the Monitor only triggers when at least 10 units are detected. This may reduce low-stock or short-lived pings, but it may also cause the task to ignore smaller restocks. ### Reset Delay Optional delay before the Monitor resets and begins watching for another trigger. ### Start Time and End Time Optional scheduling controls. ### Task Qty One Monitor task per Tag Group is sufficient for most setups. *** ## Monitor Pickup Field Breakdown ### Name Optional organizational name. ### Mode Select **Monitor Pickup** to watch local Target store inventory. ### Monitor Proxy Select an ISP proxy group. ### Input List Select the same Tag Group used by the paired Pickup tasks. ### ZIP Code Enter the pickup-area ZIP Code. This must match the ZIP Code in the Pickup checkout tasks. ### Radius Controls how far from the ZIP Code Stellar checks stores. ### Monitoring Delay Recommended range: ``` 8000–15000 ``` ### Reset Delay Optional delay before the task resumes monitoring after a trigger. ### Start Time and End Time Optional scheduling controls. *** ## Login Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Login** to prepare Target sessions. ### Profile Select the profile matching the Target account. ### Checkout Proxy Select a clean residential or ISP proxy. ### Delay Controls login request timing. Follow current Stellar guidance when scaling. ### Session Select the Target session that should be logged in. ### IMAP Session Select an IMAP session to retrieve Target login codes automatically. ### Add Address Enable this if you want Stellar to add the profile address to the Target account. ### Add Payment Enable this if you want Stellar to add the profile payment method to the Target account. ### Start Time, End Time and Task Qty Optional scheduling fields and the number of Login tasks to create. *** ## Reset Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Reset** to reset a Target account password. ### Profile Select the profile matching the Target account. ### Checkout Proxy Select a clean residential or ISP proxy. ### Password Enter the new password you want to use. If supported by the current flow, leaving this blank allows Stellar to generate a secure password. ### Session Select the Target session whose password should be reset. ### IMAP Session Required in the current Reset-mode interface. The [IMAP](#imap-session) session retrieves the password-reset email or code. ### Delay Recommended maximum starting point: ``` 10000 ``` ### Start Time, End Time and Task Qty Optional scheduling fields and the number of Reset tasks to create. *** ## Account Gen Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Account Gen** to create Target accounts. ### Profile Select profiles containing unique email and personal information. ### Checkout Proxy Use clean, high-quality proxies. Avoid generating many accounts through one small proxy pool. ### Password Enter the password that should be assigned to the new accounts. ### Delay Controls the time between account-generation requests. Use conservative delays and follow current Stellar announcements. ### Add Address Adds the selected profile’s address to the new Target account. ### Add Payment Adds the selected profile’s payment method to the new Target account. ### Start Time, End Time and Task Qty Optional scheduling controls and the number of Account Gen tasks to create. Target Account Gen is heavily protected by Shape. Start with a small number of tasks and do not repeatedly spam failed requests. *** ## Cancel Last Order Mode Field Breakdown ### Name Optional organizational name. ### Mode Select **Cancel Last Order** only when you intentionally want to cancel a recent Target order. ### Profile Select the profile associated with the order. ### Checkout Proxy Required. Select a clean proxy for the cancellation request. ### TCIN Enter the TCIN from the item or order you want Stellar to identify. ### Delay Controls the timing of the cancellation request. ### Session Select the Target session associated with the order. ### Start Time and End Time Optional scheduling controls. Cancellation may be difficult or impossible to reverse. Confirm the profile, session, TCIN, and order before starting this task. *** ## Latest Drop Notes ### Current Target Guidance - Reviewed July 31, 2026 * Run Target locally when possible. * Test macOS if it is available; it has performed better for Shape. * Use Request Login and IMAP for the recommended session flow. * Generate only 1–2 Login cookies per account. * Stop Login-cookie tasks after accounts are signed in. * Keep the browser extension and Shapev2 running while checkout tasks are active. * Use both Shapev2 Gen and Gen Experimental. * Generate Shape and ShapeV2 cookies through a mixture of Edge, Brave, Firefox, and Safari when available. Add Aloha if more browser variety is needed. Avoid Chrome unless it has proven successful for your setup. * Begin with fewer cookie generators and scale only when needed. * Use a mixture of high-quality ISP and residential proxies. * Do not assume that more accounts, proxies, or Shape tasks will improve results. * Target may release inventory in multiple waves. * In Queue, Rate Limit, and temporary Submitting Checkout statuses can be normal during major drops. * Test on less competitive products before relying on the setup for a major release. *** ## Latest Prep Call Recording Replace the placeholder below with the most recent Target prep call: {% embed url="" %} Prep-call instructions may apply to a specific release. Follow the newest written guide, interface, and Stellar announcement when information conflicts. *** ## Common Errors and Fixes ### Waiting for Shape Cookie This status can refer to either a missing Login cookie or a missing ATC cookie. The correct fix depends on what the task is currently attempting to do. **If the Account Is Trying to Log In** The task needs a Login cookie from the regular Shape module. Confirm that the regular Shape task is using: * **Mode:** `Gen` * **Site:** `Target` * **Endpoint:** `Login` * **Shape Interval:** `10000-15000` Confirm that: * The regular Shape task is running. * Login cookies are being generated. * The Target session uses Request Login. * The correct profile and session are selected. * The selected proxies are working. Generate approximately one or two Login cookies per account, then restart the affected Target Login task. After the session is successfully signed in, stop the regular Shape Login tasks. **If the Account Is Already Logged In and the Task Is Adding to Cart** The task needs an ATC cookie. Confirm that: * ShapeV2 is running. * ShapeV2 has Site set to `Target`. * A mixture of Gen and Gen Experimental is being used. * Cookie Expiration is set to `300000`. * Cookies Per Task is set to `3`. * The Target Browser Extension is connected. * The extension and cookie generator are enabled. * The Available Cookies count is increasing. * High-quality proxies are being used. If ATC cookies are not generating: 1. Test a different proxy group. 2. Test Edge, Brave, Firefox, or Safari when available. Add Aloha if additional browser variety is needed. Stop using Chrome if it produces repeated failures, bans, or a poor pass rate. 3. Restart only the failed generators. 4. Reduce excessive generators. 5. Increase generators gradually only if cookies are being consumed too quickly. ### Waiting for a Login Verification Code Target may email a one-time verification code while a session is signing in. Confirm that: * The correct IMAP session is selected. * The IMAP connection is working. * The Target verification email was received. * Email forwarding is configured correctly, if applicable. * The email on the Target session matches the intended account. Without IMAP, retrieve and enter the verification code manually when prompted. ### Extension Proxy Keeps Switching **Cause:** Another proxy-switching extension is enabled alongside the Stellar Target extension. **Fix:** * Disable BP Proxy Switcher and other proxy extensions. * Leave only the Stellar Target extension controlling proxies. * Restart the Target browser after disabling the conflicting extension. ### Shape Ban **Cause:** Target is rejecting the generated cookies, proxy, browser, profile information, or device. **Fix:** * Try another clean proxy pool. * Try a different supported browser. * Increase cookie-generation intervals. * Reduce the number of Shape tasks. * Test another profile if the address may be flagged. * Avoid repeatedly restarting the same failing setup. ### Full Shape Block or Device Warning A full Shape block is different from one failed cookie or cart attempt. Repeated full blocks may indicate device-level detection. Recommended action: 1. Stop Target tasks. 2. Stop cookie generation. 3. Allow the device and proxies to rest for 24–48 hours. 4. Restart with fewer tasks and different proxies. 5. Test on a less competitive product. Continuing to generate cookies aggressively while fully blocked can make the problem worse. ### Target Session Will Not Log In **Possible causes:** * Profile email does not match the session email. * Login cookies are missing. * IMAP cannot retrieve the login code. * The password is incorrect. * The account was locked. * The proxy is blocked. **Fix:** * Confirm all emails match exactly. * Generate new Login cookies. * Test the IMAP session. * Confirm the account credentials manually. * Try another clean proxy. * Use Login mode to prepare the session. ### Monitor Does Not Ping Checkout Tasks **Possible causes:** * The Monitor is not running. * Monitor and checkout tasks use different Tag Groups. * The Tag Group was edited after the tasks started. * Watch Task is disabled. * The product is not available. **Fix:** * Confirm the Monitor is running. * Confirm both tasks use the correct Tag Group. * Restart tasks after editing the Tag Group. * Enable Watch Task. * Confirm the TCIN and maximum price are correct. ### Pickup Task Does Not Trigger **Possible causes:** * Pickup and Monitor Pickup use different ZIP Codes. * The radius is too small. * The product is unavailable at nearby stores. * Watch Task is disabled. **Fix:** * Use the same ZIP Code in both tasks. * Adjust the radius. * Confirm local inventory. * Enable Watch Task. ### In Queue or Rate Limit This can be normal during heavy Target releases. Allow the tasks to continue running. Avoid restarting every task simultaneously unless Stellar staff announces a required restart. ### Stuck on Submitting Checkout Target may throttle checkout requests during high traffic. Allow the task to continue. Confirm that the session, cookies, proxy, profile, and payment information are valid. ### Account Lock or Session Instability **Likely cause:** More than one active checkout task is using the same Target account. **Fix:** * Stop duplicate checkout tasks. * Assign one account to one Shipping or Pickup task. * Prepare another account and matching profile before scaling. ### Checkout Uses the Wrong Payment Method **Cause:** Override Payment is configured incorrectly. **Fix:** * Disable Override Payment to use the card saved on the Target account. * Enable Override Payment to use the payment stored in the Stellar profile. * Confirm the selected profile matches the Target account. ### Tag Group Changes Are Not Appearing Running checkout tasks do not automatically reload edited Tag Groups. Restart the affected tasks after changing the product list. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.stellaraio.com/stellar/retailers/targetgo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.