You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had several partners and customers confused how to implement events or debug events when they don't work. It seems we don't include documentation of the required context data object schema and contexts or distinguish how to verify events and context data that are sent to the adobeDatalayer are actually sent to Sensei. This confuses partners and merchants, leading to them giving up trying to implement Recommendations, blaming Adobe and frustrated with not being able to implement it. Support resources do not seem to suggest this either, leading to more frustration.
What changes do you propose?
Github events documentation has the required Context data objects for each Event required, and the Context data schema required. These examples of each event, the required context data, and the context data schema for each context data type should be moved into explicit Experience League pages and linked from this page.
Anything else that can help to cover this?
None
The text was updated successfully, but these errors were encountered:
Thanks for the report @cscrewvala. I created an internal Jira ticket to track work on this (COMDOX-1007). I'll provide updates here as well as we make progress.
Is there an existing issue for this?
Which topic?
https://developer.adobe.com/commerce/services/shared-services/storefront-events/sdk/context/
What's wrong with the content?
I have had several partners and customers confused how to implement events or debug events when they don't work. It seems we don't include documentation of the required context data object schema and contexts or distinguish how to verify events and context data that are sent to the adobeDatalayer are actually sent to Sensei. This confuses partners and merchants, leading to them giving up trying to implement Recommendations, blaming Adobe and frustrated with not being able to implement it. Support resources do not seem to suggest this either, leading to more frustration.
What changes do you propose?
Anything else that can help to cover this?
None
The text was updated successfully, but these errors were encountered: