This is actually a bug, but I was encouraged by support to report it as an idea.

The error applies to real-time marketing segment builder, where the use of several segments with the combination "and also" as criteria elements gives the wrong number of contacts. The same applies if you have a table with a criteria and a related table with a criteria.

E.g. we have a case where we want to find all students who are on a course. In Outbound segment builder the query is as follows and returns 85 students, which is the correct number

PROFILE(opportunity, opportunity_1) .RELATE(opportunity_pp_studyprogramperiod_pp_studyprogram_edition, pp_studyprogramperiod_1) .FILTER(opportunity_1.pp_bcstatus == 292460000 && pp_studyprogramperiod_1.pp_fsclasscode == 'MH23MSRHO1') .TRAVERSE(opportunity_contact_customerid, contact_1)

In real-time the query looks like this and returns 154 students as the pp_bcstatus is not considered.

PROFILE(contact).RELATE(opportunity_customer_contacts, pp_studyprogramperiod_2, RELATE(pp_opportunity_studyprogram_edition_pp_study, pp_studyprogramperiod_2__1)).RELATE(opportunity_customer_contacts, opportunity_1).FILTER(opportunity_1.pp_bcstatus == 292460000 && pp_studyprogramperiod_2__1.pp_fsclasscode == 'MH23MSRHO1')

There are several ways to build this segment, but they all returns the wrong result. For example, if we combine two segments, like this

PROFILE(contact).RELATE(opportunity_customer_contacts, opportunity_1).FILTER(opportunity_1.pp_bcstatus == 292460000) INTERSECT PROFILE(contact).RELATE(opportunity_customer_contacts, pp_studyprogramperiod_1, RELATE(pp_opportunity_studyprogram_edition_pp_study, pp_studyprogramperiod_1__1)).FILTER(pp_studyprogramperiod_1) 1__1.pp_fsclasscode == 'MH23MSRHO1 ')

The result is still wrong, it returns 154 students instead of 85.

I would say this is a critical error!

TrackingID#2309220050002468