Reporting - Add "and/or" Filter Options | Community
Skip to main content
Submitted

Reporting - Add "and/or" Filter Options

Related products:Reporting
  • Nov 15, 2024 8:08 PM UTC
  • 4 replies
  • 58 views

Angel Horowitz
Forum|alt.badge.img+2

Problem to Solve:
Everywhere else (workflows, proactive support, etc) gives the option to filter with both “and/or” statements vs. just “and”. It makes it extremely difficult to filter the reports to the specific information we need, especially when we’re working with a number of products within one workspace. 

 

Request:
Add the option for “and/or” filtering to both the main report/dashboard, as well as the individual charts, and also the Intercom pre-made reports. 

 

Examples:

Automations / Workflows:

 

Segments:

 

Proactive Support:

 

4 replies

Jennifer K
Intercom Team
Forum|alt.badge.img+3
  • Intercom Team
  • Nov 20, 2024 10:15 AM UTC

Hi ​@Angel Horowitz 

Jennifer here from Intercom 😊

Thanks for this suggestion, I will pass it on to our Product Team for you

Whenever we do release new features, we announce them on the Product Changes page, so I would recommend keeping an eye there too
 


Been also posted here: 

Complete joke this extremely basic feature is not available in the REPORT tool but in other parts of the product. Right now it's either all AND or all OR. Forcing to export data and build reports in Excel/sheets.


  • New Participant
  • Feb 24, 2026 5:09 PM UTC

This needs to be addressed, I agree ​@Marcelo Novaes . It completely throws off logic and forget about setting any report wide filters with an OR logic and metric level filters with AND or vice versa. It changes the logic in the drill to be one or the other, which in most cases makes the filters contradict one another and leaving the data inaccurate or nothing to populate at all. 

 

While in some cases it does not pose any kind of issue, there are so many instances where reporting becomes limited due to the lack of flexibility in logic. 


I upvote this idea. In Inbox views, one operator (Match all or Match any) applies to every filter in the list, and a different operator per line would be a step in the right direction.

That said, it would still fall short of what many views need, which is grouping conditions. For example, a view that must show items matching A, or items matching B and C together, cannot be written as a flat list, even with a different operator per line. The same applies to “A and B, but not C” when A and B must be evaluated together first