How to use your purchased account

What you need before the first login

One rule matters more than everything else on this page: one account = one browser profile = one IP. Accounts opened in the same browser or from the same address get linked within days, even with different passwords and emails.

Prepare three things before you log in:

1. An antidetect browser — a separate profile per account. A regular Chrome gives every tab the same fingerprint: fonts, canvas, hardware, time zone.
2. A proxy matching the account geo — residential or mobile, with a sticky session. The proxy country must match the account country listed on the product card.
3. A saved delivery file — download the .txt to disk right away. The in-browser download link only works while that tab is open; once closed, the link is dead. A copy always stays in your account area and in the mini app.

Your delivery format explained

A standard line in the file looks like this:

login|password|Cookie|Email:EmailPass

• login — the account username. Enter it as is, without @.
• password — the account password.
• Cookie — a saved session. Logging in with it is softer: the platform sees a continued session rather than a brand-new device.
• Email:EmailPass — the email attached to the account and its password. Confirmation codes and recovery go through it.

The separator is a pipe |. A password may contain any character, so split the line by separator positions rather than by a blind search-and-replace.

Field sets differ between batches: some come without an email, some deliver cookies as JSON, some include a 2FA secret. The exact format of a given position is always stated on its card, next to the quantity in stock.

If cookies arrive as sessionid=...; ds_user_id=... while your browser expects JSON, convert them with our format converter. It runs in your browser and sends nothing to the server.

Step 1. Create an antidetect profile

An antidetect browser gives each profile its own fingerprint: its own canvas, font set, hardware model, time zone and cookie storage. To the platform these are different devices, not ten tabs of one person.

1. Create a new profile per account. Never reuse a profile that already held another account — cookies and localStorage stay behind.
2. Keep the OS and browser version typical for the account country. Exotic setups stand out more than a plain Windows + Chrome.
3. Set the interface language and time zone to the proxy country, not yours. A time mismatch is one of the most common triggers for a check.
4. Switch WebRTC to a mode that does not expose your local IP.
5. Name the profile after the account login — in a week you will not remember which is which.

We work in : 2 free profiles with no card required, cookies pasted into a single field on the profile card, and RPA for routine work. Dolphin Anty, Octo and GoLogin solve the same task — if you are already used to one of them, stay there; the steps below are identical.

Step 2. Attach a proxy matching the account geo

A profile without a proxy is pointless: the fingerprint will be unique but the IP shared across all your accounts — and the address is what gets linked first.

• Type: residential or mobile. Datacenter ranges are a lottery for social platforms — those ranges are well known.
• Geo: proxy country = account country from the batch card. A US account on a Polish IP looks like a takeover.
• Session: sticky, for at least a few hours. Rotating every five minutes drops the session and invites a check.
• One address — one account. More expensive, but cheaper than losing the batch.
• Check before logging in: open any IP-check service inside the profile. Country, time zone and language must match, and there must be no WebRTC or DNS leaks.

Step 3. Import cookies

1. Launch the profile and confirm it goes online through the proxy.
2. Open the platform domain (a blank login page) — cookies are set on an already opened domain.
3. Paste the cookies: in AdsPower it is the Cookie field on the profile card, in Dolphin Anty the Cookies tab, or use any importer extension.
4. Refresh the page. If the session is alive you land in the feed without typing a password.

Formats you will meet: a JSON array with name, value, domain, path, expirationDate, secure, httpOnly; a Netscape .txt file with tabs; a single name=value; name=value string. Every antidetect browser understands the first one, and the other two convert into it with our converter in seconds.

Step 4. First login and check

• If the session opened via cookies — do nothing for 10–15 minutes. Scroll the feed, open a couple of profiles, close them. It is the cheapest way to pass the first check.
• If a password login is required, type the credentials by hand instead of pasting everything instantly — input speed is read too.
• After logging in, open security settings and review active sessions: only your country should be there.
• Do not change the password, email or name on day one unless the platform demands it. Changing credentials right after a login from a new device is the classic takeover pattern.
• Do not add the account to a mobile app within 24 hours of a desktop cookie login.

The account counts as working if the feed and profile open, there is no forced phone confirmation and no restriction banner. That is exactly the state we guarantee on delivery.

Step 5. Warm-up: the first 72 hours

Warm-up is not a ritual — it is how you show the platform familiar behaviour from a new device. The first three days decide how long the account lives.

• Day 1 — read only. Feed, search, 5–10 other profiles. Zero actions: no likes, follows or messages. Two sessions of 10–15 minutes.
• Day 2 — minimal activity. 3–5 likes, 1–2 follows, some stories. Still two short sessions.
• Day 3 — first footprint. One comment, a couple of saves, another 3–5 follows. An avatar is fine — but do not rewrite the whole bio at once.
• From day 4 scale gradually: stay within 20–30 actions per day for the first week.

For the whole week log in from the same profile and the same IP. Every new device or address resets the trust you have built and invites a check.

Seven mistakes that get accounts banned

1. All accounts in one browser. Even with different proxies, a shared fingerprint links them within a week — and you lose the whole set, not one account. Split them into profiles in an ; this is the one mistake on the list that cannot be undone afterwards.
2. Changing the password and email in the first hour. Wait three days and let the account get used to the device.
3. Rotating or shared proxies. An IP that changes mid-session looks like an interception.
4. Mass actions on day one. Twenty follows in a row from a new device is the fastest route to a restriction.
5. Geo mismatch. Account in one country, proxy in another, time zone in a third — a check is guaranteed.
6. Opening the mobile app right after a desktop cookie login. Two devices within an hour is a red flag.
7. Not saving the delivery. The download link lives only while the tab is open. Save the file to disk right after payment; a copy stays in your account area and in the mini app.

The account asks for confirmation: what to do

• Code sent to email. The email and its password are in the delivery line (Email:EmailPass). Open the mailbox from the same profile and proxy — mailbox logins are checked too.
• It asks for an email code but the batch has no email. Mailbox access is not part of that position (stated on the card). Request a replacement: the account counts as invalid.
• It demands a phone number on the very first login. Do not attach your own number — an account that forces a phone at login is invalid and gets replaced.
• A “suspicious login” checkpoint. Confirm by email, then do nothing on the account for 24 hours. Retrying within the same hour makes it worse.
• Two-factor code. If the batch includes a 2FA secret it comes with the delivery — add it to any TOTP app or the generator built into your antidetect browser.
• Cookies rejected. They simply expired. Sign in with the login and password from the same profile.

Account did not work: invalid replaced within 30 minutes

If the account does not open or demands something it should not, we replace the invalid within 30 minutes. To make it fast:

1. Contact support on the day of purchase, before changing the password or email.
2. Attach a screenshot or a short screen recording of the error.
3. Give the order number — it is in your account area, in the mini app and in the bot message.

The replacement comes from the same batch while the position is in stock. If nothing is left in stock for it, we offer the closest alternative or return the amount to your balance, which you can spend on any other position.

FAQ