Split ab=3|cd=1|ef=1 in separate events (Processing Rules possible?) | Community
Skip to main content
OscarMartinezM
OscarMartinezM
Level 3
November 22, 2022
Solved

Split ab=3|cd=1|ef=1 in separate events (Processing Rules possible?)

  • November 22, 2022
  • 2 replies
  • 2697 views

Hi community, 

I have a client that would like to count how many search results are the users getting, by they would like to count them by category. For example, if user gets 20 results, we would get something like:

  • Category 1: 13 results
  • Category 2: 3 results
  • Category 3: 4 results

We are thinking in having an event of type counter for each category. But the thing is more categories would be created in future.

It's ok from our side to create new events every time they add a new category. But we would like to avoid changes in site code for assigning new events. Based on that, we tought in the option of sending all categories and values in a single eVar, then process it ans assign events using Processing Rules.

Is is possible? Do we have something like split funtion un Processing Rules? Any other option?

Thanks!

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 OscarMartinezM

You mean having 1 eVar for "category" and 1 event for "counter":

  • eVarXX: Results Categories
  • eventYY: Results Counter by Categories

So, we could display like this:

eVarXX eventYY
Category 1 25
Category 2 12

 

Ps: I created the first parte of this response before. But now I've realized it wouldn't work, because I need to take the value for each category and increasing counter for each one. I mean if:

  • At <T>: {Cat1=10, Cat2=15, Cat3=20}
  • On new user visit: {Cat1=2, Cat2=0, Cat3=5}
  • At <T+1>: {Cat1=12, Cat2=15, Cat3=25}

2 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 22, 2022

I do something similar, I set an eVar or prop with search result data (search result page|number of results|number of results per page|sort order), then I use a classification rule to split these values into separate dimensions... Processing Rules is good to concatenate values, not parse them. You could in theory look for "IF contains value Category 1 then set eventX"; but I'm not sure if this is the best approach....

 

I'm not sure why you would need an event per category? What are you trying to capture with the event? That a search was performed that returned data in that category?  So IF you "have" a category 4, but it didn't surface in the results then you wouldn't have a "search results event" for category 4?

 

Why not have 1 event "search result page", then use a classification to split the results per category. If there is no value for Category X in the results, it wouldn't apply to that classification. Then you won't be going through tonnes of events that all perform the same basic function.

    OscarMartinezM
    OscarMartinezMAuthorAccepted solution
    Level 3
    November 23, 2022

    You mean having 1 eVar for "category" and 1 event for "counter":

    • eVarXX: Results Categories
    • eventYY: Results Counter by Categories

    So, we could display like this:

    eVarXX eventYY
    Category 1 25
    Category 2 12

     

    Ps: I created the first parte of this response before. But now I've realized it wouldn't work, because I need to take the value for each category and increasing counter for each one. I mean if:

    • At <T>: {Cat1=10, Cat2=15, Cat3=20}
    • On new user visit: {Cat1=2, Cat2=0, Cat3=5}
    • At <T+1>: {Cat1=12, Cat2=15, Cat3=25}
    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    November 23, 2022

    You can consider using list props https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/prop.html?lang=en#list-props

    With list props, you can send a delimited string to AA, then AA will split that into the individual values in the prop's report.

    So if you want to track:

    • Category 1: 13 results
    • Category 2: 3 results
    • Category 3: 4 results

    You could use the following (assuming you've configured prop12 as your list prop, using "," as the delimiter):

    s.prop12 = "Cat1:13,Cat2:3,Cat3:4";

    The resulting report would look like this:

    prop12 Occurrences
    Cat1:13 1
    Cat2:3 1
    Cat3:4 1

    You can then use Classifications to further separate the Category from the Results count, as Jennifer had suggested.

    The biggest disadvantage with this approach is that your delimited string has a 100-character limit, as all props do. If you need to track longer strings, you can use list eVars https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/list.html?lang=en, but every report suite has a hard limit of 3 list eVars only.

      OscarMartinezM
      OscarMartinezMAuthor
      Level 3
      November 23, 2022

      The thing is we need would like to count how many results of each type are displayed to user and it's accumulative. For example, if User1 gets "Cat1:13,Cat2:3,Cat3:4" and User2 gets "Cat1:10,Cat2:5,Cat3:0". After those visits, we will have:

      • Cat1 = 23 (13 + 10)
      • Cat2 = 8 (3 + 5)
      • Cat3 = 4 (4 + 0)
      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      November 23, 2022

      Ok, so you can't use a "counter" event if you are trying to actually use the event to represent the values of the results.. a "counter" event will count the occurrences. 

       

      If you really need the event counter to count the values, there is no way around setting up a unique event for each category, setting them up as "Numeric events", and setting the values as:

       

      s.events="event1=10,event2=5" etc

       

      Numeric events you can pass how much to increment the event by.

       

      But this is going to be hard to maintain, and use up a lot of your events.

        Terms & ConditionsAccessibility statement

        Loading footer...