- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
07-25-2018 09:09 AM - edited 07-25-2018 09:10 AM
Is it possible to sent an Attribute from the Omnichannel to the EventStore, e.g. in the moment a visitor is mapped with the omnichannel?
We've set up Tealium AS with omnichannel, which we use fill some custom Visitor Attributes (e.g. with Target Group Information) for known visitors, and it's working fine.
Now we also want to be able to map the events from the eventstore with our data provided in the omnichannel to be able to do some offline analytics. Therefore we have to pass an identifier (we use a hashed id) from the Omnichannel into the Eventstore. But I don't know how to set this up, because the EventStore get's only attributes from "Event-Scope", of course. But it seems like I can not enrich an Event Attribute with an Omnichannel Attribute.
I'd be happy about any ideas! :-)
07-26-2018 10:26 AM
Yes this is possible. When you edit the Omnichannel File Definition be sure to check the checkbox "Send to DataAccess and EventStream Connectors". Save/Publish and this should add them to the EventStore logs.
07-30-2018 03:47 AM
thanks for your reply. I already have checked the box "Send to EventStream connectors". Still the attributes from omnichannel don't show up in the visitors event.
From my point of view, the difficulty is, that only attributes from "Event-Scope" show up in the EventStore, and Omnichannel-Channel attributes are of "Visit-" or even "Visitor-Scope". And I can't figure out a way to create "Event-Scope"-Attributes which contain omnichannel data.
07-30-2018 08:46 AM
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 "
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!
Copyright All Rights Reserved © 2008-2023