Auto Update of data tables using personalization | Community
Skip to main content
JyotiSharmaV
JyotiSharmaV
New Participant
August 22, 2023
Solved

Auto Update of data tables using personalization

  • August 22, 2023
  • 1 reply
  • 1798 views

I have a data table on a page and works like backend code reads the product data.. and throws it in page. the product data lying in AEM

 

We have activity map in analytics that counts automatically the number of clicks happening on each category type. I want to create an experience in Target where the most clicked category automatically rolls on top of the column Is it possible via target?

 

 

    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 alexbishop

    Thank you for the explanation that makes total sense. Can you tell me what that means how this be implemented in my case?

    1. You need to use "token replacement" when you create the offer, as explained here. So for example, the content in the first row of your table would reference ${user.categoryAffinity}. 

    I am following like below steps"

    1.  In Launch I created a rule where I am passing user.CategoryId as an mbox parameter and mapping it to data element that reads the product category of the page for eg. Slim Fit shirt, Regular Fit shirt, etc.

       

    2. Then I went to Target and created a category affinity audience Additionally, I also created a profile script with category affinity like the one below which I guess will also work the same as my audience but not sure

       

    3. The next step you mentioned is Token Replacement, I am not sure where & how to use it. where this steps is needed and why? Unfortunately, there are no video tutorials of Target in this case. 

     

    One thing I want to highlight here is my data tables exists on

    Product Category Pages (with rows telling Product family type) 

      

    and Product Family Pages (showing product family part numbers) for precise navigation of userS.

     

    I am not sure how the target will read which is getting clicked most in the table and do the affinity thing. Can you elaborate on that? I understand it's individual user based but then what is the role of table autoupdate then?

     


    Step 3 for token replacement is so that the top row of your table will dynamically display the most clicked category. So when you create your offer in Target, the top row of the table will reference ${user.categoryAffinity}. 

    For example:

    <table> <tr> <th>Product</th> </tr> <tr> <td>${user.categoryAffinity}</td> </tr> <tr> <td>Shoes</td> </tr> <tr> <td>Hats</td> </tr> </table>

     

    In terms of how Target reads what is clicked the most - you will need some sort of event handler, so each time someone clicks, you would send a request to Target that includes that user.categoryId parameter with the value of the product clicked on. Target then automatically stores all of these clicks and calculates the favourite product, 2nd favourite etc etc

    1 reply

    alexbishop
    alexbishop
    Employee
    August 23, 2023

    Yes, if you implement Category Affinity then you can create your Experience in Target where the top item in the table is a dynamic reference to "favourite category", the second item references "second category" etc etc 

      JyotiSharmaV
      JyotiSharmaVAuthor
      New Participant
      August 23, 2023

      @alexbishop you mean the data table will get automatically updated even without any code logic?

       

      Questions:

      1. I also have a question about user.categoryId, a mbox parameter assigned on a product page. Is this something automatically available or do I have to pass it on the page like a page param, & how can I do that? Can you pls elaborate on this?
      2. This paragraph from the documentation is bit confusing:  You can also record category information by passing it as the mbox parameter user.categoryId in any mbox (including a nested mbox), as a URL parameter user.categoryId, or in Target page parameters with a global mbox. See your account representative for more details.  WHAT does that mean? How to do that?

      3.  I understand the category affinity algorithm and how it works.  But need to understand how to implement this user.category parameter? Also, is creating a category affinity audience enough or do I need to have user.category parameter also created and passed?

      4. Also, tell me what kind of Target activity it would be and what would be goal metrics?

      Thanks

       

        JyotiSharmaV
        JyotiSharmaVAuthor
        New Participant
        August 23, 2023

         

        @gaureshk_kodag as per your response here https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/category-affinity/m-p/559314/highlight/true#M8365  on old thread of me ""you'll first need to pass category as a mbox param inside user.categoryId parameter" How this will be implemented? Is it via Adobe Launch and how? 

         

        Because we usually pass the global mbox parameter on page load via logic "adding params to all request" in launch and inside that we pass the param name and map it to data element. 

         

         

         

         

        Can you explain how user.category thing will be implemented?

         

        Thanks in advance

          Terms & ConditionsAccessibility statement

          Loading footer...