The main feature of the new version is a possibility to run BAS scripts through Multilogin browser profile manager. Earlier we announced two additional features: interactive documentation and interface constructor. Unfortunately, the interface constructor won't be included in this release and interactive documentation is available only for browser actions.
Description Multilogin is an application for realistic emulation of browser fingerprint. Unlike other solutions that inject browser fingerprint through altering a page source code, Multilogin alters fingerprint on a browser source code level. There are no easy ways to reveal this change. This is why Multilogin in knowledgeable hands prolongs the lifetime of your bots and the efficiency of scripts.
Feature list To the moment, a big number of profile management features is implemented:
Multilogin browser has some unique settings. Those are Chrome extensions, WebRTC address altering, Canvas and WebGL masking and other. Multilogin team is now developing a new method of Canvas and WebGL fingerprint altering. This method will be very hard to reveal.
We would like to specifically mention a new module for storing browser profiles. Earlier Multilogin always stored browser profiles in its online cloud. For BAS users a feature to store browser profiles locally was developed. BAS can now store Multilogin browser profiles locally. If used together with a Multilogin plan that contains synchronized profiles, BAS can convert offline to online profiles. Thereafter such profile can be easily transfered between computers or different Multilogin accounts.
Testing Due to a big number of new features and the lack of time, browser automation functionality may still contain bugs. Several features weren't integrated for various reasons and were moved into the next work scope. We kindly ask you for understanding and join the beta-testing of a new version. For testing you will receive a free subscription with limits that allow comfortable testing.
We would like to note that browser fingerprint transfer and injection mechanism may also contain bugs. For this reason, we kindly ask not to use your valuable accounts for testing. We promise to promptly fix any problems related to this or to functionality in general uncovered during the testing.
:
You can check integration status at any time from this spreadsheet: https://docs.google.com/spreadsheets/d/1mE7ltBeUYKTi3Ot3yJJHknfN_8rZ0eXX0Sla22VOWiE/edit?usp=sharing
How to begin To join beta-testing please send email to [email protected] Make sure to put "BAS BETA" title and write your Multilogin registration email in the letter body. Multilogin supports automation with BAS starting from version 1.4.10. You can download it from following link. https://www.dropbox.com/s/h2qs92gde6z8qgy/multiloginapp-1.4.10.296-windows-x86_32-setup.exe?dl=0 You don't have to connect BAS and Multilogin together. BAS will discover Multilogin by itself.
Migration of your old BAS scripts to Multilogin happens in just 3 clicks!
Make sure that this action is added before page loading, preferably the very first.
You can also place "Use Multilogin" action inside "IF" action and link the condition to a resource. This way a script user will be able to change browser engine upon the script launch.
We made the migration process incredibly simple and convenient while fully customizable at the same time. Default browser configuration is optimal for most cases: WebRTC will set parameters that match your external IP, Canvas fingerprint will be masked, User-agent and Navigator objects will get unique values matching those of real browsers. But you can change all those settings in "Advanced settings" panel.
If Multilogin is used as a browser component, all old BAS actions will be applied to Multilogin browser. "Proxy" action will set a proxy for Multilogin browser. Actions "Save cookies" and "Restore cookies" will also work with it. Cookie format is identical to BAS. Insignificant discrepancies may happen in some rare cases.
By default, a profile is created in a temporary folder. In stores a browser fingerprint, cookies, local storage etc. Profiles from a temporary folder are periodically deleted. They also can be moved to a different folder which allows saving all data and then restoring it from a disk. For example:
This allows iterating over all profiles later in other script and skip account authorization(because cookies will be restored from profile).
Online profiles are also available. You can select them by using action "Switch to online profile". Here's a usage example:
After the thread has ended, data will be automatically saved to the cloud.
Multilogin browser will only work in execution mode. For record mode internal BAS browser will be used. Because all actions, selectors and other are identical between Multilogin and BAS, no problems should arise. Scripts gives the same results in both record and run modes.
Price
Because the potential load produced by BAS users is not yet established, automation plans pricing hasn't been worked out yet. There is a temporary price draft available through Multilogin customer support.