Filter Internal Users in Amplitude
Use reversible report exclusions when the immediate need is cleaner analysis, and evaluate ingestion blocking as a separate governance decision. Either approach needs verified internal identifiers and a documented effect on historical comparisons.
Before you start: Have reliable internal-account markers and permission for the chosen control. Know whether the goal is excluding reports or stopping collection.
Worked example: Staff regularly test checkout in production. Exclude a verified internal marker from the business report, then inspect a real customer and a staff account to confirm classification.
Step-by-step guide
Define the internal population
List staff, contractors, automated tests and development environments separately. Avoid a broad IP assumption when people work remotely or share networks.
Choose the control layer
Use report filters for analytical exclusion when appropriate. Consider project data filters only when intentionally blocking ingestion is the authorized goal.
Validate identifiers
Check current raw events and user properties. Confirm that the marker is present when the relevant actions occur.
Test included and excluded users
Inspect a known customer, staff account and boundary case. Resolve false positives before changing the recurring report.
Preserve comparison context
Save the pre-change metric and exclusion rule. Recalculate equivalent periods where possible instead of comparing filtered data with an unfiltered baseline.
Document maintenance
Assign an owner for account changes and explain the difference between excluding, hiding and blocking data. Recheck the rule when instrumentation or access patterns change.
Common mistakes
IP rule catches customers
Shared networks can make broad rules misleading.
Blocking used casually
Dropped data may not be available later. Choose the layer deliberately.
Filtered versus unfiltered trend
Measurement changes can imitate performance changes.
Tips
Keep a known customer in the validation set.
Record the change date in recurring reviews.
Review remote and contractor access separately.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.