Skip to main content
Solved

Regarding user filters in Cohorts


Forum|alt.badge.img

Hello,

There are some set of common user filters like removing users from within the organization or removing test users that we use for most of the charts our organization creates on Amplitude. Is it a good practice to add these filters in cohort itself ? Or should these common filters be applied in the cohort condition as well as the chart using the respective cohort ?

Thanks!

Best answer by JennRu

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”
View original
Did this topic help you find an answer to your question?

4 replies

dangrainger
Expert
Forum|alt.badge.img+9

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


Forum|alt.badge.img

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 ?


dangrainger
Expert
Forum|alt.badge.img+9

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.


JennRu
Community Manager
Forum|alt.badge.img+9
  • Community Manager
  • 75 replies
  • Answer
  • June 16, 2023

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”

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings