Full example: How to configure your events
In this article we show you an example how to create a full working tracking configuration supporting the use cases we defined for that example.
If you have arrived at this point, then you have learned everything about the structure and configuration options of the "tracking_config.json" file. Summary
To recap you have learned
Now you are ready to master configuring your tracking. Congratulations! Finally, you are cordially invited to go through all the configuration options described as follows.
We will start with the most important point:
"Identifying your use cases" The emphasis here is on "your". While Purple offers a "ready to use" config that is sufficient for common use cases, it still needs further customization if your use cases are not covered.
Your use cases influence which tracking service you have to use, which events or attributes you need for this and how these are configured in detail.
We sum up some simple USE-CASES (in a real world scenario your USE-CASES may be more complex.):
- I want to know my top 5 downloads in 2022.
- I want to know which issues/pages have been bookmarked.
- Which search terms are used in the internal search of the app?
- Does anyone use the app menu?
- Does anyone buy subscriptions?
- I want to offer a discount to inactive subscribers to encourage them to subscribe again (via push or in app message).
Identify requirements for the tracking services used:
In our example, we want to notify app users on the one hand via push and on the other hand via in-app message.
Our decision falls on
In the next step, we first have to generalize our use cases and then find the appropriate event or attribute for it (we look for these in the Tracking Events chapter).
Generalize USE-CASES
This step is necessary because a formulated use case often represents an evaluation of events. Based on our example: The use case "I want to know my top 5 downloads in 2022" represents an evaluation of events in the backend of the tracking service and is not carried out by the tracking of the app.
The following overview shows the result of generalization and the search for events and attributes. The individual use cases are also already grouped by event type:
USE-CASE | I want to know my top 5 downloads in 2022. |
---|---|
Generalization | For this evaluation we need the information about: Which issues are downloaded? |
Resulting event |
USE-CASE | I want to know which issues/pages have been bookmarked. |
---|---|
Generalization | For this evaluation we need the information about: Which bookmarks are created? |
Resulting event |
USE-CASE | Which search terms are used in the internal search of the app? |
---|---|
Generalization | The use case already has a general formulation. |
Resulting event |
USE-CASE | Does anyone use the app menu? |
---|---|
Generalization | The use case already has a general formulation. |
Resulting event | APP_MENU |
USE-CASE | Does anyone buy subscriptions? |
---|---|
Generalization | For this evaluation we need the information about: Which subscriptions are purchased? |
Resulting event |
USE-CASE | I want to offer a discount to inactive subscribers to encourage them to subscribe again (via push or in app message). |
---|---|
Generalization | For this evaluation we need two pieces of information:
So this use case is a combination of this event and attribute. |
Resulting attribute |
Now that we know our events and attributes, it's time to configure them in the "tracking_config.json":
STOREFRONT_ISSUE_BOOKMARK_ADDED
ISSUE_DOWNLOADED
STOREFRONT_SEARCH_PERFORMED
APP_MENU
STOREFRONT_SUBSCRIPTION_PURCHASED
HAS_ACTIVE_SUBSCRIPTION
We set our tracking services as follows:
Finally, we put everything together and get the following "tracking_config.json":
To test this tracking configuration, you need to make it available in your app. Since this file is part of the dynamic resources, you can integrate it with the Purple Experience Builder at this point. Further requirements: It is also neccessary …
- that you have your own account for the used tracking services and configured them.
- that your tracking services are configured and activated in your app in the purple manager.