Hi,
I am having profile count mismatch with the backoffice commerce data that is sent to AEP. When I check in commerce, there are 100k unique buyers who made a purchase, but when I do segmentation in AEP, I get only 60k profiles. I did various tests to see if we are receiving backoffice events data into AEP or not, and I saw the events data is coming in into profile as soon as an order is placed into magento, and I couldn't find a single profile getting dropped from events randomly.
A strange thing I saw in the backoffice dataset is that it is receiving 1k records but only ingesting 600-700 records, but none of the records are failing. Could this be a problem on why profile counts are low in segmentation?
TIA
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @SaurabhDeswal - How are you defining identity of a profile in AEP? Out of the 1000 records you are ingesting , does all of them belong to different customer, is there a possibility that out of 1000 records , some records belong to same customer due to which AEP just understand it as the same customer brought some other product.
Thanks,
Arpan
Hi @SaurabhDeswal - How are you defining identity of a profile in AEP? Out of the 1000 records you are ingesting , does all of them belong to different customer, is there a possibility that out of 1000 records , some records belong to same customer due to which AEP just understand it as the same customer brought some other product.
Thanks,
Arpan
Hi Arpan, you made a really good point. So if AEP stitches 2 different emails into a single profile, the segmentation count would count that as 1 if an order is placed from both of those profiles?
For example: AEP stitched email A and email B into one profile. Now email A places an order and later email B places two orders.
Would AEP segmentation output 1 profile if I put an condition to output profiles with 3 orders?
@SaurabhDeswal Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies