It does not explain while, like someone else made notice, the problem suddenly appears after the block. I didn’t have it before, anyway beside this, my audience is female, but is not that is made by young girls, it’s made by adults.
More than 700 is useless, higher it is and less probable is that they will notice my posts. The idea should be applied filters in order to have people related with you and that engage, not simply a list of numbers that don’t see your posts or that never interact because they have opened IG three weeks ago.
There is a name list since the beginning.
1 Like
Could you help me get better settings
My guess is, the more restrictive your filters, the harder jarvee will need to work to match your settings and the more actions and queries will need to make agains IG api, so it will probably be categorized as suspicious activity. Probably now IG is limiting this queries and that´s why you don´t get results after 20 minutes of searching and bans after lots of searches.
2 Likes
I wonder how Jarvee filters by gender. I scrap user info by looking at window._sharedData.entry_data.ProfilePage[0].graphql.user of the user’s page but I don’t see gender in their graphql json.
1 Like
agreed they need to bring it up to date w/ most recent IG alg updates
1 Like
They use names. I filter by gender based on my own list of names, not the ones set by jv.
2 Likes
Okay so the golden nugget is setting the intervals?
1 Like
Exactly this!
The more filters you set up in place, the longer it takes Jarvee to perform actions, and therefore you’re increasing the time connecting to the platform. It’s really down to API request limitations (hence why forcing EB sometimes fixes the blocks). They did an API limitation a while back (1 year ago I think) and they’ve clearly done an unannounced one recently.
2 Likes
Anyone use the favor sources with high follow back ratio option on a large scale? What are your opinions on it?
3 Likes
So it’s still better to do EB with the filters than Api with no filters or less filters. I dont see any benefit from removing those or you’ll get followbacks from non targetted non engaging followers which will result in those engagement drops people talk about.
1 Like
I think it’s best to just only use the EB when you experience blocks 
2 Likes
yes actually what you are saying is making sense. I have always kept minimum number and max number of posts so when i choose that it is going to just check the number of posts in bio of scrape all of the posts? i am going to change the settings of some of the accounts and remove the recent post and number of post option.
2 Likes
You can use some accounts dedicated for only scraping if you want to speed up the tool.
1 Like
that’s right and I didn’t have thought about it thanks
1 Like
So would you rest the account after there is an API block or just move straight to EB? I always used to rest it and then slowly got it back up again with API but maybe switching straight to EB could help with the upset clients who are not getting any new follows while they get an API block.
1 Like
bro i am a bit confused can you tell me when i set the settings as eg - min no of posts - 45 then is mp going to go to each profile and scrape their recent 45 posts? or is it just going to take the number from the posts in bio and understand that the user has 45 posts?
I don’t like using EB as backup plan when doing client management. You will be banned again in no time + you will get lots of support ticket asking if their account got hacked because IG will send them login notification email.
Best bet is keep optimizing your sources bruh!
@rajasosmed Any tips in order to optimize my sources my friend ?
@LuisEduardo May I ask which proxy are you using with the clients/important accounts?
@Aaron_Ward Can you give your opinion about His reply?:
Just providing an update about my current situation
-
Personal business account, home IP, running ads around 7 days in a month.
-
Automation limited to like, follow, unfollow. Warmed up following the suggestions provided by the automation team and increased settings in the end of April.
-
Running between 11 and 13 hours per day, 250 avg follows per day, 240 avg likes per day and using EB.
-
Account was older 6 months when received a temp like action block in May 21. Waited, restarted, blocked again. Unchecked the function “like post after follow” all good.
-
Blocked 3 times in a row during the block wave of June 5th (+/-)
-
ID reset and restarted in June 14th by adding the execution time slots that you can see in this post but with a lesser number of executions, around 2-3 less. I was following 40-50 as avg per day, running the tool 9-10 hours per day.
-
It didn’t works anyway. July 1st I’ve been blocked with the common problems, first the block in EB resolvable by deleting cookies and lately in July 14th with the function logout/login introduced in the tool update.
-
I’ve tried to manual follow via browser but the scraping function it’s not this cream, the import had problems, the unfollow process was too articulated and I stopped. IG continued to block my browser experience from PC other 2 times. I suspect that the block was related with the starting of the automation tool, I mean just the simple scraping.
-
With the idea of giving a last try before abandon the tool, I’ve started again with like automation in July 23th so far so good. Added several execution times also for likes automation. Currently 28 avg per day. No ID reset. Switched to API and EB only when action blocked. EB logout/login checked.
-
Follow automation started in July 25th, so far so good. 13 execution time slots, running for 11-12 hour. Currently 29 follow avg.
finger crossed.
and I think the same of @oneoneseven
No, you understood me wrong. I told you to disable at ALL those 2 options like here: http://prntscr.com/oku8q2
1 Like