What Things Trigger Identification/Verification For New or Aged Account?

SLL

Registered Member
Joined
Sep 3, 2019
Messages
82
Reaction score
3
Particularly if you are recreating an account that Facebook just deleted. For an average, non-advertising account. Keep in mind the two triggering scenarios: (1) for an aged account of 2+ years that you just bought from someone, and (2) for a newly-created account that you just made.

Additional optional questions:

Is it even possible to make a Facebook now without it asking for verification or identification?

Is creating a Facebook at a library or Starbucks preferable to making one over a residential connection or not?

Would creating it as a youth (under 18) as opposed to an adult prevent triggering verification?

After one is successfully made, about how long until you can use a common VPN to connect to it? (Assuming you still use the same cookies.)

How many people can you add or message a day on a new or just-bought aged account?

After acquiring an aged account, how long should you take to change the name, email, password, photos, information, etc.? Which should be done first and last?

If a seller of an aged account that has not been actively logged into or maintained for years promises that you can successfully log into it without using their cookies, is that a stretch? Why do other sellers say you need cookies?

Thanks!
 
I have tested many things in the past few months with aged and brand-new Facebook accounts used for scraping and my findings are basically the below. These may or may not be relevant for your use as this was primarily concerning automated browser sessions:

1. Use a unique proxy IP for each account, never mix up this IP with another one. Only ever sign in the account with this proxy.
2. Most importantly, reuse valid cookies. Nothing triggers Facebook's bot detection like an account repeatedly signing in multiples times per day. A normal user signs in maybe once per week. Log the account in, save the cookies however you are able, reinject the cookies next time you use this account to continue a valid session.

With the above, I have seen very little difference between phone verified aged accounts and phone verified brand new accounts.

Regarding verification, I had almost no success creating accounts without some sort of phone verification being involved. Facebook is increasingly heading in the direction of requiring more and more personal info to create an account.
 
I have tested many things in the past few months with aged and brand-new Facebook accounts used for scraping and my findings are basically the below. These may or may not be relevant for your use as this was primarily concerning automated browser sessions:

1. Use a unique proxy IP for each account, never mix up this IP with another one. Only ever sign in the account with this proxy.
2. Most importantly, reuse valid cookies. Nothing triggers Facebook's bot detection like an account repeatedly signing in multiples times per day. A normal user signs in maybe once per week. Log the account in, save the cookies however you are able, reinject the cookies next time you use this account to continue a valid session.

With the above, I have seen very little difference between phone verified aged accounts and phone verified brand new accounts.

Regarding verification, I had almost no success creating accounts without some sort of phone verification being involved. Facebook is increasingly heading in the direction of requiring more and more personal info to create an account.

The proxy itself is most likely not used only by yourself. You not using it multiple times doesn't mean that other users of the same proxy aren't using it for the same purpose - FB.

Never have I ever added phone number into FB account in the last 3 years of my work with BH ads.
 
I should add that I use only 100% private dedicated proxies. They definitely cost more but obviously any shared proxies are going to get you shut down sooner or later.
 
Using a commercial VPN services definitely triggers facebook. Look for residential proxy solutions if you want to be 100% covered.
 
Using my own 4G connection (i reload when i need to change IP) but i still receive selfie requests even if i sign-up through cellphone number and not email.

Obviously using thispersondoesntexist i don't have a selfie.
 
I have tested many things in the past few months with aged and brand-new Facebook accounts used for scraping and my findings are basically the below. These may or may not be relevant for your use as this was primarily concerning automated browser sessions:

1. Use a unique proxy IP for each account, never mix up this IP with another one. Only ever sign in the account with this proxy.
2. Most importantly, reuse valid cookies. Nothing triggers Facebook's bot detection like an account repeatedly signing in multiples times per day. A normal user signs in maybe once per week. Log the account in, save the cookies however you are able, reinject the cookies next time you use this account to continue a valid session.

With the above, I have seen very little difference between phone verified aged accounts and phone verified brand new accounts.

Regarding verification, I had almost no success creating accounts without some sort of phone verification being involved. Facebook is increasingly heading in the direction of requiring more and more personal info to create an account.

Whats your problem creating or keeping them alive? I was creating some accounts months ago to test some things with payments,mainly that got my accounts deactivated.Not touching it shouldnt be too hard at least by the way I look at it when I did it.
 
Back
Top