1 item
Filter out your own visits from Umami, datafa.st, Oxidt Analytics, Plausible, and PostHog Stop skewing your own analytics! Internal Traffic Filter excludes your visits from supported analytics services on websites you manage. 🎯 SUPPORTED ANALYTICS • Umami • datafa.st • Oxidt Analytics • Plausible • PostHog* The extension applies each service’s opt-out flags or filters supported PostHog browser events and stops session recording. ✨ FEATURES • Simple “Exclude my visits” switch for the current site • Clear exclusion status and a “Refresh page” button • Manage all excluded sites from one popup • Exclusion settings sync across devices when browser sync is enabled • See today’s page loads with exclusion enabled • Settings apply separately to each subdomain, protocol, and port The daily count stays on your device. It counts page loads with exclusion enabled, not analytics requests blocked. 🔒 PRIVACY FOCUSED • No telemetry, tracking, or extension backend • No browsing history stored for daily statistics • Exclusion settings use browser sync storage and may sync through your browser provider • PostHog filtering preserves the visitor’s existing consent settings • Open source: github.com/hauju/internal-traffic-filter 🛠 HOW TO USE 1. Visit a website you want to exclude from analytics 2. Click the extension icon 3. Turn on “Exclude my visits” 4. Click “Refresh page” when prompted To remove an exclusion, turn off the switch or remove the site from your list, then refresh any open tabs for that site. 💡 PERFECT FOR • Website owners checking their own sites • Developers testing in production • Teams keeping internal visits out of their analytics *PostHog support covers the standard browser snippet and SDK instances exposed as window.posthog before initialization, including named instances and cookieless modes. Hidden bundled SDKs, workers, and server-side tracking are not covered. Feature-flag and SDK configuration requests may continue. Works with Chrome, Brave, Edge, and compatible Chromium browsers based on version 111 or newer.
Nov 2, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.