Meta tags:
description=Exclude traffic by IP address, country, path, hostname, or user agent;
author=Rybbit Team;
keywords=web analytics,privacy analytics,open source analytics,Google Analytics alternative,website tracking,self-hosted analytics;

Headings (most frequently used words):

exclusions, filters, filter, traffic, available, ip, country, path, hostname, user, agent, what, apply, to, how, are, evaluated, testing, locally, on, this, page,

Text of the page (most frequently used words):
#exclusions (22), traffic (19), the (17), and (15), your (13), filters (12), #country (11), for (11), rybbit (10), path (9), user (8), agent (8), hostname (8), matches (7), are (6), from (6), analytics (6), own (6), site (6), filter (6), not (6), matching (6), case (6), insensitive (6), preview (6), admin (6), settings (6), this (5), server (5), events (5), use (5), internal (5), exclude (5), app (5), 192 (5), 168 (5), entries (5), apply (4), test (4), localhost (4), data (4), vercel (4), staging (4), specific (4), pages (4), ranges (4), 100 (4), guides (4), locally (3), how (3), bot (3), hiding (3), event (3), configured (3), pathname (3), filtering (3), any (3), with (3), but (3), address (3), checks (3), tools (3), substring (3), headlesschrome (3), examples (3), patterns (3), such (3), users (3), using (3), exclusion (3), private (3), addresses (3), codes (3), ipv4 (3), single (3), self (3), documentation (3), testing (2), evaluated (2), what (2), available (2), page (2), detection (2), tracked (2), values (2), that (2), should (2), match (2), example (2), com (2), type (2), pageview (2), real (2), track (2), response (2), usually (2), because (2), session (2), replay (2), autocapture (2), custom (2), stored (2), they (2), crawlers (2), other (2), wildcard (2), sequence (2), characters (2), when (2), local (2), environments (2), side (2), only (2), you (2), can (2), also (2), tracking (2), script (2), level (2), all (2), routes (2), vpns (2), proxies (2), vpn (2), proxy (2), location (2), cannot (2), geolocated (2), ips (2), api (2), united (2), two (2), letter (2), iso (2), block (2), countries (2), setup (2), best (2), 2001 (2), db8 (2), cidr (2), monitoring (2), glob (2), domains (2), hosting (2), troubleshooting (2), feature (2), 687 (2), github (2), identifies, prevent, visits, being, set, payload, site_id, content, application, json, http, 3000, post, curl, send, public, through, header, accepted, changes, take, effect, within, seconds, configuration, cached, briefly, 200, order, batches, error, performance, web, vitals, pageviews, run, before, normal, uptime, monitors, synthetic, predictable, strings, uses, mozilla, 120, pingdom, mymonitor, requests, whose, contains, netlify, hostnames, useful, same, used, across, production, client, skipping, option, enforced, ingestion, skip, appear, dashboards, previews, paths, query, string, visitors, detected, based, their, physical, work, includes, docker, container, during, development, 172, 127, uppercase, dashboard, germany, china, kingdom, states, resolves, visitor, maxmind, geolite2, database, then, compares, resulting, code, list, instructions, practices, see, notation, ipv6, supported, formats, way, hide, request, returns, successful, does, write, storage, headless, browsers, deployments, temporary, 250, regional, compliance, requirements, home, office, network, limit, behavior, provides, keep, unwanted, out, entire, open, copy, markdown, definitions, import, inviting, billing, teams, organization, account, migration, managing, installation, quick, start, embeds, funnels, goals, sdks, guide, integration, tagging, identify, usage, hosted, cloud, architecture, comparison, introduction, reference, search,

Text of the page (random words):
filter traffic rybbit search k github rybbit io rybbit 12 4k 687 documentation api reference documentation guides setup and feature documentation github rybbit io rybbit 12 4k 687 introduction comparison architecture self hosted vs cloud usage tracking script troubleshooting track events autocapture identify users tagging integration guides proxy guide sdks hiding your own traffic filter traffic bot detection goals funnels embeds feature guides self hosting quick start managing your installation troubleshooting self hosting guides migration to v1 0 settings account settings organization settings teams billing inviting users site settings data import other definitions filter traffic filter traffic exclude traffic by ip address country path hostname or user agent copy markdown open rybbit provides server side traffic filtering to keep unwanted data out of your analytics you can exclude your own traffic staging and preview environments internal tools monitoring checks or entire countries filters are configured from site settings exclusions available filters filter use it for matching behavior limit ip exclusions your home office vpn or internal network traffic single ips cidr ranges and ipv4 ranges 100 entries country exclusions regional filtering or compliance requirements two letter iso country codes such as us gb or de 250 entries path exclusions admin pages private pages preview routes or test pages case insensitive glob patterns using 100 entries hostname exclusions localhost staging domains preview deployments or temporary domains case insensitive glob patterns using 100 entries user agent exclusions monitoring tools headless browsers or custom crawlers case insensitive substring matching 100 entries when a request matches an exclusion rybbit returns a successful response but does not write the event to analytics storage ip exclusions block traffic from specific ip addresses or ranges at the server level this is usually the best way to hide your own traffic supported formats single ipv4 192 168 1 1 single ipv6 2001 db8 1 cidr notation 192 168 1 0 24 2001 db8 32 ipv4 ranges 192 168 1 1 192 168 1 10 for setup instructions and best practices see hiding your own traffic country exclusions block all traffic geolocated to specific countries rybbit resolves the visitor ip address with the maxmind geolite2 database then compares the resulting country code to your exclusion list use two letter iso country codes us for united states gb for united kingdom cn for china de for germany country codes are stored as uppercase values in the dashboard and api private ip addresses country exclusion cannot work for private ip addresses such as 127 0 0 1 192 168 x x 10 x x x or 172 16 x x because they cannot be geolocated this includes localhost and docker container ips during local development vpns and proxies visitors using vpns or proxies are detected based on the vpn or proxy server location not their physical location path exclusions exclude traffic to specific page paths path exclusions match the pathname only not the query string examples admin preview internal matching is case insensitive a wildcard matches any sequence of characters so admin matches admin users and admin settings use path exclusions for pages that should not appear in analytics at all such as admin dashboards internal previews or test routes for client side only pageview skipping you can also use the tracking script s data skip patterns option site level path exclusions are enforced on the server and also apply to session replay ingestion hostname exclusions exclude traffic from specific hostnames this is useful when the same site id is used across production staging preview and local environments examples localhost staging example com vercel app netlify app matching is case insensitive a wildcard matches any sequence of characters so vercel app matches my preview vercel app but not vercel app user agent exclusions exclude traffic from requests whose user agent contains a configured substring examples headlesschrome mymonitor pingdom matching is case insensitive and uses substring matching so headlesschrome matches mozilla 5 0 headlesschrome 120 use user agent exclusions for uptime monitors synthetic checks internal crawlers or other tools with predictable user agent strings what filters apply to traffic filters run before normal analytics data is stored they apply to pageviews custom events performance and web vitals events error events autocapture events session replay batches how filters are evaluated rybbit checks exclusions in this order ip address country path hostname user agent if any filter matches the event is accepted with a 200 response but is not tracked changes usually take effect within 60 seconds because site configuration is cached briefly on the server testing filters locally to test country filtering locally send a public ip through the x real ip header curl x post http localhost 3000 track h content type application json h x real ip 8 8 8 8 d type pageview site_id your site id hostname example com pathname test for path and hostname filters set pathname and hostname in the event payload to values that should match your configured exclusions hiding your own traffic prevent your own visits from being tracked in analytics bot detection how rybbit identifies and filters bot traffic from your analytics on this page available filters ip exclusions country exclusions path exclusions hostname exclusions user agent exclusions what filters apply to how filters are evaluated testing filters locally