Introduction
Connect product signals, your audience, and research evidence to your development workflow.
On this page
Askdepth connects product signals with research and the tools you use to build. These developer docs cover the browser SDK, your own audience connector, and access to workspace research through MCP.
Choose an integration
| Your goal | Start here | What you need |
|---|---|---|
| Capture events and frustration signals in a web app | Browser SDK | A public write key and collector URL |
| Use a React or Next.js app | React & Next.js | React 18+, plus SDK configuration |
| Capture context around friction | Session replay | Browser SDK, replay package, consent |
| Connect an existing user database | Audience Connector | A server you control and read access to your database |
| Read research from your coding agent | Codex or Claude Code | Workspace membership and OAuth authorization |
| Set up hosted Claude execution | Claude Code routines | A supported cloud routine and GitHub setup |
These integrations are independent. You can connect MCP without installing the browser SDK, or install the SDK without connecting a coding agent.
Understand the packages
| Package | Role |
|---|---|
@askdepth/core | Browser collection, events, identity, consent, and tracing |
@askdepth/react | React Provider, hooks, error boundary, and compiler integration |
@askdepth/replay | DOM recording and bounded replay uploads |
@askdepth/contracts | Telemetry, replay, and tracing schemas and types |
@askdepth/audience-contract | Request and response schemas for your audience connector |
The Audience Connector guide also uses @askdepth/audience-connector, a server helper package. The two contract packages describe different protocols; they are not interchangeable.
Follow the shortest path
- Choose one integration above.
- Read its prerequisites and copy the configuration for your own environment.
- Install the documented package versions and run the smallest example.
- Complete the guide's verification step before expanding the integration.
Versions and availability
Package guides identify the npm version they were reviewed against. SDK package versions, telemetry protocol versions, and the Audience Connector protocol version are separate. Read protocol versioning before building a custom producer or collector.
Feature access depends on the current workspace role, plan, and platform configuration. The platform's connection screen is authoritative for your account. These public docs do not grant access to a workspace.