classify eVars colon delimeter | Community
Skip to main content
X
xcode2295
Level 4
October 20, 2022
Solved

classify eVars colon delimeter

  • October 20, 2022
  • 4 replies
  • 1614 views

I have below captured below in an eVar in a colon delimeted format. How can I show values in a row format individually?. My list eVars are all used.

 

 

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 FrederikWerner

You could use Classification Rules to pull those values apart, but that would have the challenge that your first value would end up in a different dimension from your second, third, etc. values. Instead, have you considered using a List Prop? That could be enough for what I see on your screenshot. If that would not be enough in terms of length, you could think of introducing name spaces to your list variables.

4 replies

J
jlinhardt_blueAcorn
Level 3
October 20, 2022

@xcode2295 

hello.  If your listVars are all used, the only other option you have would be to use a list Prop.  Prop variables can support a list, similar to listVars.  However, the entire string can't be more than 100 characters, otherwise the list prop won't work either.

 

I hope that helps.

    FrederikWerner
    Community Advisor and Adobe Champion
    FrederikWernerCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    October 20, 2022

    You could use Classification Rules to pull those values apart, but that would have the challenge that your first value would end up in a different dimension from your second, third, etc. values. Instead, have you considered using a List Prop? That could be enough for what I see on your screenshot. If that would not be enough in terms of length, you could think of introducing name spaces to your list variables.

    Learn more about Adobe Analytics and Customer Journey Analytics on my blogNeed help with Adobe Analytics or Customer Journey Analytics? Let's talk!
      X
      xcode2295Author
      Level 4
      October 21, 2022

      Yes, I have list prop available, so I can use that. Thanks for the suggestion. I think the length should not be a problem. I do not want to use classification rules and store the values in different dimensions. 

      jeff_bloomer
      Community Advisor and Adobe Champion
      jeff_bloomerCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      October 21, 2022

      Hi @xcode2295,

      When you say "show values in a row format," I hear how do I break these values out separately from each other.  I agree with @frederikwerner with using Classifications to break out the values, which "feels" like what you're asking.  The one limitation you run into with listProps vs. listEvars is character length, which could undermine what you're trying to do as well.  

      "List props are still subject to the 100-byte maximum length. List props are easier to hit this limit and be truncated, since they can contain multiple values. Consider using abbreviations or shortening values if you might hit this 100-byte limit."

      https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/prop.html?lang=en

        Alexis_Cazes_
        Alexis_Cazes_
        Level 10
        October 21, 2022

        I had a similar requirements for tracking in a project this is how I approached it. 

         

        We had a form where the stakeholder wanted to see individual selections in a form but also the concatenated version.

         

        I used a list variables to be called stacked values and did not actually assigned for any specific purpose just to send stacked values.

         

        When sending to adobe I would put everything in s.listN="type:D:value1|type:D:value2|type:D:value3|type:C:value1,value2,value3"

        In the reporting I would see a line item as follow:

        type:D:value1

        type:D:value2

        type:D:value3

        type:C:value1,value2,value3

         

        I then used the classification feature on the list variable to create one report Type Detail and Type Concat where type is the specific data use case.

        Then I used classification rule builder which said if start with type:D then put in Type Detail and if start with type:C Type Concat.

        This way I had the 2 reports that I needed with the details and the concatenated version.

         

        For your situation you have an evar, you could use classification to put in different reports if the section delimited by a : mean something specific in each case lets say type:category:productId. If the syntax always respect this order then you can easily use classification rule builder to split the value into their own reports which would give you the detail you need 

          Terms & ConditionsAccessibility statement

          Loading footer...