In this article, I'm going to show you step by step how to set everything as perfection and avoid errors that could make the new settings inefficient.
Please check the FAQ page before starting.
Purchase the accounts you need here (AirProxy is not affiliated with the seller, we suggest him because it's the best bang for the buck). The cheapest ones I linked are fine, buying the more expensive won't add any benefit.
The accounts will come in this format: email,password,username
Use the account email (and not the username) in Jarvee when adding the account.
The email coming with the accounts it's the original mail where the account was registered on and it's active. It's only accessible with POP3. Check below to know how to retrieve the 6-digit code in case of Email Verification.
Verify the account now, and solve the eventual Email Verification.
Now that the account is VALID, tag it as "SCRAPER".
Now copy all the follow/like sources you had in the main account to your scraper.
When done, set the scraper Follow tool as follow:
Move to the Follow Sources tab and add all the sources you had on your main account (and some more).
Let's move to the Extracted Users tab and set it up to send the scraped users to your main account.
I suggest keeping a limit of 200 scraped users per account because having more wouldn't add any benefit but would increase the scraper workload of API calls.
Select these two options:
And now select the account where the scraper will send the scraped users to (your main account):
All done for the scraper. Let's move to the main account.
NOTE: While we faced 0 issues using these scraper settings (not even a PV), a client with very strict filters reported having the accounts getting blocked from scraping one after another.
This means that even with such moderate settings IG will temporarily block your scrapers if you use a lot of strict filters. What should be avoided the most is using blacklists and whitelists.
With all tools set to OFF, go on the Advanced Settings of the main account and set them as follows:
Move now to the Follow Tool - Sources tab and enable "Follow Specific Users"
On the Follow Tool - Settings tab, do not set any filter for the main account. Filters are only set in the scraper.
Why? Becuase scraping is not covered by the API Full Emulation and scraping itself could cause PV/AC and blocks, thus we want the churn and burn accounts to do it for our mains.
Doing faster actions than what we usually do has decreased the blocks overall on accounts running on API.
Similiar settings to what shown below (short delays between each follow) have been able to decrease blocks from 70% to 40% on 200 clients accounts compared to the old settings (large delays between each follow).
At this point, both the main and the scraper accounts are set and with all tools still on OFF.
1) Start the scraper account Follow tool.
2) Go to SOCIAL PROFILES, select the main/client account, click on ACTIONS ON SELECTED PROFILES - re-login accounts
3) When the main account login has been completed, wait a few minutes and start the Follow Tool.
It doesn't need any scraper and it has to be set directly in the main account.
NOTE: do not set any User Filter other than "Unfollow all users followed by Jarvee".
Specifically, using "Also target users followed from outside Jarvee" will require 1 extra API call that isn't covered by the Full API Emulation. It shouldn't be enough to cause issues, but you do it at your own risk.
The same process as for the Follow Tool, you just do it in the Like Tool this time.
1) You should never re-login the account more than once every 2 days. Doing the re-login twice in a day will give you a 3 day hard block.
2) When getting blocked, just wait it out. Usually, you are able to follow after a few hours already. DO NOT re-login to skip the wait time, unless you want to get a 3-day block :)
This is why in the Advanced Settings of the main account we selected "Treat action blocks as temporary blocks" and "Suspend tool when temporary blocked between 3 and 6 hours" along with "Disable automatic API logout when action blocked".
Doing faster actions has decreased the blocks overall on accounts running on API (someone tests this on EB too guys!).
Similiar settings to what shown below have been able to decrease blocks from 70% to 40% (tested on 200 clients).