# Browser SDK settings

Change optional browser capture without mistaking a toggle for an installation.


## Capture controls

The project stores separate switches for replay, console logs, page events, and rage-click detection. These optional plugins default to off. The browser SDK requests project configuration after initialization and normally refreshes it every 30 seconds while capture is allowed.

A toggle affects an installed, reachable SDK. It does not add a dependency to the repository, deploy your app, create historical events, or prove installation success.

## Visitor choices win

Replay must also be enabled by your local SDK options. Analytics/replay consent takes precedence over remote switches. If configuration cannot be fetched, the client keeps its last confirmed configuration; a dashboard change is not guaranteed to appear instantly on every offline client.

## Tracking domains

Domain configuration records the requested domain and its connection status. It needs the DNS, HTTPS, and collector routing required by that deployment. Adding a hostname alone does not configure an external DNS account or make a local-only API publicly reachable.

## App type and stack

App type and stack describe the application and its setup guidance. They do not restrict the project to one repository or replace runtime-specific instrumentation.

See [browser SDK](/docs/sdks/browser), [privacy](/docs/features/privacy), and [projects/components](/docs/guides/projects).