Sticky Sessions in Proxies: When You Need Them and How to Configure Them Correctly

Sticky sessions are a mode of proxy operation where one IP address is assigned to your session for a certain period: from a few minutes to several hours. This is critically important for many tasks — from scraping marketplaces to working with advertising accounts. Incorrect configuration can lead to account bans, parser failures, and data loss.

In this guide, we will explore what sticky sessions are, how they differ from IP rotation, in which cases sticky sessions are essential, and when they can be avoided. We will provide step-by-step configurations for popular tools: anti-detect browsers, parsers, and APIs.

What are sticky sessions and how do they work

Sticky sessions are a mode of proxy server operation where your requests go through the same IP address for a specified time. This time is called session lifetime and can range from 1 minute to 24 hours depending on the proxy provider.

Imagine a situation: you log into a marketplace website from the IP address 185.123.45.67, add products to your cart, and proceed to the checkout page. If the IP address suddenly changes to 92.45.78.123, the site may perceive this as suspicious activity — the cart will reset, the session will be terminated, and in the worst case, you will receive a ban due to fingerprinting.

Sticky sessions solve this problem. When you connect to a proxy server, it assigns you a specific IP address from the pool and maintains this association. All your subsequent requests within the same session go through this same IP. The session remains active either until the set time expires or until you disconnect.

Sticky sessions vs IP rotation: key differences

Many beginners confuse sticky sessions with IP rotation. These are opposite approaches to working with proxies, each solving its own tasks. Let's break down the key differences.

Practical example: You are working with 20 Facebook Ads accounts through the anti-detect browser Dolphin Anty. For each account, you need a stable IP address throughout the working session (usually 2-4 hours). If the IP changes every 5 minutes, Facebook will consider this suspicious activity — the account will get banned. In this case, you need sticky sessions with a duration of at least 2-4 hours.

On the other hand, if you are scraping competitor prices on Wildberries and making 10,000 requests per hour, IP rotation will be preferable. Each request comes from a new IP address, which reduces the likelihood of blocking due to the number of requests from a single source.

When sticky sessions are absolutely necessary

There are tasks where sticky sessions are not just a recommendation, but a mandatory requirement. Without them, you will face technical problems or get banned. Let's consider the main scenarios.

1. Working with advertising accounts (Facebook Ads, TikTok Ads, Google Ads)

All advertising platforms strictly monitor IP address changes within a single session. If you log into Facebook Ads Manager from one IP, create a campaign, and 10 minutes later your IP changes — the security system will perceive this as a hacked account. The result: forced password change, two-factor authentication, or complete account ban.

Recommended session duration: 4-6 hours for a working session. If you work with an account daily, it is better to use the same IP for several days or even weeks. For this, residential proxies with the ability to fix the IP for a long time are suitable.

2. Multi-accounting on social networks (Instagram, TikTok, VK)

SMM specialists managing 10-50 client accounts use anti-detect browsers like Dolphin Anty, AdsPower, or Multilogin. Each profile in the browser must have a unique fingerprint and stable IP address. If the IP changes during work, the social network may link several accounts together (chain-ban) or block them for suspicious activity.

Recommended session duration: at least 30 minutes for one-time actions (posting, responding to comments), up to 24 hours for active work. Ideally, fix one IP to one account on a permanent basis.

3. E-commerce: working with carts and order processing

If you are testing the purchasing process on marketplaces (Wildberries, Ozon, Yandex.Market), adding products to the cart and proceeding to payment, changing the IP will lead to session reset. The cart will be cleared, and you will have to start over. This is especially critical for automated purchasing scenarios or monitoring product availability.

Recommended session duration: 10-30 minutes — enough to complete the purchasing process.

4. Data scraping with authorization

If you are scraping data from sites that require authorization (personal accounts, closed sections, API with tokens), changing the IP may lead to session termination. The authorization token will become invalid, and you will have to re-authenticate. This slows down the scraper and increases the risk of blocking.

Recommended session duration: depends on the lifetime of the authorization token on the target site. Usually 30 minutes - 2 hours.

5. Testing web applications from different regions

Marketers and QA specialists test how the site appears to users from different cities and countries. For example, checking flight prices for Moscow and St. Petersburg or content availability for users from Kazakhstan. For accurate testing, it is necessary to maintain one IP throughout the check; otherwise, the results will be distorted.

Recommended session duration: 15-60 minutes depending on the volume of testing.

When sticky sessions are not needed or harmful

There are tasks where sticky sessions are not only unnecessary but can even harm work efficiency. Let's consider such cases.

1. Mass scraping without authorization

If you are collecting large volumes of data from public pages (product prices, descriptions, specifications), IP rotation will be more effective. Many sites limit the number of requests from one IP address in a given time (rate limiting). For example, Wildberries may block an IP if it receives more than 100 requests per minute.

With rotation, each request comes from a new IP, allowing you to bypass these limits and scrape data 10-100 times faster. In this case, data center proxies with fast rotation will be the optimal choice.

2. Checking ads and SEO positions

When checking how your ads appear in Google Ads or Yandex.Direct from different regions, you need to quickly switch between IP addresses from different cities. Sticky sessions will only hinder here — you will have to wait for the session to end or manually change the session ID.

3. Data collection from APIs without restrictions

If the service's API has no IP restrictions and only uses authorization tokens, sticky sessions do not provide advantages. You can use rotation or even do without proxies.

How to choose session duration for different tasks

The duration of a sticky session is a critically important parameter. A session that is too short will lead to frequent IP changes and possible bans. A session that is too long will lead to inefficient use of the IP address pool and increased risk if the IP gets blacklisted by the target service.

Practical advice: If you are unsure about the optimal duration, start with 30 minutes and gradually increase it while monitoring the results. For working with advertising accounts and multi-accounting on social networks, it is better to err on the side of caution and choose a longer session.

Setting up sticky sessions in anti-detect browsers

Anti-detect browsers are the main tool for working with multiple accounts. Dolphin Anty, AdsPower, Multilogin, GoLogin — all of them support sticky sessions, but the setup may differ. Let's break it down step by step for the most popular browsers.

Setup in Dolphin Anty

Dolphin Anty is one of the most popular anti-detect browsers among arbitrageurs and SMM specialists. Here’s how to set up sticky sessions:

1. Open a browser profile or create a new one (click the "Create profile" button)
2. Go to the "Proxy" section in the profile settings
3. Select the proxy type: HTTP, SOCKS5 (SOCKS5 is recommended for better compatibility)
4. Enter the proxy details in the format: host:port:username:password
5. In the "IP change" field, select "Do not change" or specify the desired session time
6. Click "Check proxy" — the IP address and geolocation should be displayed
7. Save the profile

Important nuance: Dolphin Anty automatically saves the IP binding to the profile. If you use residential proxies that support sticky sessions, the same IP will be used each time you launch the profile for the session lifetime.

Setup in AdsPower

AdsPower offers more flexible proxy settings with the option for automatic rotation:

1. Create a new profile or open an existing one
2. In the "Proxy settings" section, select the proxy type
3. Enter the connection details (host, port, login, password)
4. In the "IP rotation" setting, select "Fixed IP" or specify the rotation time
5. If your proxy provider supports session ID, add it to the username: username-session-12345
6. Check the connection with the "Check proxy" button

Setup in Multilogin and GoLogin

The setup process in Multilogin and GoLogin is similar to Dolphin Anty. The main difference is in the interface. You need to enter the proxy details and choose the "no rotation" mode or specify the desired session time. Both browsers work correctly with sticky sessions from most providers.

Configuration for scraping and automation

If you are using ready-made scrapers for marketplaces (Wildberries, Ozon, Avito) or automation tools, the setup of sticky sessions depends on the specific service. Let's consider the general principles.

Using session ID in proxy URL

Many proxy providers (including quality services) support passing the session ID through the username. This allows you to control sticky sessions at the application level. The format is usually like this:

username-session-YOUR_SESSION_ID:password@host:port

Where YOUR_SESSION_ID is any unique string you generate (for example, UUID or just a number from 1 to 10,000). As long as you use the same session ID, the proxy server will provide you with the same IP address.

Example: If you are scraping Wildberries and want to keep the IP for 30 minutes, create the session ID once at the beginning of scraping and use it for all requests during those 30 minutes. After 30 minutes, generate a new session ID — you will get a new IP.

Setup in popular scrapers

Most ready-made scrapers for marketplaces have a section for proxy settings. It usually looks like this:

• Field for entering the proxy (format host:port or full URL)
• Login and password for authorization
• Option "Use one IP" or "IP rotation" — choose the first for sticky sessions
• Session lifetime (if supported)

If the scraper does not support sticky sessions directly but allows specifying a proxy with session ID in the username, use this method. The main thing is not to change the session ID during operation.

Sticky sessions for automation via API

If you are using the proxy provider's API for automation, sticky sessions are configured through request parameters. Usually, the provider provides documentation with examples. A typical approach is to pass the session ID in headers or request parameters.

Important: Clarify with your proxy provider how exactly sticky sessions are implemented — via session ID in the username, through API parameters, or in another way. This is critically important for correct operation.

Common mistakes when working with sticky sessions

Even experienced specialists make mistakes when setting up sticky sessions. Here are the most common problems and how to solve them.

Mistake 1: Session duration is too short

Problem: You set the session duration to 5 minutes for working with Facebook Ads. The IP changes during the creation of the advertising campaign, and the account gets banned.

Solution: For advertising platforms and social networks, use a minimum of 30 minutes, ideally — 2-6 hours. It is better to err on the side of caution and choose a longer session.

Mistake 2: Using one session ID for different accounts

Problem: You use one session ID (and thus one IP) to work with 5 Instagram accounts. All accounts get banned simultaneously (chain-ban).

Solution: Each account should have a unique session ID and unique IP. Never mix accounts on one IP, even if they belong to the same client.

Mistake 3: Forgot to check the type of proxy

Problem: You are using data center proxies for working with TikTok Ads. Even with sticky sessions, accounts get banned because TikTok easily identifies data center IPs.

Solution: For advertising platforms and social networks, use only mobile proxies or residential ones. Data center proxies are suitable only for scraping and tasks without strict moderation.

Mistake 4: Did not consider time zone and geolocation

Problem: You are working with a Facebook Ads account for promotion in Moscow, but you are using an IP from Vladivostok (time zone +7 hours). Facebook sees a mismatch between the activity time and geolocation.

Solution: Choose an IP from the same region where the account is registered or where the target audience is located. In the anti-detect browser, set the time zone according to the proxy's geolocation.

Mistake 5: Do not monitor IP quality

Problem: The IP address provided by the proxy provider is already blacklisted by the target service (for example, it was used by another client for spam). You get banned immediately upon connection.

Solution: Before starting work, check the IP against blacklists (services like AbuseIPDB, IPQualityScore). If the IP is "dirty," request a replacement from the provider or change the session ID to obtain a new IP.

Conclusion

Sticky sessions are not just a technical setup, but a critically important element for safe operation with multiple accounts, advertising accounts, and automation. Proper configuration of sticky sessions protects against bans, maintains operational stability, and imitates real user behavior.

The main thing to remember: for each task — its optimal session duration. Working with Facebook Ads requires 4-6 hours of stable IP, scraping with authorization — 30 minutes to 2 hours, while mass scraping without authorization is better done with IP rotation. Use the tables from this article as a guideline and adapt them to your tasks.

Do not forget about proxy quality: sticky sessions work effectively only with clean IP addresses. For advertising platforms and social networks, choose residential or mobile proxies; for scraping, you can use data center proxies.

If you plan to work with multi-accounting on social networks, traffic arbitrage, or SMM automation, we recommend trying residential proxies with support for sticky sessions — they provide a high level of trust from platforms and minimal risk of blocks. For particularly demanding tasks (TikTok Ads, Instagram), the optimal choice will be mobile proxies with the ability to fix the IP for a long time.