The credential line shows up in your dashboard a few seconds after payment clears: positions held in stock are handed over almost instantly, the rest take up to a minute. What follows decides the fate of the batch — the first fifteen minutes. In that window the account either settles into a profile and works, or picks up a checkpoint and turns into a replacement case. Below is the order of operations, minute by minute, exactly as it should be carried out.
00:00–00:02 — save it before you open it
The first move after delivery is not the login. Every position in the order card has "Download .txt", and the whole order has "Download all" and "Copy all". The file lands under a name like order-4872-sku345.txt: the number after sku is the position article, and it later tells you which batch a line came from. When an order holds several positions, its index goes into the name too: order-4872-2-sku228.txt.
Download before the first login. The line in the dashboard does not change afterwards, but the account does — and if an hour later you need to compare the original password or the original cookies, there is nothing to compare against when the data only ever lived in a browser tab. One file per order, a folder per date, nothing forwarded through messengers.
00:02–00:04 — split the line by its separators
The format is written into the product title itself, after the word "Format". There are eight of them on the storefront, and the difference is not cosmetic.
Login:Pass|Cookie— the baseline. The colon separates account fields, the vertical bar cuts off the cookie block.Login:Pass:2FA_code|Cookie— the third field is the base32 secret for a code generator, not a ready six-digit code.Login:Pass:2FA_code|Cookie|Email:EmailPass— the fourth block is access to the attached mailbox, its login and password split by a colon.IAM,IAM (no Cookie),IAM|Email:EmailPass,IGAM,INSTAMEN— whole lines built for a specific account manager. You do not cut them up by hand, you paste them into the import of the software they were assembled for.
A manager-format line is not useless if you intend to work in a browser: the real sessionid sits inside its header block, wrapped into Bearer IGT:2:. The converter's reverse direction pulls it out together with ds_user_id and mid and assembles browser cookies from them. IAM carries four blocks — the account, a User-Agent shaped like Instagram … Android (25/…), the device-id and the headers — with the mailbox, when it ships, appended at the tail after a double bar.
Count the lines in the file at this same step. There must be exactly as many as you bought; a mismatch shows up in five seconds and gets sorted out before you have spent half an hour on profiles.
00:04–00:06 — the proxy comes up before the profile
The order is exactly that: a working exit first, the environment second. A profile created with no proxy and opened once has already shown your home IP next to its fingerprint, and that cannot be un-taught after the fact.
- Type — mobile or residential. A datacenter range is recognised on the very first request, and access limits follow.
- Geo matches the country of the account. A "Real Device SMS | Colombia" batch routed through a European exit returns a verification straight away, before you ever see the feed.
- One exit per account within the session. Rotation in the middle of a login reads as a device change.
- The profile timezone and interface language are set by the exit country, not by yours.
- Before importing, verify the actual address and who it belongs to — not what the panel you took the exit from claims, but what is really presented outward.
00:06–00:09 — the profile and the cookies
The profile comes up empty: its own fingerprint, its own proxy, nothing inherited from the neighbouring one. The account moves in on cookies rather than on a password — that is what the Cookie block in the delivery line is there for. A new user of AdsPower gets two free profiles, and on the first couple of lines that is enough to keep the purchase out of the same browser where your personal account is open.
Cookies arrive either as a csrftoken=…;sessionid=… string or as a JSON array, while the profile field expects an array of objects with full attributes. There is no need to reshape them by hand: the format converter builds ready JSON for .instagram.com out of the line — path /, secure, httpOnly on sessionid. A button in the order card leads there and carries the selected lines over on its own.
00:09–00:11 — the first login and what it showed
Authentication is done by sessionid. Instagram sets csrftoken itself on the first request, so its absence from the cookie set is not an error. Then look at what opened.
- The feed loads, the avatar is in place — normal, touch nothing else.
- A confirmation prompt offering email or phone — the session is alive, the profile is being asked to identify itself. If a mailbox shipped with the line, the code comes from there.
- A selfie-video demand — the line is unusable for work, there is no point going further with it.
- A request error at the login itself — more often a conflict with the exit than a block. Change the address and repeat exactly once.
- A password form instead of the feed — the cookies did not take. The usual cause is the domain or the path on import, less often a session already invalidated.
The password is not typed by hand at this step. A manual login on top of a live session can zero it out, and then re-importing cookies will not save it: the same confirmation prompt comes back.
00:11–00:13 — the replacement window
Replacement of invalid accounts within 30 minutes counts from the purchase, not from the moment you got around to the line. That is the whole reason for the order above: by minute eleven the state of the account is already known, and almost as much time again is left. A request needs the order number and the position article — both are in the name of the downloaded file — plus what the first login showed.
A batch of fifty lines and up is not checked end to end. Take a sample of 5–10 from different places in the file: the head, the middle, the tail. Lines inside one supply are homogeneous, so a clean sample means the rest can be laid out into profiles calmly; two invalids out of five in the sample turns the question into one about the whole position, raised inside the same window.
00:13–00:15 — what is not done in these minutes
- No password change. It kills every other session and, on a fresh login, looks like a takeover; leave it for a day.
- No switching off 2FA when it shipped with the account.
- No touching the avatar, the name, the bio or the link in the header.
- No following, no likes, no direct messages.
- No two tabs open at once — the working one and the personal one — in the same environment.
- No VPN extension stacked on top of the profile proxy: two routes produce a mismatch between address and timezone.
What carries past the fifteenth minute
After this the profile is closed and left standing; warming starts the next day and runs on its own schedule. Five facts carry out of the first fifteen minutes: the file is saved and named by article, the format is identified, the exit matches the geo, the login went through on cookies without a password, and questionable lines were sent for replacement inside the window. Everything after that is work, not acceptance.
Formats and articles per position are visible in the catalog, and a delivered line can be reshaped in the converter.