Mobile App, Purchase Event, Processing Rules & Handling incrementor events and merchandising evars

[#1]

Hello - I am implementing a mobile app.  Our product string contains several incrementor events and a single merchandising eVar.  See example below.  I am not sure how to set up processing rules to handle the incrementor events and the merchandising evar.  They are all showing up as 0.   Is there anything special you need to do in order to get the data to show up accurately?  Please note I know that some of the events have 0 in them already.  Thanks for the help!

;c5cb53cb212e41f9a9f5812d6c047629;2;22.64;event70=24.84|event71=24.84|event72=2.7|event73=0.5|event74=0|event75=0|event84=2|event85=2|event86=0|event87=0;evar65=Jet

[#2 · Accepted solution]

This is solved.

The documentation did not have information discussing &&events in conjuction with incrementor events.  So if you are using incrementor events in the product string, you must use &&events.  merchandising evars work fine in the product string (&&products) simmilar to web.

[#3]

HI Michael,

Thank you for replying this is great information. You are correct, I did find the corresponding documentation here: 

Android: https://marketing.adobe.com/resources/help/en_US/mobile/android/products_variable_evars_events.html

iOS: https://marketing.adobe.com/resources/help/en_US/mobile/ios/products_variable_evars_events.html

I updated the event documentation to clarify how events are set with the SDK here: https://helpx.adobe.com/analytics/kb/comparing-event-types.html

Best,

Tacia

[#4]

Hi Michael,

In the events report do the events show as zero, or only when added to the eVar report? Per the documentation here: 

"Processing rules cannot read eVar values from the product list. eVars used by processing rules must be populated directly on the page (for example s.eVar1="news") or by using a processing rule earlier in the processing order."

If this is a product variable syntax the processing rule wouldn't work. The eVar would need to either be set on the image request, or implemented by a processing rule earlier in the order to set the eVar. I think in this case that is the most likely cause of the issue.

-Tacia