A previous update to Trace functionality introduced a bug that prevented "current visit" scoped attributes from displaying enrichments within Trace. This issue has been resolved. Please note, applying the enrichments to visitor profiles was not negatively affected; this was purely an issue with Trace only.
Many performance updates have been made to DataAccess to ensure Amazon Redshift remains scalable and provides speedy performance.
Previously, Omnichannel data was not acted upon in a manner that represented a typical web event. It was setup such that if multiple rows of Omnichannel data was applied to a visitor, only the last row of data was applied to the visitor profile. Omnichannel Enrichments corrects this so that each row of Omnichannel data mimics a true event and can be correctly applied to a visitor profile. Please see this post for more details.