Scribd
Upload
4 views

Filtering Using Containers and Attributes

Uploaded by

picevih793
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

Filtering Using Containers and Attributes

Uploaded by

picevih793
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Filtering Using Containers and Attributes

Help doc : https://help.salesforce.com/s/articleView?


id=sf.c360_a_container_basics.htm&type=5

Scenario 1 : If you add other related attributes to the container,


they act on the same data row as the container object. The
attribute library displays objects up to five relationships away
from the container. You can include the related attributes of any
of these objects in the container.
Scenario 2 : However, attributes in separate containers have no
relationship to each other and filter your segment separately.

Considering you have 1:n relationship from Profile Table (Individual) to


Engagement Table (Product)
Product has let's say two fields you want to put filters on in the same container
i.e. color & type

EXAMPLE Scenario 1: If you place the attributes “yellow” and


“scarf” in the Order Product container, the query engine uses
AND logic and looks for a customer who purchased a yellow scarf
as a single order product” on the purchase.

Now consider the above example for “yellow” “scarf”. This means the filters
inside the same container would have been (color = “yellow” and type=”scarf”)
and lets say your segment has just this one container and below is your data
set.
Ind Id Product Id Product Product Container
Color Type Condition
1 1 yellow brush False
1 2 red scarf False
2 4 yellow scarf True
3 5 blue scarf False
4 6 yellow towel False
4 7 yellow scarf True
Now your final population(Individuals) as part of the segment result would be
just 2,4. Since these were the only data rows satisfying both the conditions.

EXAMPLE Scenario 2 : If you place the attribute “yellow” in one


container, and the attribute “scarf” in another container and both
the containers are joined by AND, the query engine looks for
customers who purchased any yellow product and purchased a
scarf of any color.

Here in this example there are two containers, Let's say C1 ( color = “yellow” )
and C2 (type = “scarf”) and your segment looks like C1 AND C2. Consider the
same data set as in scenario 1 , we will see what will be the result here and how
it differs from Scenario 1.

Ind Id Product Id Product Product Container Container


Color Type 1 2
1 1 yellow brush True False
1 2 red scarf False True
2 4 yellow scarf True True
3 5 blue scarf False True
4 6 yellow towel True False
4 7 yellow scarf True True
Now,
Individuals satisfying the Container 1 condition will be : 1,2,4
Individuals satisfying the Container 2 condition will be : 1,2,3,4
Individuals satisfying segment criteria C1 AND C2 will be : 1,2,4 (final
population)

Conclusion

Now if you see here, the 1st individual had two different events, one where he
had a “yellow” brush and another where he had a red “scarf”.
In the first scenario, we checked for a single row(event) which would satisfy
“yellow” “scarf” and 1 didn’t have any such event and hence was not part of the
segment result.

But in the second scenario , this individual(1) satisfied both the conditions
separately and since the containers were joined through AND , it finally ended
up in your segment result.

Hence, having filters in the same container and having them in different
containers with the same logical operator means different for related attributes
and your final population might differ. So if you need to have filters applied on
attributes of same related engagement event use setup like scenario(1) and if
you are filter applied on any related related engagement event use setup like
scenario(2)

You might also like