UPDATE: I have reached out to the CIJ product team and they have confirmed that this is indeed a bug in RTJ, and that a fix is on its way.
---
Hi!
I am trying to re-create a segment that exists in Outbound Marketing in Real-time Journeys. In my data model I have two tables that relate to each other as depicted below and the second table ("Table 2") has a reference to a contact:
Records of each table can have the values A, B or C. Consider two different contacts. The first contact has a related object of Table2, while the other contact has two related objects of Table2 according to the image below. The various Table1 and Table 2 objects have different values:
I want to create a segment that includes all contacts that are related to a hierarchy of Table1 and Table2-objects with the following values:
It is clear from the image above that only Contact_1 fulfills this requirement. In Outbound Marketing, such as segment can be easily created:
This segment contains the correct number of contacts - 1.
Now, I want to create the segment in Real-time Journey, but I can't find a way of doing so. If I try the setup below, the number of contacts are 2:
This is because the underlying query is the following, which is not what I need:
PROFILE(contact).RELATE(cr512_Table1_Contact_Contact, cr512_table1_2).RELATE(cr512_Table1_Contact_Contact, cr512_testtable1_1, RELATE(cr512_TestTable1_cr512_TestTable1_cr512_Table1, cr512_testtable1_1__1)).FILTER(cr512_testtable1_1__1.cr512_value == 914820000 && (cr512_table1_2.cr512_value == 914820001))
The query above is what you get when you create a segment in OBM like this:
And this is not what I want... I want to create a segment that enforces the condition that both Table1 and Table2 should have certain values and that both the objects having these values should be in the same hiearchy - not different hierarchies.
The above is a simplication and illustration of the kind of OBM segments that many customers are using heavily. How can I re-create these kind of segments in Real-time Journeys?
Thanks!
Rgds,
Andreas
