Site settings

Configure your site settings including privacy options, analytics features, traffic filtering, and more

Open your site's dashboard and click Site Settings at the bottom of the sidebar.

site settings

Settings are split into tabs: General, Tracking, Exclusions, Integrations (Cloud), Tracking Script, Widget Embeds, Dashboard Embed, Import and Usage.

General

Site Name and Domain

Site Name is the display name for the site. Domain is the domain used for tracking. Click Update next to either to save it. Changing the domain doesn't affect existing data; all historical analytics are kept.

Privacy & Security

Public Analytics

Make your analytics publicly accessible by enabling the "Public Analytics" toggle.

  • External viewers have read-only access to your analytics data
  • Viewers cannot edit settings, reports, funnels, or goals
  • Your other websites are not affected

User ID Salting

Rybbit stores user IDs as a hashed combination of IP + user agent. This allows identifying users across sessions, but may be considered storing personally identifiable data under GDPR.

Enable "User ID Salting" to have Rybbit forget about unique users every day. If a user visits 10 times in one day, they count as one user with 10 sessions. But if they visit once a day for 10 days, they appear as a new user each day.

Downsides of enabling user ID salting:

  • User session history beyond 24 hours is not available
  • Unique user counts over periods longer than 24 hours will be inflated
  • The user retention page becomes effectively useless

Block Bot Traffic

Enable "Block Bot Traffic" to prevent detected bot traffic from being tracked in your normal analytics. See Bot detection for how Rybbit identifies and stores bot traffic.

First-Party Proxy

Turn on First-Party Proxy if tracking requests reach Rybbit through your own proxy or CDN (for example a Cloudflare Worker, CloudFront or nginx). Rybbit then always reads visitor IPs from forwarded headers. Leave it off if the script talks to Rybbit directly. Without Cloudflare in front, as on most self-hosted installations, Rybbit reads forwarded headers either way, so the setting has no effect. See the proxy guide.

Track IP Address

Enable "Track IP Address" to store the IP address of visitors.

This is not GDPR compliant. Only enable if you have a legitimate need and proper consent mechanisms in place.

Tracking

Analytics Features

Session Replay (Pro)

Record and replay user sessions to understand user behavior. This feature allows you to see exactly how users interact with your site.

Web Vitals (Cloud, Standard)

Track Core Web Vitals metrics including:

  • LCP (Largest Contentful Paint)
  • CLS (Cumulative Layout Shift)
  • INP (Interaction to Next Paint)
  • FCP (First Contentful Paint)
  • TTFB (Time to First Byte)

SPA Navigation

Automatically track navigation in single-page applications (SPAs). Enabled by default. This detects URL changes via the History API and tracks them as page views.

URL Parameters

Include query string parameters in page tracking. Enabled by default. Disable if you want cleaner URLs in your analytics or need to exclude sensitive parameters.

Track URL fragments

Keep fragments such as #shipping in page paths, so checkout stages or tabs are tracked as separate pages. Off by default.

Initial Page View

Automatically track the first page view when the tracking script loads. Enabled by default.

Auto Capture

Track when users click on external links leaving your site. Enabled by default.

Error Tracking (Standard)

Capture JavaScript errors and exceptions from your site to identify and fix issues affecting your users.

Button Clicks (Standard)

Automatically track clicks on all buttons.

Copy Events (Standard)

Track when users copy text from your site.

Form Interactions (Standard)

Automatically track form submissions and input and select changes.

See Autocapture for what each of these records.

Exclusions

IP Exclusions

Block specific IP addresses or ranges from being tracked. Supports:

  • Individual IP addresses (e.g., 192.168.1.1)
  • CIDR notation (e.g., 192.168.1.0/24)
  • IPv4 ranges (e.g., 192.168.1.1-192.168.1.255)

Country Exclusions

Block all traffic from specific countries using ISO country codes (e.g., US, DE, FR).

ASN Exclusions

Exclude traffic from specific networks by autonomous system number, such as a corporate VPN or hosting provider. Enter the number with or without the AS prefix (e.g., AS13335 or 13335). Up to 100 ASN exclusions are allowed.

Path Exclusions

Exclude traffic to specific pages. Use * as a wildcard (e.g., /admin/* or /preview). Matching is case-insensitive. Up to 100 path exclusions are allowed.

Query Param Exclusions

Exclude traffic to URLs containing specific query parameters. Use a parameter name alone (e.g., preview) to match whenever it's present, or name=value (e.g., utm_source=internal) to match a specific value. Values support * as a wildcard, and matching is case-insensitive. Up to 100 query param exclusions are allowed.

Query param exclusions need URL Parameters turned on in the Tracking tab. With it off, events are sent without their query string and these exclusions can't match.

Hostname Exclusions

Exclude traffic from specific hostnames such as staging or preview domains. Use * as a wildcard (e.g., localhost or *.vercel.app). Matching is case-insensitive. Up to 100 hostname exclusions are allowed.

User Agent Exclusions

Exclude traffic from user agents containing any of these terms. Matching is a case-insensitive substring (e.g., HeadlessChrome). Up to 100 user agent exclusions are allowed.

All of these exclusions work at the server level, ensuring blocked traffic never reaches your analytics database.

Tracking Script

The Tracking Script tab shows the snippet to add to the <head> of your website, with an AI agent tab holding a prompt you can paste into a coding agent. Under Options you can set Skip Patterns (URLs to exclude from tracking), Mask Patterns (URLs to anonymize, e.g. /users/*/profile) and the Debounce Duration (ms) before a pageview is tracked after a URL change. See Tracking script for every option.

Embeds

Show Rybbit data on another site with an embeddable iframe.

  • Widget Embeds show a compact live visitor widget. Enable them from the Widget Embeds tab. This is independent of Public Analytics and only exposes the data the widget displays. See the Widget Embeds guide for details.
  • Dashboard Embed shows the analytics dashboard in an iframe. Configure it from the Dashboard Embed tab. It uses a generated private link, not Public Analytics. See the Dashboard Embed guide for details.

Integrations (Cloud)

Google Search Console

Connect your Google Search Console account to see search performance data alongside your analytics.

Import

Import historical data from another analytics tool. See Data import.

Usage

The Usage tab shows this site's events for the current calendar month, its share of your organization's events, the organization's event limit, a projection to month end, and a Daily Events chart. Usage resets at the start of each calendar month. See Billing for what counts.

Moving a site

Admins and owners can move a site to another organization from the General tab. Its analytics data, goals, funnels, dashboards, segments, annotations and settings go with it, and the tracking script keeps working unchanged. Site access granted in the old organization (restricted-member grants and team assignments) is reset.

Move to Organization

To move a site to another organization you manage, pick the organization under Move to Organization, click Move and confirm with Yes, move site. You need to be an admin or owner of both organizations.

Transfer to someone else

Enter the recipient's email under Transfer to someone else and click Send transfer. They get an email with a link (you can also use Copy link and send it yourself); they open it signed in with that address (on Rybbit Cloud it must be verified; the page offers to send the verification email), choose one of their organizations, and accept. The link is valid for 7 days, and you can Cancel transfer until it's accepted. Neither of you needs to join the other's organization.

When someone else accepts a transfer, the site's Google Search Console connection is removed, since it uses the sender's Google account; the new owner can connect their own. On Rybbit Cloud the receiving organization's plan must have room for another site.

Delete Site

Permanently delete a site and all associated data from the Danger Zone at the bottom of the General tab. Only admins and owners can delete sites. Click Delete Site, then press and hold Hold to delete site to confirm.

This action cannot be undone. All analytics data, reports, funnels, and goals will be permanently deleted.

On this page