Cookies help make your profiles look like real users by building a browsing history. The best time to collect cookies? Right after creating a profile! That way, your profile has a natural cookie trail before visiting important sites.

Our Script runner API offers a cookie-robot command, allowing you to start collecting cookies in no more than 5 steps!

Open Multilogin CLI 

Follow the following article for more info: How to start working with CLI.

Run default settings

1. Log in via xcli login --username yourname --password yourpass
2. Collect one or more profile IDs you wish to gather cookies
3. Enter xcli cookie-robot --profile-id “profileid” → your browser will open in headless mode and start collecting cookies!

Customize settings

There are several customizable parameters that influence how the crawling process works. They allow users to adjust settings such as the target website, crawling order, and more. By fine-tuning these options, users can optimize the script’s performance to their specific needs.

--profile-id

 An object containing a profile ID number. Multiple entries can be added.

--website

An object containing a website that will be crawled by the CookieRobot, such as --website=https://google.com. Multiple entries can be added.

--random-order

• --random-order=true → mix things up and visit sites randomly
• --random-order=false → keep everything in order and visit sites as listed

--fraction-mode

Want to run just a portion of the websites, instead of all of them as default? Choose a float number between 0.0 and 1.0 (0% to 100%) as the fraction.

• --fraction-mode=0.5 will run 50% of the websites in the list

--process-cookie-consent

Many websites display an “Allow Cookies” button due to privacy laws like GDPR (What is GDPR?), which requires user consent before tracking cookies.

• --process-cookie-consent=true →  CookieRobot will click the consent button automatically (default)
• --process-cookie-consent=false → CookieRobot will ignore cookie pop-ups. This can be useful if:
  • You're browsing non-EU websites that don’t show cookie banners
  • You’re not concerned about GDPR compliance (e.g., using proxies outside the EU)

--closeBrowser

If you want to close the profile after running the script – you can change that parameter. Or you can do the opposite.

• Set to “true” → profile will be closed (default)
• Set to “false” → profile will stay open