Sitecore CDP Notes: Understanding the “Point of Sale” Concept
I approach the Sitecore CDP product from a several angles. Outside of the advanced data mart, integrated cloud APIs, and extensive testability, I impress on learners the importance of the “Point of Sale”. In Sitecore, this is referenced through the platform as the “PoS”. It is one of the core requirements for event sessionalization, and a critical concept to understand for debugging the Sitecore CDP APIs. In this document, I explore specific use cases where PoS is used; most are the use cases that appear on the CDP and Personize Certification Exam.
The Anatomy of a CDP Event
One key are of the certification exam is the actual JavaScript that is implemented to collect event data. In this case, the PoS parameter is intended to represent that application it is placed on, as the source of the event.
var viewEvent = { "browser_id": Boxever.getID(), "channel": "WEB", "type": "VIEW", "language": "EN", "currency": "EUR", "page": "/home", "pos": “spinair.com”}
Notes
- When debugging the event timelines in the Sitecore CDP, Events that fail to be populated usually don't have the PoS parameter defined
- In general, sessionalization is constructed from the Browser, Channel, and Timestamp
- The PoS parameter is often used to validate the API response for Interactive Tests