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 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.

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:

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 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:

Process summary for both variants

In this process, the following three questions arise so that a functioning tracking can be set up for your Purple App:

Once you have read all three chapters carefully you will be able to set up tracking for your apps.