When login setup is needed
Login or cookies may be required when:- The website hides data behind an account
- Search results or detail pages require authentication
- The website shows different content after login
- A session expires during extraction
- Cloud runs fail because the login state is not available
- Cookies control region, language, or user-specific content
Typical workflow
Use Browse Mode
Interact with the page like a normal browser to complete login or reach the desired page state.
Save the session setup
Configure the task so the required login or cookie state is available during extraction.
Cookies and sessions
Cookies store information that helps a website recognize a browser session. They may include login state, preferences, region, language, or tracking information. For scraping tasks, cookies matter because the website may show different content depending on whether the session is valid.Common issues
| Issue | Possible cause |
|---|---|
| Task returns login page | Session expired or login was not preserved |
| Works locally but fails in cloud | Cloud run does not have the same session state |
| Data differs between runs | Cookies, region, or account state changed |
| CAPTCHA appears after login | Website detected unusual session behavior |
| Task stops after some pages | Session expired mid-run |