It seems like Tealium is no longer on this list: https://github.com/disconnectme/disconnect-tracking-protection/commit/9158ab0bded2a6471112bae229937208fb5ca65e (see also: https://github.com/disconnectme/disconnect-tracking-protection/issues/31#issuecomment-471711233)
... View more
Thanks for the additional details, as now I believe I understand where the confusion exists.
If you've used the Tealium Universal Data Hub for a couple of years you may remember that we used to scope Omnichannel attributes to Visitor/Visit scoped AudienceStream attributes.
However, Omnichannel attributes are by default now considered event attributes, hence why you see them in EventStore. This is due to the fact that even if the data is associated to a visitor, it's based on an action (or event) that the visitor has taken or that a system has calculated against the visitor. If you go to EventStream > Attributes you can see a filter for Omnichannel in the left nav showing that these are indeed event attributes. Therefore, your current Omnichannel setup with " Send to DataAccess and EventStream Connectors" checked handles passing the Omnichannel event attributes to EventStore.
If you need to store an Omnichannel attribute at the Visit/Visitor level then you'll need to explicitily create a new AudienceStream attribute to store the event based data.
If you have any further questions it may be useful to contact your Account Manager for further discussions, we are always here to help!
... View more