Assigning values to serialized event via Processing rules SDK | Community
Skip to main content
trochira
trochira
May 11, 2021
Solved

Assigning values to serialized event via Processing rules SDK

  • May 11, 2021
  • 3 replies
  • 3180 views

Hi, 

I have a question regarding the processing rules and events in Adobe Analytics SDK. I want to assign values to a serialized event via Processing rules. For example:

 

  • If a context key starts with A then assign value 1.5 to serialized event
  • If a context key starts with B then assign value 2 to serialized event

In other words this is how I see it before serialization :

 

Assigned valueSerialized ID
1,56789
26789
1,512345
212345
212345

 

And this is what I am expecting as serialized values - assuming that Adobe will sum up the Assigned values and serialize them by Serialized ID

 

Assigned valuesSerialized ID
3,56789
5,512345

 

Would it work like that?

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 jeff_bloomer

@trochira 
To answer your question about the processing rule, yes, you are correct about answer A, because you are using an eventID.  That eventID can only be used ONCE, and nothing else can be done with it ever again, which is how Adobe maintains the uniqueness of its value.  We actually ran into this when we found out that orders were accidentally going through with duplicate IDs when we were first learning how to do eComm.  Does this get to the heart of your issue?

3 replies

H
Adobe Employee
HemanginiAdobe Employee
Adobe Employee
May 12, 2021

@trochira ,

As I understand it is not possible to serialize events via Processing rules. This is also mentioned in this SDK document .
You can opt for VISTA rules, crafted by Adobe Engineering Services, but that is a paid option. (VISTA rule info... ).

Thanks,
Hemangini

    jeff_bloomer
    Community Advisor and Adobe Champion
    jeff_bloomerCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 12, 2021

    @hemangini is correct.  When you get into Adobe's documentation for Mobile specifically, they explain that, "Event serialization is not supported by processing rules."
    https://experienceleague.adobe.com/docs/mobile-services/ios/analytics-ios/event-serialization.html?lang=en#analytics-ios 

    They make digging for this info a bit fun, but it's there.  😉
    More on Event Serialization 

    trochira
    trochiraAuthor
    May 13, 2021

    Hi both @jeff_bloomer @hemangini 

     

    first of all, thank you for your replies and looking into subject. In this case event is serialized according to the SDK documentation and not via processing rules (it`s hardcoded). So the sequence is like that:

     

    1. Event is fired on the App

    2. Event is serialized via Adobe SDK

    2. Event is assigned specific numeric value (Assigned value column) via Processing Rules - depending on the parameters flowing into Adobe 

     

    Since serialization and Processing Rules are in place for the same event, I am wondering about the final outcome. I am expecting following scenarios:

     

    a. Serialization will result in assigning only first Assigned value to the event (and ignore any other Assigned values coming in)

    b. Serailization will not work and values will be assigned to the event one by one (i.e. all Assigned values will be coming in)

    c. Event will not bring back any values

    d. Other - no idea what could that be...

     

    This is a very specific case, where event is serialized and processing rules are assigning value to it. My guess is answer a), due to the fact of serialization and Processing rules, but have no evidence o far 

    Would you be so kind and share your thoughts ?  

    jeff_bloomer
    Community Advisor and Adobe Champion
    jeff_bloomerCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    May 13, 2021

    @trochira 
    To answer your question about the processing rule, yes, you are correct about answer A, because you are using an eventID.  That eventID can only be used ONCE, and nothing else can be done with it ever again, which is how Adobe maintains the uniqueness of its value.  We actually ran into this when we found out that orders were accidentally going through with duplicate IDs when we were first learning how to do eComm.  Does this get to the heart of your issue?

    trochira
    trochiraAuthor
    May 13, 2021

    Hi @jeff_bloomer 

    Yes, that is the essence of my question, thanks for looking in to it and for your answer

     

    Everyday we learn something new

     

    Regards

    Rafal

    Terms & ConditionsAccessibility statement

    Loading footer...