OOTB XDM variables are not working as conditions in Processing Rules | Community
Skip to main content
pradeep_nextrow
pradeep_nextrow
Level 4
January 20, 2022
Solved

OOTB XDM variables are not working as conditions in Processing Rules

  • January 20, 2022
  • 3 replies
  • 4223 views

Hello Folks! I am facing a weird issue. Have implemented Web SDK to capture AA data. I am using processing rules to populate many eVars and props. But to my surprise none of processing rules were firing and all my custom variables had no data. I found that an overall condition ("implementationDetails.version" which is an OOTB XDM value) for the processing rules, did not meet and hence no rules fired. I tried with "web.webPageDetails.name", same result. I change the processing rule condition to a custom XDM value that I defined and they seem to be working fine.

My hypothesis here is the variables which are automatically mapped to AA which are defined here - https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/automatically-mapped-vars.html?lang=en#data-collection is not available in processing rules. (But in the documentation it is not mentioned and in fact some examples use these). Anyone else facing this issue or any workarounds here? TIA!

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 yuhuisg

@pradeep_nextrow shouldn't you be mapping from the 2nd column in the table at https://adobe.ly/3Ira5zD?

So in your screenshot, instead of using "a.x.media.mediaTimed.starts.value", you should be using "c.a.media.view". Note: I don't use Adobe Video Analytics, so I am unsure if this will solve your problem. So the above is based on my understanding of the mapping in that help page's table.

3 replies

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
January 21, 2022

Are you prefixing your XDM variables with "a.x...."?

The following works for me:

 

    pradeep_nextrow
    pradeep_nextrowAuthor
    Level 4
    January 21, 2022

    Yes, I am using "a.x". In fact the eventtype was working for me as well. But this is not passed in all my alloy.js calls. Since I want the processing rules to fire only for alloy.js calls. So wanted to use "a.x.implementationDetails.version". But the condition is not met. Tried with "a.x.web.webPageDetails.name" that was not met as well.

    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    January 21, 2022

    One thing that you can do is to use the Adobe Debugger to verify your assumptions.

    Sign into the Adobe Debugger and toggle to your appropriate organisation. Then, in Logs > Edge, enable logging by clicking "Connect". Now, when you send Web SDK events, you should see logs for Adobe Analytics. You can then see what are the fields that Adobe Analytics is receiving. Then you can use whatever is listed there in your Processing Rules.

    Here's an example of what I get from a single Web SDK event:

    I don't see "implementationDetails" in the list of "c.a.x...." parameters, so I won't be able to use that in Processing Rules.

    For reference, this was the Web SDK event that resulted in that AA hit (you can see the matching "_id" parameter value in both screenshots):

     

    D
    Adobe Employee
    dwright-adobeAdobe Employee
    Adobe Employee
    January 21, 2022

    That seems odd. "implementationDetails.name" is just the version of the alloy.js library, so that should always be present. How did you conclude that the condition "did not meet"? What debugging process were you using to come to that conclusion? Do you see that XDM value passed in the page call?

      pradeep_nextrow
      pradeep_nextrowAuthor
      Level 4
      January 21, 2022

      @dwright-adobe I used real-time reports for validation. Let me shoot a quick video and post it here. I setup a processing rule "If a.x.implementationDetails.version exists, then populate prop5 to some value". Then, monitored the result in Real-time reports. This setup was not populating any numbers. Then if I remove the condition, real-time reports populate data for prop5. I replaced the condition with "web.webpageDetails.name", then similar problem occurred (no data in real-time reports).

      The primary reason I ended up doing this experiment is, I was doing AppMeasurement to WebSDK migration for a big client and no data was populating in AA after 3 days of setting up processing rules.

      pradeep_nextrow
      pradeep_nextrowAuthor
      Level 4
      January 21, 2022

      @yuhuisg @dwright-adobe I just sent up a simple processing rule without any condition: 

      I was not able to see event14 fire in the Real-time reports. I am using "media" Mix-in (Field Group) to capture video related data. Even though it gets mapped automatically to video reporting inside AA, I want to fire custom events based on this. So if I use processing rules for that, it is not working. So the question is are the variables listed here - https://adobe.ly/3Ira5zD are not available in processing rules? (as these are auto mapped?).

      If that is the case, it defeats the very purpose of using standard Mix-ins (field groups) as I will not be able to copy the values as per my wish into AA.

      yuhuisg
      Community Advisor
      yuhuisgCommunity AdvisorAccepted solution
      Community Advisor
      January 23, 2022

      @pradeep_nextrow shouldn't you be mapping from the 2nd column in the table at https://adobe.ly/3Ira5zD?

      So in your screenshot, instead of using "a.x.media.mediaTimed.starts.value", you should be using "c.a.media.view". Note: I don't use Adobe Video Analytics, so I am unsure if this will solve your problem. So the above is based on my understanding of the mapping in that help page's table.

      pradeep_nextrow
      pradeep_nextrowAuthor
      Level 4
      January 24, 2022

      @yuhuisg Sure! I am going to try this today and will keep this thread posted!

      Terms & ConditionsAccessibility statement

      Loading footer...