Installation security
Control where your tracking script is accepted, exclude internal traffic, and keep dynamic URLs readable.
Allowed hostnames
Allowed hostnames restrict which domains can send events for a project. This helps prevent a copied script tag from polluting your analytics.
examples
example.comwww.example.comapp.example.com*.example.comexample.comwww.example.comapp.example.com*.example.comexample.comhostname
Allow exactly the root domain.
app.example.comhostname
Allow one specific subdomain.
*.example.comwildcard
Allow all subdomains under the root domain.
ℹ
Manage allowed hostnames from
Project settings -> Security.Blocked IPs
Use blocked IPs to exclude internal traffic, QA devices, office networks, or noisy monitors from your reports.
examples
203.0.113.10198.51.100.0/24203.0.113.10198.51.100.0/24Blocked pages
Blocked pages prevent specific paths from being tracked. This is useful for admin areas, previews, or routes that should not appear in analytics.
examples
/admin/dashboard/*/preview/*/admin/dashboard/*/preview/*Masked pages
Masked pages group dynamic paths into readable patterns so reports do not fill up with unique IDs.
examples
/orders/*/users/*/projects/*/settings/orders/*/users/*/projects/*/settings✦
Masking keeps pages like
/orders/123 and /orders/456 grouped as one report row.