Setting Up the Scraping Browser
ZenRows® Scraping Browser works seamlessly with your existing Puppeteer or Playwright code — just one line of code is needed to integrate, making it ideal for developers looking for fast and easy solutions.
Initial Setup
To start using the Scraping Browser, follow these steps:
Sign Up for ZenRows
If you haven’t already, create a ZenRows account by visiting the Registration Page.
Head to your Scraping Browser dashboard
Once registered, log in to your dashboard to access your Scraping Browser page.
Scraping Browser Parameters
ZenRows® Scraping Browser is designed for ease of use with minimal configuration. However, you can still customize some options to suit your needs, including World Region, Country and Session TTL.
You can adjust the following options:
World Region
Select a world region to focus your scraping on a particular geographic area. Simply update your proxy settings to access IPs from your preferred region.
Without using the SDK, you can specify the region by appending the proxy_region
parameter to your WebSocket URL:
In SDK mode, you can specify the region when generating the connection URL:
Country
When set to Global
, you can choose specific countries to target for geo-restricted data. A full list of available countries is accessible through our Premium Proxy Countries List.
Without using the SDK, select a specific country by adding the proxy_country
parameter to the WebSocket URL:
In SDK mode, specify the country when generating the connection URL:
Session TTL
You can control the duration of a browser session by using the &session_ttl
parameter. The Session Time To Live (TTL) determines how long a session remains active, with a default value of 3 minutes. The session duration can be customized between 1 minute (60 seconds) and 15 minutes (900 seconds).
In SDK mode, specify the session time in seconds using the sessionTTL
parameter. The value must be a number, as duration strings are not common in JavaScript. Here’s an example where the session is set to 2 minutes (120 seconds):
Without using the SDK, append the session_ttl
parameter (duration string) to the WebSocket URL to adjust the session duration:
Was this page helpful?