I'm going to assume that you are using the all-datasets, timestamp-based merge policy.   If you define a relationship between the event schema and your look up schema for that Coupon Master ID, and you've marked both schemas and their corresponding datasets for Profile before ingesting data, then th...

For activation take a look at Computed Attributes:https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview That's normally all that's needed versus activating a long list of events. When they need more complex logic then people schedule Data Distiller SQL I...

I've not seen good results combining upsert with arrays. Nobody likes refactoring, but I'd split that array off into another schema/dataset where you don't need to use upsert. And then send the entire array every time that there's any change. Just ignore the array field in the original schema/datase...

My experience has been that at some point you need to sample. Take any random ten profiles from the system where you see more than the other. Then look to see what subset of the ten is in the other system, and for those that are not, investigate why they didn't make it into the same list. Usually on...