Marketers
See which channels and pages bring visitors who convert.
Review Browserbase session statuses, regions, project concurrency and persistent contexts in a read-only data source.
Start free Connect Browserbase
Updated November 2026
| Status | Region | Keep alive |
|---|---|---|
| COMPLETED | us-west-2 | 1,240 |
| Pending | 640 | 640 |
| Refunded | 210 | 210 |
See which channels and pages bring visitors who convert.
Get a weekly traffic summary without opening another dashboard.
Send each client the same clean traffic report every month.
Read sessions, projects and contexts using your Browserbase API key.
Datapipe reads Browserbase data for reports. It never changes anything in Browserbase.
Browser sessions are never created or modified.
Combine session status counts, regions and project limits in one report.
An API key or token from your Browserbase account.
Read access only. Datapipe never changes anything in Browserbase.
Read-only reporting access using your Browserbase API key. Browser sessions are never modified.
Headless browser sessions, projects, and contexts from Browserbase.
Read-only reporting access using your Browserbase API key. Browser sessions are never modified.
Headless browser sessions, projects, and contexts from Browserbase. Read-only reporting access using your Browserbase API key. Browser sessions are never modified.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Browserbase headless browser sessions with project ID, status, region, keep-alive, and timestamps.
Browserbase projects with concurrency limits and default session timeout.
Persistent Browserbase contexts with project ID and creation date.
13 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Summarize Browserbase headless sessions, project concurrency, and contexts.
412 sessions ran across us-west-2 and eu-central-1 with a 98.5% completion rate.
Browserbase headless browser sessions with project ID, status, region, keep-alive, and timestamps.
Use this template →Browserbase projects with concurrency limits and default session timeout.
Use this template →Persistent Browserbase contexts with project ID and creation date.
Use this template →Create a project and choose Browserbase in Data sources.
Pick where it goes. This one sends the numbers to PostgreSQL.
Pick where it goes. Choose Browser sessions, Projects, or Browser contexts and a destination.
| Session ID | Project ID | Status | Region | Keep alive | Created at | Project ID | Project name |
|---|---|---|---|---|---|---|---|
| sess_01 | proj_01 | COMPLETED | us-west-2 | 1,240 | 2026-11-13 | proj_01 | 1,240 |
| 1025 | 1025 | Pending | 640 | 640 | 640 | 1025 | 640 |
| 1031 | 1031 | Refunded | 210 | 210 | 210 | 1031 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
This integration is read-only in Datapipe. You can report on Browserbase, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Browserbase. Read-only reporting access using your Browserbase API key. Browser sessions are never modified.
This page lists 13 report fields across 3 datasets. You pick the columns when you build the report.
Headless browser sessions, projects, and contexts from Browserbase. Account permissions and the records available from the provider determine which rows can be read.
One for each Browserbase account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Browserbase when you are ready.