> 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/shape.md).
# Shape
The regular Shape module generates cookies required by certain retailers for login, monitoring, or checkout.
The type of cookie generated depends on the selected **Site** and **Endpoint**.
## Gen Mode
## Important Target Information
For Target, the regular Shape module is currently recommended for generating **Login cookies only**.
The recommended Target workflow is:
1. Use the regular Shape module with the `Login` endpoint to generate Login cookies.
2. Use those cookies to sign in Target sessions configured with **Request Login**.
3. Stop the regular Shape tasks after all Target sessions are successfully signed in.
4. Use **ShapeV2 and the Target Browser Extension** to generate ATC cookies while Target checkout tasks are running.
Each tool has a different purpose:
* **Regular Shape:** Generates Target Login cookies.
* **ShapeV2:** Continuously generates Target ATC cookies.
* **Target Browser Extension:** Continuously generates additional Target ATC cookies.
Do not use the regular Shape module as your primary Target ATC-cookie generator unless current Stellar instructions specifically tell you to.
### Preliminary Checklist
Before creating Shape tasks, confirm that you have:
* [ ] Updated StellarAIO to the latest version.
* [ ] Added high-quality proxies.
* [ ] Prepared multiple proxy providers or proxy pools when possible.
* [ ] Confirmed which retailer and endpoint you need.
* [ ] Reviewed the applicable retailer guide.
* [ ] Prepared multiple supported browsers.
* [ ] Tested a small number of Shape tasks before scaling.
## Supported Mode
### Gen
Gen mode generates Shape cookies for the selected retailer and endpoint.
The cookie’s purpose depends on the selected endpoint. For example, Target’s `Login` endpoint generates the cookies used while signing accounts in.
## Field Breakdown
### Name
This is an optional custom name for the task.
Use a clear name that identifies the retailer and purpose, such as:
```
Target Login Cookies
```
### Mode
Select `Gen` to generate cookies using the regular Shape module.
### Checkout Proxy
Select the proxy group the task should use when generating cookies.
High-quality ISP proxies are generally recommended. Good-quality residential proxies may also work.
For larger setups:
* Use multiple proxy providers or proxy pools.
* Avoid placing every task on the same proxy group.
* Test your proxies before an important release.
* Replace or rotate proxies if you experience repeated bans or failed cookie generation.
There is no single proxy provider or proxy type that works perfectly for every user.
### Site
Select the retailer for which you want to generate cookies.
Available retailers may include:
* Target
* SportChek Canada
* Pokémon Center Japan
Always select the correct retailer. Cookies generated for one retailer cannot be used for another retailer.
### Shape Interval
The Shape Interval controls how often the task attempts to generate a cookie. The value is entered in milliseconds.
For example:
```
10000 = 10 seconds
```
```
20000 = 20 seconds
```
You can also enter a range:
```
10000-15000
```
This selects a random interval between 10 and 15 seconds.
Recommended intervals can differ by retailer and endpoint. Always follow the applicable retailer guide or the latest Stellar announcement.
For Target Login cookies, the recommended starting interval is:
```
10000-15000
```
Lower intervals generate cookies more frequently but may increase proxy, browser, or device bans. Higher intervals are safer but generate cookies more slowly.
### Cookie Expiration
Cookie Expiration controls how long generated cookies remain available before expiring. This value is entered in milliseconds.
For example:
```
300000 = 5 minutes
```
Use the value recommended in the applicable retailer guide. Retailers can require different expiration settings.
### Cookies Per Task
Cookies Per Task controls how many cookies the Shape task attempts to keep available.
More cookies are not always better. Creating excessive cookies can unnecessarily increase CPU usage and the risk of proxy or device bans.
For Target Login, generate only enough successful cookies to provide approximately **one or two Login cookies per account**.
### Endpoint
The Endpoint determines which step the generated cookie supports.
**Login**
The `Login` endpoint generates cookies used during the login process.
For Target, this is the recommended endpoint for the regular Shape module.
**ATC**
The `ATC` endpoint generates cookies used during the add-to-cart or checkout process.
For Target, use **ShapeV2 and the Target Browser Extension** for continuous ATC-cookie generation unless Stellar announces otherwise.
Other retailers may use the endpoints differently. Follow the applicable retailer guide.
### Browser
Select the browser the Shape task should use to generate cookies.
#### Recommended Browsers
Use a mixture of:
* Edge
* Brave
* Firefox
* Safari, when available on your device
If additional browser variety is needed, add:
* Aloha
#### Chrome Guidance
Chrome has produced the lowest Shape pass rate in current Stellar testing and is not recommended as a default browser.
Only test Chrome if it has already produced successful cookies for your specific device, proxies, retailer, and current website protection. If Chrome produces poor pass rates or repeated bans, stop using it and switch to the recommended browsers.
Other browser options may remain available in Stellar, but being supported in the interface does not mean they are currently recommended.
Do not run every Shape task through the same browser. Begin with a small mixture of Edge, Brave, Firefox, and Safari when available. Compare successful cookie generation and keep the combinations that work best for your setup.
Browser performance can change based on:
* The retailer
* Current website protection
* Operating system
* Device
* Proxy provider
* Proxy pool
* Number of simultaneous generators
### Invisible
Invisible mode attempts to generate cookies without displaying a browser window.
This feature is experimental.
Recommended testing process:
1. Keep your existing number of Shape tasks.
2. Enable Invisible mode on only one task.
3. Compare its performance with your visible tasks.
4. Scale only after confirming that it works well on your device.
Do not increase your total number of Shape tasks simply because Invisible mode is enabled. Excessive tasks may increase the risk of device-level Shape bans.
### Start Time
This is an optional time at which an already-started task may begin operating.
Setting a Start Time does not start the task automatically. You must still start the task inside Stellar.
### End Time
This is an optional time at which the task should stop operating.
## Target Request Login Walkthrough
This section explains how the regular Shape module works with Target’s recommended Request Login method.
#### Step 1: Create the Target Session
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** as the login method.
7. Save the session.
Request Login tells Stellar to sign in using the saved Target account credentials. It does not generate the required Login cookies by itself.
#### Step 2: Create the Shape Login Tasks
Create regular Shape tasks using the following settings:
* **Mode:** `Gen`
* **Site:** `Target`
* **Endpoint:** `Login`
* **Shape Interval:** `10000-15000`
* **Checkout Proxy:** High-quality proxy
* **Browser:** Edge, Brave, Firefox, or Safari when available. Add Aloha only if more browser variety is needed. Chrome is not recommended unless it has proven successful for your setup.
* **Invisible:** Optional
Generate enough successful cookies to provide approximately **one or two Login cookies per Target account**.
#### Step 3: Run the Target Login Tasks
After Login cookies are available:
1. Create or start Target tasks using **Login mode**.
2. Select the profile matching the Target account.
3. Select the correct Target session.
4. Select an IMAP session if you want Stellar to retrieve emailed verification codes automatically.
5. Select a high-quality checkout proxy.
6. Enter the currently recommended delay.
7. Start the Login task.
8. Wait for the Target session to sign in successfully.
If Target emails a verification code, the selected IMAP session can retrieve it automatically.
Without IMAP, you may need to complete the verification manually.
#### Step 4: Stop the Login Setup
Once all Target sessions are successfully signed in:
1. Stop the Target Login tasks.
2. Stop the regular Shape tasks using the `Login` endpoint.
3. Leave the Target sessions signed in.
You do not need to keep generating Target Login cookies throughout the drop.
Before starting Target Shipping or Pickup tasks, start **ShapeV2 and the Target Browser Extension** to generate fresh ATC cookies.
### How Many Shape Tasks Should I Create?
There is no universal task ratio.
Start with a small number and increase only when necessary. Running excessive Shape tasks can:
* Increase CPU and memory usage.
* Place unnecessary load on your browsers.
* Burn proxies.
* Increase the risk of Shape bans.
* Reduce performance instead of improving it.
For Target Login, focus on obtaining one or two successful Login cookies per account. Stop the tasks after the accounts are signed in.
### Recommended Practices
* Test your setup before an important drop.
* Use high-quality proxies.
* Use multiple proxy providers or proxy pools when possible.
* Start with a mixture of Edge, Brave, Firefox, and Safari when available. Add Aloha if additional variety is needed. Avoid Chrome unless it has already produced a reliable pass rate for your setup.
* Begin with fewer Shape tasks.
* Scale only when your current setup is not producing enough cookies.
* Give your device and proxies a break after excessive Shape bans.
* Follow the retailer guide when its recommendations differ from this general guide.
* Follow the newest Stellar announcement when temporary drop instructions are provided.
## Common Errors and Fixes
#### Cookies Are Not Generating
Possible causes include:
* Poor or blocked proxies
* An unsupported or outdated browser
* The incorrect retailer or endpoint
* A Shape ban affecting the device or proxy
* Too many generators running simultaneously
* An outdated Stellar version
Try the following:
1. Confirm Stellar is updated.
2. Confirm the correct Site and Endpoint are selected.
3. Test another high-quality proxy group.
4. Test Edge, Brave, Firefox, or Safari when available. If more browser variety is needed, test Aloha. Stop using Chrome when it produces repeated failures, bans, or a poor pass rate.
5. Reduce the number of Shape tasks.
6. Give the device and proxies time to rest before testing again.
#### Target Session Is Waiting for a Login Cookie
Confirm that the regular Shape task is using:
* **Site:** `Target`
* **Endpoint:** `Login`
Make sure the Shape task has successfully generated cookies before restarting the Target Login task.
#### Target Session Is Waiting for a Verification Code
This is an email-verification issue rather than a Shape-generation issue.
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.
#### Excessive Shape Bans
Reduce the number of generators and test different:
* Proxy providers
* Proxy pools
* Supported browsers
* Devices
Do not repeatedly restart a large number of Shape tasks after a ban. Allow the affected device and proxies time to rest.
#### High CPU or Memory Usage
Every visible browser task uses computer resources.
Reduce the number of simultaneous Shape tasks, test Invisible mode on a small number of tasks, and close unnecessary programs.
Only create as many Shape tasks as your computer or server can handle reliably.
---
# 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/shape.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.