IP address blocking
Exclude an exact IPv4 or IPv6 address, such as an office connection or development machine. IP rules do not support CIDR ranges or wildcards. Up to 30 IP rules per site.
Appearance
ProductGuards & ExclusionsEvery feature on every plan.
Control exactly what traffic gets tracked
Exclude exact IP addresses, countries or page paths, and allow listed hostnames. Wildcards apply to page and hostname patterns. Rules filter incoming events without deleting existing history.
Illustrative rules for studio.example
A closer look at the platform.Sample data
4Rule types
30Rules per type
WildcardsPattern matching
IncomingEvents checked
Capabilities
Keep your analytics focused.
Country exclusion
Block traffic from specific countries by 2-letter ISO code. Useful for excluding regions with high bot traffic or focusing analytics on target markets. Searchable country dropdown with flags.
Page path exclusion
Exclude specific pages or entire sections from tracking. Supports wildcard patterns, /admin/* blocks all admin pages, /test/* blocks all test pages. Up to 30 page rules per site.
Hostname allowlist
Once you add any hostname rule, OpenMetrica switches to allowlist mode, only traffic from listed hostnames is tracked. Everything else is silently dropped. Essential for filtering out staging, preview, and development environments.
Wildcard pattern matching
Page and hostname rules support wildcard patterns using the * character. Put the * at the start, at the end, or at both ends of a pattern to match what a path or hostname ends with, starts with, or contains. Rules are case-sensitive for paths and case-insensitive for hostnames.
Checked as events arrive
Rules are checked during ingestion and cached for up to five minutes. Adding, editing or deleting a rule invalidates the cache. Rules affect future events and do not rewrite stored reports.
A closer look
Choose what belongs in your reports.
Internal traffic
Stop counting your own visits
Add your office IP addresses to the exclusion list and your team's visits will no longer inflate your analytics. This is the single most common use case for guards, clean data starts with excluding known internal traffic.
Staging environments
Keep staging and preview traffic out of production analytics
If your staging site shares the same tracking code, use hostname rules to allowlist only your production domain. Traffic from staging.yourdomain.com, preview.yourdomain.com, or localhost will be silently excluded.
Geographic filtering
Focus on your target markets
Exclude countries with high bot traffic or irrelevant audiences. Country rules use the same country-level GeoIP database used for visitor location, 2-letter ISO codes with instant matching at the ingestion layer.
The details
Frequently asked questions
Answers before you get started.
How many exclusion rules can I create?
Up to 30 rules per type, 30 IP rules, 30 country rules, 30 page rules, and 30 hostname rules. That is 120 total rules per site.
How quickly do rule changes take effect?
Saving a rule invalidates the shared rule cache. Cached rules have a five-minute expiry. Changes affect incoming events only, rather than removing already recorded traffic.
What happens when I add a hostname rule?
OpenMetrica switches to allowlist mode for hostnames. Only traffic from hostnames that match your rules will be tracked. All other hostnames are excluded. This is different from IP, country, and page rules, which use blocklist mode.
Do excluded events count against my pageview limit?
No. Events excluded by guards are dropped at the ingestion layer before they are counted. They do not consume your monthly pageview or event quota.
Get started
Clean up your analytics data
Block internal traffic and staging environments in minutes. No credit card required.