# Control what Relia collects (SDK settings)

> Pause Relia, record fewer sessions, ignore pages and routes, and leave out button text, page speed or replays, without a new deploy.

Section: Settings and safety · Page: https://tryrelia.com/docs/sdk-settings · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/eTS5T0wgMdQ

SDK settings let you change what Relia's SDKs collect from your apps, from the Relia app, with no code change and no new deploy. They can only collect **less** than your code allows, never more. They never delete anything already stored, and you can switch any of them back.

## Before you start

- You are an owner or admin of the project. Others can see the settings but not change them.

## Open the settings

Click **Settings** in the sidebar, then the **Advanced** tab, then **SDK settings**.

Changes reach your browser, Node.js and Python apps within about 10 minutes.

## The settings

| Setting | What it does | Default |
|---|---|---|
| **Monitoring** | Off pauses Relia for the whole project: every browser, Node.js and Python app of this project stops sending. Nothing already stored is touched. Switch it back on to carry on. | On |
| **Button and link text** | Off records clicks without the words on the button or link. | On (text is still only recorded if your code sets `captureText: true`; Relia's setup writes `false`) |
| **Page speed** | Off sends no web vitals from the browser. | On |
| **Screen replays** | Off records no replays, even where your app's code turned them on. | On (replays still only happen if your code asks for them) |
| **Sessions recorded** | The share of browser sessions kept, 1 to 100 %. At 50, about half. | 100 |
| **Pages and routes to ignore** | Pages (browser) and incoming routes (server) that are never recorded. One per line, up to 30. | none |

Switches save as soon as you flip them. For **Sessions recorded** and **Pages and routes to ignore**, click **Save**; you'll see "Saved. SDKs pick it up within 10 minutes."

### Sessions recorded

Which sessions are kept is decided per session, so a visitor's reload stays in or out together. Errors in skipped sessions are not seen, so stay at 100 unless you need to record less.

### Pages and routes to ignore

Write paths, each starting with `/`:

```text
/health
/admin/*
/orders/*/receipt
```

- `/admin/*` ignores everything below `/admin`.
- `*` in the middle matches any one part of the path.
- No spaces, no query strings (`?…`).

## Which apps follow which setting

| App | Follows |
|---|---|
| Web app (browser SDK) | Every setting |
| Node.js and Python servers | **Monitoring** and **Pages and routes to ignore** only |
| PHP / Laravel and OpenTelemetry apps | None of these settings |

An app checks for new settings about every 10 minutes. To stop the server fetch entirely in an app, set `RELIA_REMOTE_SETTINGS=0`.

> **Tip:** watch [Privacy in Relia: what is recorded and what never is](https://youtu.be/G-WlncnUWeY) (2 min).

## Check it worked

Wait about 10 minutes, then use your app. With **Monitoring** off, nothing new arrives on the project's **Setup** tab. With a page ignored, it stops showing new visits on **Visitors** and **Sessions**; with a route ignored, new requests to it stop appearing on **Requests**.

## If something's wrong

- **A change didn't apply after 10 minutes**: the app may run an older SDK. Update to the latest `relia-sdk` and redeploy once.
- **A PHP app still sends**: PHP doesn't read these settings. Remove or change its setup in the app.
- **"Not a path"**: each line must start with `/` and have no spaces or `?`.

## Next

- [Privacy](https://tryrelia.com/docs/privacy.md)
- [Plans and limits](https://tryrelia.com/docs/plans-and-limits.md)
- [Environment variables](https://tryrelia.com/docs/environment-variables.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
