Verify your integration

Start with the smallest integration and verify each boundary. An installed package, copied command, or saved configuration does not confirm a working connection.

Browser SDK

1. Confirm your installed versions with npm ls @askdepth/core @askdepth/react @askdepth/replay.
2. Initialize only in a browser context with the intended public write key and full telemetry endpoint.
3. Grant consent through your actual consent flow. Collection does not start while consent is unknown or denied.
4. Send a simple event such as Askdepth.track('integration_check').
5. Inspect the browser's Network panel for the telemetry request and collector response. Allow for batching; check the configured sampling rate and network/CSP restrictions.

Askdepth.isInitialized() confirms active SDK collectors, not server ingestion or dashboard visibility. A successful collector response likewise does not prove downstream processing completed.

See core configuration and consent.

Session replay

Verify that @askdepth/replay is installed, replay is enabled, consent is granted, and the replay upload URL is correct. A replay requires recording to have started before there is context to upload.

Core captures replay on frustration signals; installing it does not continuously stream the whole session. A newly loaded recorder cannot recover DOM history from before it started. See replay behavior and masking limits.

Audience Connector

Run the conformance checks against your deployed connector, then inspect its request logs without recording secrets or contact payloads. Check HTTPS reachability, raw-body signature verification, timestamp handling, cursor behavior, and schema-valid responses.

Do not loosen signing checks to make a test pass. Use the exact raw request bytes and the intended connector secret.

Codex or Claude Code

1. Copy the current add command from the correct workspace's MCP screen.
2. Complete OAuth in the browser using an account that belongs to that workspace.
3. Ask the agent to call get_workspace_context.
4. Refresh the platform screen and check for actual tool use, rather than authorization alone.

For missing tools, expired login, role restrictions, or conflicts, see MCP errors. For hosted execution, follow the separate Claude routine guide.

Report an SDK issue

Include package versions, framework and bundler versions, a minimal reproduction, and sanitized error/status information in an SDK issue. Remove write keys, OAuth tokens, connector secrets, contact data, and private research before sharing logs.