xdm icon indicating copy to clipboard operation
xdm copied to clipboard

XDM Support for Chatbot Experience Event Schemas

Open marcus-robinson opened this issue 5 years ago • 2 comments

The current XDM schemas are not sufficiently expressive to represent the events emitted during chat interactions between brands and customers. We propose the creation of a new set of generic chat experience event schemas to represent such interactions.

What are the schemas that are affected by the issue

There are no existing schemas affected - the issue here is that there are no schemas that exist to represent a stream of events that are emitted from a chatbot and/or livechat experience.

What are examples of products that are impacted by the issue

Our chat automation platform, Stackchat, needs to send events to AEP as part of a client project. These types of events are defined here. On the recommendation of Adobe employee Wouter Van Geluwe (@woutervangeluwe ), we propose creating a set of generic chat experience event schemas that are common to all chat experiences across all third-party chat platforms.

Any chat platform will need to send to AEP both experience events & profile attributes. We plan to fork the XDM repo and raise a PR to add the new chat experience event schemas. We will use the existing profile schema for any user profile data.

As a business, we've invested considerable time and resources in defining how chat data should be represented and shared between external systems, as can be seen in our existing third-party integrations, such as with Adobe Analytics and Segment. As a thought leader in the space, we're well placed to lead this effort and are looking to the XDM team to provide their blessing for us to proceed.

marcus-robinson avatar Apr 29 '20 05:04 marcus-robinson

@cmathis @khanna-vikas @lrosenthol @prabhum2 Can you please give your blessing for us to go ahead and fork the XDM repo and begin work on this issue?

marcus-robinson avatar Apr 29 '20 06:04 marcus-robinson

There is no need to fork the repo...just go ahead and create a branch with your changes and when ready raise the PR for us to review.

If you'd like our input along the way, feel free to ask...

Most important think to remember as you design your schemas is "don't reinvent the wheel"..If there is a schema or even a few members/keys of that schema that meet your need - use them. Also, any other 3rd party schemas that exist and can be leveraged (eg. DublinCore, Schema.org, etc.) should also be looked at as well.

lrosenthol avatar Apr 29 '20 11:04 lrosenthol