trackAction in mobile app passing multiple events

[William83]

hello all

Is it possible to pass/fire multiple events against a the one trackAction? In this case an interaction and an additional event using a.action coupled with &&products.

Specifically, we are tracking an interaction via trackTask with the addition of setting a named event via a.action against &&product

However, when reviewing Assurance, we are seeing the app interaction evar and event fire/count as expected. We can also see the &&product set correctly but we do not see the associated event number count, we only see the count for interaction event. I wonder if this is a limitation whereby a trackTask can only count one event. 

I can confirm we have setup processing rules with the event coupled with the condition of a.action(Context Data) equals 'Any of' of the event name 

I hope that makes sense thank you all

[Elanchezhiyan_E]

Hi @William83,

Yes, It is possible to fire multiple events with a single trackAction call.

You can either configure both events within the same processing rule or create a separate processing rules for each event, depending on your implementation preference.
Please let me know if you need further assistance.

[KumarRishii]

It seems like there may be a limitation in how trackTask handles multiple events or how the processing rules are applied. To resolve the issue, I recommend separating the events or adjusting the rule logic to ensure that both the interaction event and the product event are counted separately in Assurance.

[AJODev]

Hi @William83 ,

it is absolutely possible to fire multiple events with a single trackAction call, but the way those events are registered and counted depends on how you structure your implementation and processing rules.To track product-specific events correctly, you need to include them directly in the &&products string. Just setting the event globally or in context data isn’t enough—it won’t link the event to the product. When using trackAction, pass a context data object and map your keys to events through processing rules. Make sure product events are tied to the product using the product string, not just set separately. Check your processing rules for accuracy. Use tools like Adobe Assurance or a debugger to verify events are firing. This ensures both interaction and product events show correctly in reports.

Thanks

AJODev