A beginner-friendly guide to the Integration tab: what it is, why it exists, and how to build a working proxy connection string without memorizing any syntax.
Every proxy you create has a settings page with three tabs: Overview, Settings, and Integration.This guide is about the Integration tab - the place where you turn your proxy into a ready-to-paste connection string or a working code snippet.If you have never used a proxy before, read this page carefully. You do not need to know what “ASN” or “sticky session” means yet - everything is explained along the way.
Host, port and password never change. The username is the interesting one, because with 2extract the username is not just an identifier - it is also the instruction sheet for the request.Everything you want to control - which country the IP comes from, whether the IP stays the same between requests, how long it stays the same - is written into the username as a chain of parameters:
2xt-customer-a1b2-proxy-my_scraper-country-de-state-bavaria-session-a1b2c3-time-30└─────────── your proxy ─────────┘└── where ──┘└──── what kind of session ────┘
This design is what makes 2extract flexible: one single proxy can send traffic through Germany, then through Japan, then through a fixed New York IP - all at the same time, from the same program, just by changing the username string.The trade-off is that the string has rules. Parameters must be in the right order, city names must be lowercase without spaces, ZIP code cannot be combined with a city, and so on. One typo and you either get an error or - worse - traffic silently routed through the wrong place.
The Integration tab is the tool that writes that string for you. You click a few dropdowns, and it produces a correct username plus a complete, copy-pasteable code snippet for your language. You never have to memorize the syntax.
It is worth spelling out how the settings of the proxy itself differ from what you do on the Integration tab.
Settings tab = saved
What you configure on the Settings tab (default location, traffic limits) is saved to your proxy. It applies to every request you make, forever, until you change it.
Integration tab = not saved
What you configure on the Integration tab is not saved anywhere. It only builds a text string for you to copy. Closing the page throws the selection away.
Think of the Integration tab as a calculator, not a form. A calculator does not “remember” that you typed 2 + 2 - it just hands you the 4. In the same way, the Integration tab hands you a username and forgets about it.Why this is convenient: you can generate as many different configurations as you want from a single proxy. Ten countries, fifty sessions - all valid at the same time, no extra proxies needed, nothing to save or switch between.
There is no “Save” button on the Integration tab, and that is intentional. If you want to change the default behaviour of the proxy itself, use the Settings tab instead.
The tab is made of three cards, stacked top to bottom.
1
Configuration - you make choices here
Protocol, location, session behaviour, plus one-click presets.
2
Verify & Connect - the result appears here
A ready code snippet in cURL, Python, Node.js or Go, updating live as you change anything above.
3
Generate List - bulk output
Produces many connection strings at once, each with its own session (when the session type is Sticky), for tools that expect a proxy list file.
When you first open the tab, the fields are pre-filled with your proxy’s default location (the one from the Settings tab), protocol HTTPS, and session type Rotating. No preset is highlighted. This is deliberate - it shows you the configuration you would get if you did nothing at all.
Let’s do a real example from start to finish.The goal: check prices on a German online store, from a German IP address, using Python.
1
Open the Integration tab
Go to My Proxies, click your proxy, then click the Integration tab.
The Integration tab is the third tab on the proxy settings page.
2
Pick a protocol
Under Protocol you will see three options: HTTP, HTTPS, SOCKS5.If you do not know which one you need, choose HTTPS. It encrypts the connection between your computer and our gateway, so nobody on your network can read your proxy password.
HTTPS - the safe default. Works with almost everything.
HTTP - same thing, but the connection to the gateway is not encrypted. Only pick this if a tool specifically demands it.
SOCKS5 - a different, lower-level protocol. Needed by some desktop apps, game clients and anti-detect browsers.
Choosing HTTPS here does not stop you from visiting http:// websites. This setting is only about the link between your program and our gateway.
3
Choose where the IP should be
Under Targeting Mode, leave the default Location selected. (The other option, ASN, is for advanced users - see below.)Below it are four dropdowns: Country, Region / State, City, ZIP Code.For our example, open Country and select Germany. Leave the rest empty.The rules the interface enforces for you:
You cannot pick a Region, City or ZIP until you have picked a Country.
Picking a Region or City disables ZIP Code, and vice versa. These two ways of narrowing down a location cannot be combined.
Every field you leave empty simply means “anywhere” - an empty City means any city in Germany.
Selecting Germany as the target country. Region, City and ZIP stay empty.
4
Choose how the IP behaves
Under Session Control, the Session Type dropdown has two values:
Rotating - you get a different IP on every request. Best for collecting many pages, because the target site sees a crowd of visitors rather than one persistent user.
Sticky - you keep the same IP for a while. Necessary when your steps depend on each other: log in, add to cart, check out. With a rotating IP, the site would see a different visitor at every step and log you out.
For price checking, keep Rotating. The two fields next to it - Session Time (min) and the Force Constant IP toggle under Strict Mode - stay greyed out, because they only make sense for sticky sessions.
Session Control with Rotating selected - the sticky-only fields are disabled.
5
Copy the result
Scroll down to the Verify & Connect card. It already contains a finished snippet built from your choices.Use the dropdown in the top-right corner of that card to switch language: cURL, Python, Node.js, Go. Pick Python, then click the copy button on the code block.You now have working code:
import requests# Connection stringproxy = "https://2xt-customer-a1b2-proxy-my_scraper-country-de:a_very_secure_password@proxy.2extract.net:5555"# Configure both protocols to use the proxyproxies = { "http": proxy, "https": proxy}response = requests.get("https://api.ipify.org", proxies=proxies)print(response.text)
Notice the -country-de that appeared in the username. That is the whole point of the tab: you clicked “Germany” in a dropdown, and it wrote the parameter for you.
The Verify & Connect card. The snippet rebuilds itself every time you change a setting above.
6
Run it
Paste the snippet into your project and run it. It requests https://api.ipify.org, a free service that simply reports the IP address it sees.If the printed IP is a German one, everything works. This is the fastest way to confirm your setup before pointing the code at a real target.
In the top-right corner of the Configuration card there are four buttons: E-Commerce, Web Scraping, SMM & Accounts, Local SEO.Each one fills in every field at once with a combination that suits that kind of work. They exist to show you what a sensible configuration looks like - if you are unsure what to pick, click the closest one and adjust from there.
E-Commerce
Web Scraping
SMM & Accounts
Local SEO
Protocol
HTTPS
HTTP
SOCKS5
HTTPS
Targeting Mode
Location
Location
Location
Location
Country
US
-
US
US
Region
California
-
Florida
-
City
-
-
Miami
-
ZIP
-
-
-
11368
Session Type
Rotating
Rotating
Sticky
Sticky
Session Time
-
-
30 min
15 min
Force Constant IP
off
off
on
on
Clicking a preset overwrites everything you had selected, including your country. As soon as you edit any field afterwards, the preset stops being highlighted - because the configuration is no longer that preset.
Quick Presets. The active preset is highlighted; editing any field clears the highlight.
Switch Session Type to Sticky and three things happen.1. A session ID is generated. A short random code such as a1b2c3 is added to your username as -session-a1b2c3. That code is the session: every request you send with the same code goes through the same IP. Send a different code and you get a different IP. Your program can generate as many codes as it likes - one per user account, one per browser profile, one per task.2. Session Time becomes editable. This is how long, in minutes, the IP should stay yours. It appears in the username as -time-30.3. Force Constant IP becomes available. This is a strict mode toggle, and it deserves an explanation.Our IPs come from real residential and mobile devices, and a real device can go offline at any moment - someone closes a laptop, someone leaves a Wi-Fi zone. If that happens to your session:
Force Constant IP off (default) - we quietly give you a replacement IP so your program keeps running.
Force Constant IP on - we do not substitute. Your request fails with an error instead.
Turn it on only when a changing IP would be worse than a failure - for example when managing a sensitive account where a sudden IP change would trigger a security alert. For ordinary data collection, leave it off.
The second Targeting Mode option replaces the location dropdowns with a network selector. Use it when you care about which provider the IP belongs to rather than where it is.
Residential proxies - ASN. Enter an Autonomous System Number, the ID of an internet provider’s network (for example 7922 for Comcast). You get an IP inside that provider’s network.
Mobile proxies - ISP. Choose a mobile operator such as T-Mobile or Vodafone from the list. You get an IP on that carrier’s mobile network.
Network targeting and location targeting cannot be combined. Choosing ASN or ISP removes the country, region, city and ZIP parameters from the username entirely. This is why switching Targeting Mode hides the location fields instead of merely disabling them.
If you have no specific reason to target a provider, stay on Location.
Some tools - anti-detect browsers, multi-account managers, scraping frameworks - do not want a single proxy. They want a file with dozens of lines, one proxy per line.The Generate List card at the bottom of the tab does that:
Set Quantity - how many lines you need.
Set Format - the layout the receiving tool expects: host:port:user:pass, user:pass@host:port, or host,port,user,pass.
Click Generate.
Take the contents of the Output field: Copy All, or download it as .txt or .csv.
Every line uses the configuration you built above, but with its own unique session ID. So a list of 50 gives you 50 independent sticky sessions - which is exactly what you want when running 50 browser profiles that must not share an IP.
Generate List produces bulk credentials, each line carrying its own session ID.
I changed something on this tab. Do I need to save it?
No. There is nothing to save. The tab only produces text. What matters is the string you copied - once it is in your code, the tab has done its job.
I closed the page and my configuration is gone. Did I lose anything?
No. Rebuild it in a few clicks, or better, keep the copied connection string in your project. If you want a configuration to be permanent, set it as the proxy’s default on the Settings tab.
Can I use several different configurations at the same time?
Yes, and this is the main advantage of the design. One proxy, many usernames. Nothing is locked, nothing conflicts, and you are not charged extra for it - billing is based on the traffic you use, not on how many configurations you generate.
Why is the ZIP Code field greyed out?
Because you have selected a Region or a City. ZIP and Region/City are two competing ways of narrowing down a location and cannot be used together. Clear the Region and City fields and ZIP becomes available again.
Why does my username look different from the examples in the docs?
Yes. The tab is a convenience, not a requirement - anything it generates you can type yourself, and anything you type correctly will work. The parameter reference is in Geo-Targeting Parameters. Most people use the builder because it removes the typo risk.
The generated code returns an error. What now?
First run the snippet unchanged against https://api.ipify.org - that isolates whether the problem is the proxy or your target site. If it still fails, check the Error Codes page, and make sure your account balance is positive.
