Dolphin provides automatic updates for accounts, campaigns, adsets and ads.
In order for the data to be loaded automatically - you need to set the appropriate interval for this action. You can do this in the Settings.
It is necessary to enable the function "Sync account data" and set the desired value.
To set the right values for updating accounts with mobile proxies, you need the number of maximum number of accounts per mobile proxy, (for example if you have two mobile proxies, one with 15 accounts, the other with 30, you take the number 30) and calculate 0.6*(number of accounts)
For example: if you have 15 accounts added to 1 mobile proxy, an acceptable interval would be 0.6*30=18 That is, 18 minutes. + pause between IP updates (at the moment we do not have the functionality to change the IP when requesting in the interface).
As soon as we implement the IP update functionality on the link, we will create an article Working with Mobile Proxies Dolphin {Cloud} in our Help Center.
What happens if you set the intervals less than recommended above?
It's very simple, Dolphin will not have time to load the correct data, loading your proxies at the same time. Now let's be more specific. You have 20 accounts added, the update interval is 10 minutes. After that time begins the process of downloading new data, the update of 1 account takes about 1 minute. Accordingly, after 10 minutes Dolphin has time to update only 10 accounts and starts the process again, starting from the first account, at the same time updating the data on the remaining from the previous update. This way the proxies and Dolphin itself in particular are loaded. That's why we recommend to set the intervals according to the above rule.
Less than 15 minutes is not recommended. FB does not update statistics more often than once every 15 minutes.
Server proxies are devoid of such problems, because they do not need to change IP and, logically, do not require waiting for a pause between requests to change them.
If you want an account not to be automatically updated, you should put a "no-update" tag on it.
⚠️One of the important points is the priority of tasks.
Requests in the interface (manual) ALWAYS have priority over automatic updates. If the automatic update is currently running, but you need to perform some action (create an FP or bind a pixel), then that action will be performed first, and the update will be interrupted until your task is finished.
Autofill also has priority over data update. Accordingly, when you start the autofill, the consequences will be the same as in the case of manual requests from the interface, to be more precise - first the filling will be finished, and only after that the data update will be resumed.