Boomly

What to prepare before buying accounts

The checking window is counted from the purchase. Everything that can be done before it has to be done before it.

Why this is a question of time rather than convenience

The replacement guarantee runs for thirty minutes from the purchase. Assembling the order takes one to two minutes, five at most, and that time is already inside the window. If after receiving the delivery you start installing a browser, buying proxies and figuring out the account manager, the window closes before you get to the first login.

Hence a simple rule: before payment you should already have everything needed for the first login. Below is what exactly, in order of importance.

Hand-over and connecting are two different actions, and confusing them is expensive. Hand-over answers the question «is this what I was given», connecting answers «does it work on my side». The first is limited to half an hour, the second is not limited in time at all, but starting it before the first is finished is not worth it.

It is worth checking not only that the software is there but that it works on an empty profile. A program installed six months ago and never launched since is the same unresolved question, only postponed to the most inconvenient moment.

The tool for the format

The first thing settled before the purchase is what you will open the delivery with. The formats in the catalogue fall into two groups, and they are incompatible with each other.

  • IGAM and IAM profiles are opened by the account manager; «Format: IGAM» means InstAccountsManager and nothing else.
  • Separately there is «IAM (No Cookie)» — the same profile, but with no ready session inside, the login goes by login and password.
  • The text shapes — Login:Pass|Cookie and Login:Pass:2FA_code|Cookie — suit an antidetect browser, a manager or your own script.
  • If the tool is already chosen, positions have to be filtered by the «Format» mark in the title rather than by category.

A mistake here costs more than the others: a batch in the IGAM format bought for an antidetect browser will not become usable in thirty minutes or later. And that is not a case for replacement — the format was stated in the position title.

The practical side of the choice looks like this: if you have an account manager, both groups of formats are open to you; if it is an antidetect browser or your own script — only the text ones. That narrows the catalogue more than any category does, and the narrowing has to be done first.

A reverse check is useful as well: make sure your tool accepts exactly the text shape you are taking. The field order differs between batches, and bringing it to the shape you need is easier with the converter on the site than by editing a file by hand.

Proxies and the environment

The second point is the network. An account registered with a Brazilian number and an account registered automatically through an API behave differently, but they have one thing in common: the first session sets the picture, and making it from an address that sharply diverges from the origin of the batch is a bad idea.

The country of registration is not stated for all the product: it occurs as a feature of part of the real-device positions rather than as a separate catalogue section. If geo matters for your task, you have to look for it by a search in the title, and in advance too.

For positions with a stated country the logic is direct: the proxy is sensibly picked for the country of registration written in the title. For fresh batches what matters is not geography but stability: the account has no login history, and any contradiction in the environment at the start is more noticeable than on a stored one.

The practical minimum is a separate profile and a separate address per account, prepared in advance in bulk for the whole volume of the batch. Setting them up one by one after the delivery means stretching the connection over hours, and in the first thirty minutes you will manage to check only the start of the list.

Separately worth remembering are empty profiles of a large age — positions where an archive age mark and the «Empty» mark stand side by side. Age here means only the term of existence, not accumulated activity: an account that did nothing for years and then suddenly became active looks uncharacteristic for itself.

User-Agent strings are a separate position, not an add-on

If your process requires every account to have its own User-Agent string, it has to be built into the same purchase. It does not arrive together with the account: in the catalogue this is a product of its own with its own format — one value per record.

This is the only product in the catalogue that is not an account, which is why it is easy to miss when planning a purchase. It lies separately among the categories, is not included in the set with accounts and is picked for your scenario rather than for a particular batch.

The varieties differ by purpose, and that is visible right in the position title. There are variants for iPhone and Android, Web and API variants, as well as strings marked «for InstAccountsManager» — taken by those who work with the account manager.

  • The «string» format — one value per record; there is no login, no password and no cookie there.
  • Positions marked «for InstAccountsManager» are intended for the account manager, and the format on them is stated as «Format: string» all the same.
  • The iPhone, Android, Web and API marks describe which environment the string depicts.
  • The minimum batch on such positions varies the most — look at the card before placing the order.

Checking such a position at hand-over is the simplest of all: exactly as many lines must arrive as were paid for, and each of them must be one value without separators. Anything else is a discrepancy with the description and a reason to write to support before the window expires.

This is exactly the case where preparation saves the window. Buying strings after the accounts have been delivered means spending hand-over minutes on a second order. It is simpler to take both positions at once and lay them out across the profiles before the first login.

A checklist before payment

PointWhat for
The tool is installed and startsso that the window is not spent on installation
The position format is compared with the toola profile and a text line are not interchangeable
The proxies are preparedthe first session sets the picture
The balance is topped upa charge from the balance goes at once, without waiting for a transfer
The format converter is openparsing the delivery takes seconds and catches discrepancies
The support bot is openthe request is sent without being distracted by looking for the channel
The order number and the SKU are knownthey are what you contact support with if something did not match

A topped-up balance is on this list for a reason. With a direct cryptocurrency payment, the network confirmation time passes between the transfer and the delivery, and the stock in the catalogue may change during it. A charge from the balance happens at once — the order is assembled without waiting.

The list looks long, but it is walked through once: from the second purchase onwards only the line about the format changes in it — it is compared anew for every new position. The rest is already set up and working.

The last point is worth going through in advance at least once: contact with the shop runs through Telegram only, it does not use e-mail, and there is no phone and no office. Looking for the channel in the twenty-ninth minute of the window is a bad idea.

Short answers

Related pages