I am looking for advice on how to troubleshoot an issue that I am seeing in our reporting.
there are a small number of duplicate Order Ids that are used across multiple days that we are seeing different product and revenue amounts tied to them. We are only seeing the first date and product in our back end system so I am under sure how the second would populate with a different revenue amount and different productions
Dates – 2/8 and 2/12
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @denise_arjunan1 , I'd love to hear what others offer, but one thing to consider is that if you have a high number of order IDs (<100k), there is a greater likelihood of Hash Collisions,which can manifest like this (multiple items mapping to the same value when they should not). Adobe Support should be able to help identify if this is indeed the case.
My only other thought would be that whatever mechanism is used to create Order IDs somehow created the same one twice. That's a long shot, has this happened before, or is this the first time you've seen this?
You might also check other dimensions like user domain or agent string, MCID (if you collect it), just to make sure it's not the same person in both cases, in which case there could be some kind of caching going on.
Hi @denise_arjunan1 ,
This could happen because of reasons like,
Order ID is not an OOB dimension in Adobe Analytics/CJA so I'd assume you are using a custom dimension to track this information. Adobe provides ability to persist the custom dimensions beyond the hit they were set on using expiration settings. If you are using a dimension with expiration longer than hit then what you are seeing could happen. Here's a scenario that can cause it,
You should check for two things to fix this issue,
Cheers!
Hi just to add to previous 2 comments. I suspect OrderID is an evar that is captured at time of purchase event in your case. If it is make sure to change it be HIT/visit based expiry under admin > reportsuite > conversation variable settings. This should eliminate the duplication of if it is a cache based from longer lookback window.
Next if possible look at IP, city, any used ID evars/props you may capture for these 2 transactions to see if they are indeed same user or 2 new users.
Views
Replies
Total Likes
Thanks All for your input.
Here is the current configuration in our report suite manager and is set with the purchase event in tags
The order ID is only showing once in our back end system so I don't think it is an issue with our order id generation process.
Our ecid and geo data is showing two different IDs and States
We do have a large number of orders - so I am opening a ticket with Adobe support to discuss the Hash error possibility.
Views
Likes
Replies
Views
Likes
Replies