Duplicate ecommerce events are getting fired. | Community
Skip to main content
Level 3
September 24, 2024
Question

Duplicate ecommerce events are getting fired.

  • September 24, 2024
  • 1 reply
  • 561 views

The scenario goes like, my implementation is for an application and I have used the mobile SDK for the same. Now, all the allocation to eVars, props and events would happen via processing rules at the end. In my use case, when I am looking into the values of the out of the box events specifically for Product Views, Cart Additions, Cart Views, Checkouts and all..I am seeing the the count is twice or even, which means if product is added once, it is getting counted as twice. 
Please Note : It is a counter event not numeric and no any custom configuration is done in the report suite configuration as well.

 Cart AdditionsProduct Views
Prod A22
Prod B04
Prod C26

 

Thanks in Advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 24, 2024

Do you have AEP Assurance installed in your apps for testing? Have you checked all the data that is being sent to Adobe, and also what the post-processing is doing?

 

There are so many potentials here, that without seeing it, it will be really hard to diagnose... the first step is to really test your implementation and try to identify where it might be happening... whether it be multiple calls (with the same data), the data being sent to Adobe being doubled, or maybe something happening during the mapping...

 

Figuring that out is the first step to understand and fixing the issue.

Level 3
September 25, 2024

App is  not a commercial based, so I can not install that and create a session to see the analytics events at this point.

 

I thought of removing the processing rule (below) from the configuration for atleast 2-3 days, but then workspace report shows "0" as a value against that product. 

Not sure exactly which section to look at while debugging.