List var not segementing correctly. Does not work with hit container exclusion but works with visit container exclusion? | Community
Skip to main content
O
Olso6744
May 31, 2024
Question

List var not segementing correctly. Does not work with hit container exclusion but works with visit container exclusion?

  • May 31, 2024
  • 2 replies
  • 797 views

Hi all, 

So when I try to make a segment for when in our visit a certain line of business has their visit they receive the Old Homepage experience. We have an impression call firing when New Homepage experience is served.

So I made a Visit level segment to look at visits that had my LOB and did not include a Hit for New Home.

 

But that doesn't work as I still see visits with l2 = new home attributing to that segment.

 

If I change the segment so that it is excluding new home on a visit level it works.

 

But I don't understand why the Hit level exclusion isn't working but the visit is. Shouldn't the Visit segment with the hit exclusion exclude any visit in which that Hit is present?

 

Thanks!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 31, 2024

    Hi,

     

    This is a tricky one... you are correct that the HIT exclusion should work, but I think something to do with the nature of being a list (and having multiple values for the same hit) might be causing some issues with the exclusion logic...

     

    I tested with some proxy data in my implementation, and I saw that some data is excluded, most of it is coming through. 

     

    I suspect my hits that have only one list item of "x" are being excluded, but if I have both "x" and "y" then they are not? I don't have direct access to our raw data, but this is my working theory at this time.

      Ankit_Chaudhary
      Community Advisor
      Ankit_ChaudharyCommunity Advisor
      Community Advisor
      June 1, 2024

      I think instead of equals you should try a contains logic maybe that would work with the hit segment.

        O
        Olso6744Author
        June 3, 2024

        Unfortunately does not work. 

         

         

        Jennifer_Dungan
        Community Advisor and Adobe Champion
        Jennifer_DunganCommunity Advisor and Adobe Champion
        Community Advisor and Adobe Champion
        June 3, 2024

        Yeah, unfortunately when it comes to list items, the criteria is run against each item after it's been split... so in this case equals or contains would work the same

         

        Basically let's say you pass the following into a list:

        "value,something,other"

         

        These will be split to be "value", "something" and "other"; so whether you look for equals "value" or contains "value" the result will be the same....

         

        Now, if you had:

        "value,something,other,another value"

        "something,other,another value"

         

        Then equals "value" will only return the items that specifically have "value" (i.e. the first option only), whereas if you have contains "value", both the above would meet the criteria.

        Terms & ConditionsAccessibility statement

        Loading footer...