Hi @srushti.wadekar. How are you identifying your colleague traffic? You could likely use Drop or Block filters. The former ignores specific data at query time….the latter prevents the data from being ingested into your Amplitude project at all.

https://help.amplitude.com/hc/en-us/articles/5078869299099-Filter-events-with-block-filters-and-drop-filters

Hello, thank you for the response. I’m identifying colleague traffic using email domain.

What is the good practice to apply these user filters if they are common in 90% of charts and dashboards ?

Personally I’d split into multiple Amplitude projects. One for “live” data which is clean and excludes things like bots, staff traffic, etc. Then a second for “dev” data which is for dev sites/ apps, staff traffic, etc.

Adding an alternative suggestion here, if you still wish to keep the data altogether in 1 project

In order to bulk remove these test users from customer-level analyses, you can take 2 approaches. 

• create a saved segment and consider setting it as your default and marking it as official to encourage others to use it as well, or just label it really well so it’s easy for others to find e.g. OFFICIAL] Exclude test users
  • internally at Amplitude, we have a few saved segment that by default removes amplitude employee emails from our customer analyses
  • the benefit of this is if you and your teammates set this as the default segment, it’ll show up on every new chart you start building without having to re-add the same filters all over again
  • you can have a “saved segment” that references a cohort
• create a discoverable cohort that removes employees + test emails with a clear cohort title
  • and then for every new cohort you create, add the condition “and part of cohort Exclude test users”