How to prepare Facebook accounts for use in an antidetect browser: a pre-import checklist

An anti-detect browser helps conveniently separate profiles, environments, proxies, and work sessions. But the browser itself does not solve the main issue: what accounts you upload into it and how suitable they are for your task.

A common mistake is to first import a batch of accounts and only then figure out where each GEO is, whether there is a Fan Page, if a BM is needed, whether the proxy is suitable, if there is a card for the first billing, and how one account format differs from another. As a result, some of the profiles turn out to be redundant, some do not fit the task, and the team spends time sorting them manually.

It is much more convenient to do the reverse: first define the workflow scenario, then select accounts and consumables, and only after that upload them into the anti-detect browser.

In this article, we will analyze what should be checked before importing Facebook accounts and how to build a basic infrastructure for advertising, tests, BM, Fan Page, or the Instagram direction.

Define the task, do not just buy accounts 

Before buying accounts, it is important to answer a simple question: what are they needed for?

For a quick test, one format might be suitable. For an advertising structure with Business Manager — another. For working through a page — a third. For the Instagram direction — a fourth. For a temporary project, sometimes renting rather than buying is actually more profitable.

Conditionally, tasks can be divided as follows:

• quick tests and starting actions;
• working with Facebook Ads;
• working through Business Manager;
• preparing a Fan Page;
• Instagram direction;
• temporary access for 7, 14, 21, or 30 days;
• assembling a full setup: account, BM, Fan Page, card, proxy. 

If you buy everything "by name" or solely at the lowest price, it is easy to get a set that does not fit into a working system.

Do not confuse autoregs, farm, and PZRD 

One of the main mistakes is to assume that all Facebook accounts are the same. In practice, these are different formats for different tasks.

Autoregs are the basic starting option. They are often taken for tests, distribution across projects, simple scenarios, and situations where an expensive prepared base is not needed.

Farm accounts are a more prepared format. Usually, they are chosen when history, warming up (resting), activity, additional data, and a clearer package are needed.

PZRD accounts (reinstated/passed access restriction accounts) are a separate type of account that should not be mixed with regular farm accounts. They are selected for tasks where the status after the access restriction (ZRD) and the corresponding workflow logic are important.

Therefore, before importing into an anti-detect, it is better to immediately label profiles by type: autoreg, farm, PZRD, BM, FP, GEO, date, supplier, task. This will make it easier to manage them inside the browser and not confuse different scenarios.

Check the account package 

Before uploading an account into an anti-detect, you need to understand exactly what is included in the package.

At a minimum, you should check:

• login and password;
• email and access to it;
• 2FA, if specified;
• cookies;
• User-Agent, if included in the delivery;
• presence of a Fan Page;
• presence of a BM;
• account GEO;
• registration date or warming up (resting) time;
• additional data: token, documents, selfies, activity, friends, pages. 

The better you understand the package, the less chaos there will be after import. This is especially important if accounts are bought in batches rather than individually.

Decide on the Business Manager separately 

BM is not just "another account." Business Manager is needed for the advertising structure: ad accounts, roles, pages, limits, asset management, and teamwork.

For a simple test, BM may not be needed. But if the task is related to advertising, scaling, or managing multiple assets, it is better to understand in advance which format is suitable:

• a separate BM;
• an account with BM included;
• BM with a $50 limit;
• BM with a $250 limit;
• high-limit option;
• temporary rental of BM;
• BM with PZRD. 

The mistake here is very common: a person buys a regular account, and then realizes they need a BM. Or vice versa — they get a BM when the current scenario required a prepared personal profile.

It is better to plan the Fan Page in advance 

A Fan Page may be needed for advertising, a catalog, a showcase, a brand, an Instagram combination, or a multi-geo project.

Before purchasing and importing, it is worth understanding:

• whether a Fan Page is needed at all;
• should it be separate or included with the account;
• whether followers are important;
• whether the name can be changed;
• if a filled-out page is needed;
• which GEO and niche it will be used for. 

If a page is needed for advertising logic, it is better to take this into account even before choosing an account. Otherwise, you may get an account without the necessary page and then separately search for a Fan Page that will not always match your scenario.

Proxies must match the account logic 

An anti-detect browser provides the ability to separate profiles, but the quality of the environment depends not only on the browser. A proxy is a separate crucial element of the setup.

Before importing accounts, check:

• proxy GEO;
• proxy type — mobile, residential, datacenter;
• stability;
• rotation;
• speed;
• protocol: HTTP/SOCKS5;
• whether the proxy is suitable for the specific profile. 

The main idea is simple: the proxy should not live separately from the account. If the account, card, BM, and proxy are chosen for different GEOs, the setup becomes less logical and harder to manage.

For Facebook and Instagram, mobile 4G/5G proxies are often used because they are convenient for working with individual profiles and GEOs. But a proxy does not replace the quality of the account, BM, card, content, and user actions. It is only one element of the infrastructure.

Do not put off the payment part until later 

If the task is related to Facebook Ads, the payment part better be thought through in advance. Often, the account is already chosen, the BM is prepared, the Fan Page is there, the proxy is set up — and only then does it turn out that the card is not suitable for the required scenario.

Before launching, it is worth checking:

• BIN GEO;
• currency;
• limit;
• balance;
• compatibility with the task;
• backup options;
• first billing logic. 

A card is not just "the final step before paying for ads." It is part of the overall setup. If it is chosen at random, a problem may arise even before a full-scale launch.

Sort accounts before importing 

Before bulk importing, it is convenient to prepare a simple table. In it, you can specify:

• profile name;
• account type;
• GEO;
• supplier;
• date of purchase;
• presence of BM;
• presence of Fan Page;
• presence of 2FA;
• email;
• proxy;
• card;
• status;
• comment on the task. 

This approach is especially useful for teams. One person purchases accounts, another imports them into the browser, a third works with advertising, and a fourth monitors payments. If there is no common structure, profiles quickly turn into chaos.

When it is better to get a ready-made kit 

It is not always profitable to assemble everything separately. Sometimes it is easier to get an account that already contains the necessary elements: BM, Fan Page, selfie, warming up (resting), email, cookies, User-Agent, or other data.

A ready-made kit can be convenient if:

• you need to start quickly;
• there is no time to manually assemble the infrastructure;
• a clear package is needed;
• the account + BM connection is important;
• a Fan Page is needed in the package;
• the team works with a large number of profiles;
• you need to reduce the number of manual actions before importing. 

But even here, it is important to look not only at the product name. One kit may be good for tests, another for BM, a third for a page, and a fourth for Instagram.

Where to select accounts and consumables for the task 

If you need to build infrastructure for Facebook or Instagram Ads, it is more convenient to choose not a single random product, but a setup for a specific scenario: account, BM, Fan Page, mobile proxy, card, and backup.

At CrazyFB — shop №1 you can select various consumables for Facebook and Instagram Ads: autoregs, farm accounts, PZRD, Business Manager, Fan Page, Instagram accounts, mobile proxies, cards, and rental accounts or BMs for a limited period.

The main advantage of this approach is that you can choose not "what is cheaper" but "what is suitable for the task." For a test — one format. For an advertising structure — another. For Instagram — a third. For a temporary project — rental. For scaling — BM or high-limit solutions.

Mini-checklist before importing into the anti-detect 

Before importing accounts, check:

1. Whether you understand the account's task.
2. Whether the type is selected correctly: autoreg, farm, PZRD, BM, Fan Page, Instagram.
3. Is there access to the email.
4. Is there 2FA and is it clear how to work with it.
5. Are there cookies and User-Agent, if they were declared.
6. Does the GEO of the account, proxy, and payment part match.
7. Is BM needed.
8. Is Fan Page needed.
9. Is the card prepared for the first billing.
10. Is there a clear profile name inside the anti-detect.
11. Are there backup accounts or proxies.
12. Are different tasks not mixed up in one batch. 

Conclusion 

An anti-detect browser is a convenient tool for managing profiles, but the result depends not only on it. It is important what accounts you import, how they are prepared, whether they have the necessary package, and how logically the entire setup is assembled.

A good infrastructure starts not with the "import" button, but with the right choice: account, BM, Fan Page, proxy, card, GEO, operational period, and task. If all of this is thought through in advance, the work becomes clearer, and the team spends less time on chaos, rebuilding, and manual fixes.