Listed item out of segment - Adobe Workspace | Community
Skip to main content
H
H_L
Level 7
April 26, 2021
Solved

Listed item out of segment - Adobe Workspace

  • April 26, 2021
  • 5 replies
  • 2001 views

It's found in the workspace table, after a segment is applied, the listed result contains lots of items out of the segment.

For example, a segment to Page URL has been applied that the report needs to include URLs contains /troubleshooting

 

But in the table listed, there are a lot of result the URL does not contain /troubleshooting (red highlighted)

 

*I used a filter to short the result, want to list "does not contain", but in above list, you still can see some result contains /troubleshooting

 

Seems the result lists items not in segment, and, the filter in table also does not work?

Please help to clarify.

 

By the way, if a URL is in (Low-traffic) in workspace displayed, when I set segment "URL contains", will it get data from very backend, or only workspace displayed data? - which mean all (low-traffic) will not be counted, have to use Data Warehouse to get the full result?

 

Thanks in advance.

H

 

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

    Can you try to create a segment with the Instance attribution model as shown in the screenshot below and share a screenshot with full URLs returned in the table if that does not help?

     

    Also can you confirm that the Page URL dimension and the Page URL Instances metric in your table are linked to the same eVar (as sometimes there are various variables with the same name)?

     

     
    The urls grouped under the low traffic value will not be evaluated against the segment criteria.
     

    5 replies

    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    April 26, 2021
    In your second screenshot, besides the "Page URL Instances", what other metrics have you included in the table?
      Andrey_Osadchuk
      Andrey_OsadchukAccepted solution
      Level 10
      April 27, 2021

      Can you try to create a segment with the Instance attribution model as shown in the screenshot below and share a screenshot with full URLs returned in the table if that does not help?

       

      Also can you confirm that the Page URL dimension and the Page URL Instances metric in your table are linked to the same eVar (as sometimes there are various variables with the same name)?

       

       
      The urls grouped under the low traffic value will not be evaluated against the segment criteria.
       
        H
        H_LAuthor
        Level 7
        June 11, 2021

        Hi Andrey, please see my reply below. Thanks.

        H
        H_LAuthor
        Level 7
        June 11, 2021

        @andrey_osadchuk 

        I just create a segment by using Instance attribution model.

         

        Here is the outcome list:

         

        Seems that's saying:

        - The segment limits the outcome URL shall need to contains /troubleshooting, but there are some do not contain (e.g. Row 6, 7).

        - The filter limits the URL shall not contain /toubleshooting, there are some contains (e.g. Row 5)

         

        Sorry I cannot paste the full URL here,but I can confirm the hidden part of Row 6, 7 do not contain "/troubleshooting".

        If it's necessary, please let me know a way I can send you in private.

          H
          H_LAuthor
          Level 7
          June 11, 2021

          Hi @yuhuisg , the "Page URL Instances" is the only metric in the table.

          jantzen_b
          Adobe Employee
          jantzen_bAdobe Employee
          Adobe Employee
          July 19, 2021
          Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?
          Terms & ConditionsAccessibility statement

          Loading footer...