Recording Settings

Summary

The Recording Settings page lets you control which sessions LogRocket records for a project. You can use it to:

• Pause recording: Stop recording new sessions for a project entirely.
• Limit how many sessions are recorded: Cap a project's sessions per quota period or per day.
• Record by location: Allow or block sessions from specific continents, countries, and states or regions.
• Block IPs: Block sessions from specific IP addresses or CIDR ranges.
• Block app versions: Block sessions from specific releases of your app.
• Block user agents: Block sessions from bots and other automated traffic, identified by user agent.

Sessions blocked by these settings aren't recorded and don't count toward your session quota. This makes them a good way to avoid spending quota on traffic you don't care about (e.g., bots, internal testing, or regions you don't serve).

You can find the page in the LogRocket dashboard under Settings > Recording Settings, or go to it directly. Settings apply to the project you currently have selected. Only users with the Admin role can access this page.

Pause Recording and Session Limits

• Pause Recording: Turn this on to stop recording new sessions for the project. Turn it off to resume recording.
• Quota Session Limit: Limit the number of sessions recorded for the project during the current quota period. This uses the same window as your plan's session allowance. Session quota is shared by all projects in your organization, so this is useful for keeping one project from using up quota that the rest of your projects need. See Impose Session Limit for more information.
• Daily Session Limit: Limit the number of sessions recorded for the project per day. The daily count resets at midnight UTC, and recording typically resumes within about 30 minutes afterward.

Once a project reaches either limit, LogRocket stops recording new sessions for it until the limit resets.

Record By Location

Use this section to allow or block sessions based on where they come from. LogRocket determines a session's location from its IP address.

First, choose whether you want to use an Allowlist or a Blocklist:

• Allowlist: Only record sessions that match a value in every field you fill in.
• Blocklist: Don't record sessions that match a value in any field you fill in.

Then, fill in one or more of the following fields. Fields you leave empty are ignored.

• Continent: Select one or more continents from the list.
• Country: Select one or more countries from the list. U.S. territories (e.g., Puerto Rico, Guam) are listed here as countries, not as states.
• State/Region: Select one or more U.S. states, or type the name of a state, province, or region from another country (e.g., England, Ontario) and select + Add. Regions are matched by their English name, ignoring case.

For example:

• To record only sessions from the U.S. and Canada, select United States and Canada under Country and leave the other fields empty.
• An allowlist with Europe under Continent and United States under Country won't record anything, because no session can be in both places.
• An allowlist with California under State/Region won't record sessions from anywhere other than California, including sessions from outside the U.S.

Block IPs

Use this section to specify IPv4 addresses, IPv6 addresses, or CIDR ranges you want to block sessions from (e.g., 203.0.113.7, 2001:db8::1, 10.0.0.0/8, 2001:db8::/32). This is useful for excluding traffic from your office or VPN. LogRocket ignores entries that aren't valid IP addresses or CIDR ranges.

Block App Versions

Use this section to specify app versions you want to block sessions from (e.g., 0.1.0, 0.2.1, ed6285c81f). Versions must match exactly. A session's app version comes from:

• Web sessions: The release value you pass to LogRocket.init.
• Android sessions: The PackageInfo.versionName field, captured automatically.
• iOS sessions: The CFBundleShortVersionString field, captured automatically by SDK version 1.6.0 or newer.

If you use Expo Update ID tracking, the update ID is appended to the release, so the app version changes with every Expo update.

Block User Agents

Use this section to stop recording web sessions from bots and other automated traffic that can be identified by user agent.

NOTE: Google crawlers (e.g., Googlebot, AdsBot-Google) are never recorded, regardless of these settings.

Block Well-Known Bots

Turn on Block well-known bots to stop recording sessions from automated traffic that identifies itself in its user agent. This includes search engine crawlers, AI agents, link previewers, uptime monitors, headless browsers, and test runners. Detection matches against public lists of named, well-known bots and also uses generic patterns (e.g., a standalone "bot" token; a URL in the user agent).

This is off by default. If you record automated traffic on purpose, such as end-to-end tests (e.g., Cypress, Playwright) or synthetic monitors (e.g., Datadog Synthetics, Lighthouse), turning it on will stop recording that traffic, too. Use Test a User Agent to check if a given user agent would be blocked.

Custom User Agents

Specify custom user agents to block traffic that Block well-known bots doesn't catch, like an internal crawler or monitoring tool. You can also use them to block only specific bots instead of turning on Block well-known bots (e.g., to block Amazonbot but keep recording your Playwright tests). Enter part of a user agent (e.g., MyInternalCrawler) and select Add User Agent. LogRocket blocks any session whose user agent contains it, ignoring case.

Test a User Agent

Paste a full user agent into Test a user agent to see whether sessions from it would be blocked and why. For example, it'll tell you if a user agent is a well-known bot that would be blocked if you turned on Block well-known bots, or if a custom user agent you've added isn't needed because Block well-known bots already blocks it.