Swetrix
Site settings

Project Configuration & Security

Beyond the basics of tracking, Swetrix offers a robust set of configuration options to secure your data, manage access, and customise your project settings.

To access these settings, go to your Project Settings page. You can learn how to access it here.

General Settings

The General tab allows you to configure the basic identity of your project.

  • Project name: A friendly name for your project (e.g., "My Personal Blog").
  • Website URL: The main URL of the website you are tracking.
  • Project ID: A unique identifier for your project (read-only).

Security (Shields)

The Shields tab provides powerful tools to protect your analytics from spam, bots, and unwanted traffic.

Allowed origins

By default, Swetrix accepts events from any domain. If you want to restrict tracking to specific domains, add the domains that are allowed to send analytics using this Project ID.

  • Separate multiple domains with commas.
  • Requests from domains not listed here will be rejected.
  • Leave the field empty to allow all domains.
  • Wildcards are supported, for example cornell.edu, app.example.com, or *.gov.uk.

Blocked IP addresses

You can ignore traffic from specific IP addresses or CIDR ranges, which is useful for excluding your own visits from analytics.

  • Separate multiple values with commas.
  • Supports IPv4, IPv6, and CIDR ranges, for example 172.126.10.16, 192.168.0.1/32, or ::1.

Blocked countries

Choose the countries you don't want to track. Traffic from these countries will be ignored in your analytics.

  • Select countries from the country dropdown.

Bot traffic filtering

Swetrix has built-in bot detection. You can choose how aggressively bot and automated traffic should be filtered from your analytics:

  • Off: Tracks all incoming traffic, including bots and automated requests.
  • Basic (default): Ignores common bots detected by their user agent and known headless-browser fingerprints.
  • Strict: Ignores more automated traffic, including suspicious headers, vulnerability-scan paths, referrer spam, and (on cloud) datacenter IPs.

Below the dropdown you'll find a per-project Blocked traffic report showing how many requests were filtered out, broken down by classification and country. See the dedicated Bot Protection page for the full list of detection methods, privacy notes, and FAQ.

Session Replays

The Session replays tab controls how long newly recorded replay chunks are retained for the project.

Available retention periods depend on your plan. When you change the retention period, the new value applies only to replay chunks recorded after the change. Existing replay chunks keep the expiry date they were recorded with.

See Session Replays for setup, privacy modes, and playback details.

Access Control

The Access tab manages who can see your dashboard and which organisation the project belongs to.

Visibility Settings

  • Sharable Link: A direct link to your public or password-protected dashboard (read-only).
  • Public dashboard: If enabled, anyone with the link can view your analytics dashboard. No login required.
  • Password protected: If enabled, visitors must enter a password to view the dashboard. Useful for sharing stats with clients without requiring them to create an account.

Organisation Assignment

If you are a member of an Organisation (Team), you can transfer the project to that organisation here. This allows all members of the organisation to access the project according to their roles.

Danger Zone

The Danger Zone contains project status controls and destructive actions. Proceed with caution.

  • Collect analytics data: Turn this off to stop collecting new analytics data. Existing data and project settings stay available.
  • Transfer ownership: Move ownership of the project to another user. See Transfer Ownership for details.
  • Reset project: Delete analytics data while keeping project settings and Project ID. See Reset project data for details.
  • Delete project: Permanently delete the project and all associated data. This action cannot be undone.

On this page