Purple Tracking

getting started a native purple app technically consists of a native part and a purple experience part that runs within a web view the purple experience is the dynamic area in the app that you can configure by adjusting the dynamic resources more on the topic of dynamic resources and how to integrate the file there can be found in the purple experience builder docid\ kmuf0oag3of3a46iup5q4 chapter both of the above mentioned app components can trigger events through user interaction this means that some of the events are only triggered in the native app area, while the other part is only triggered by the purple experience area with a few exceptions, this technical distinction is reflected in the naming of the tracking keys a more detailed description of tracking keys can be found here configuration event and attribute docid\ dlhlkez7ixhd33i4qab7k if an event is triggered by the corresponding user interaction, it is first transferred to the app's internal tracking management further processing takes place there before the events are forwarded to the specific tracking services this essentially consists of 2 points filter events or complete event types configuration of events and preparation of the event data for specific tracking services both points mentioned are configured by the " tracking config json " file this file is of json format and is also part of the dynamic resources you can find out exactly how this configuration works in the tracking configuration docid\ sxkxo oept7crfzzob9nw chapter in addition to the aforementioned integration of purple experience in a native purple app, purple experience can also be provided as a stand alone solution on the web the following graphics show a simplified overview of the entire tracking process for both variants experience as part of the native purple app simplified overview of tracking process in purple apps experience as stand alone web integration simplified overview of tracking process in web process summary for both variants various events are triggered by the user's interaction with the app or web forwarding of the events to the internal tracking management using the " tracking config json " file to filter and prepare the events for the specific tracking services sending the events to the specific tracking services how to proceed from here in this process, the following three questions arise so that a functioning tracking can be set up for your purple app which events can i use or are available to me as a purple customer? which events can i use or are available to me as a purple customer? the events available in a purple app are listed in the tracking events docid\ wmhcwvhbk60lcgh5urtfo chapter and in its subchapters how can i configure these events? which event is sent to which tracking service and how? how can i configure these events? which event is sent to which tracking service and how? the configuration of events is described in the tracking configuration docid\ sxkxo oept7crfzzob9nw chapter and its subchapters which tracking services can i use? which tracking services can i use? the tracking services that can be integrated into purple apps are documented in the tracking services docid 3ofsgplkna2zz3rzik3fg chapter the individual tracking services are described there at a technical level once you have read all three chapters carefully you will be able to set up tracking for your apps