Omniata allows you to integrate several different data sources to enable a wide range of use cases. In the following, we will go through integrating an external database with a Project, integrating a real-time event based Project, and integrating Custom Events that are specific to your use cases.
Project is a key concept in Omniata. Project is a set of configurations, managed through Project objects, that define how to structure and deal with a specific sources of data, extract useful information from it, and take actions based on this information. In other words, Project is a schema on how to process data to be used within Omniata, and how to make actions based on the data.
Within a Project you will have possibility to add visualizations of your data, create users segment to whom you can target with content that aims to change user experience. These experiences are part of campaigns that focus on, for example, A/B testing, In-App messaging, Push Notifications, and Email campaigns.
Projects have often different scopes. Some Projects are built on real-time event data streams from one (or more) applications, while others might read from databases hosted outside of Omniata.
Currently, there are two types of Projects in Omniata:
Below are some examples of Projects. Mobile Game is an example of a single game and within the Project will have visualizations, information on Push notification campaigns, tools to engage users in real-time and many others. We will explore the content of this Project later. The other Projects are Web Store (example of an online store), User Acquisition (user attribution and ad network data on marketing spend), and External Database (data hosted outside of Omniata).
In the previous chapter one you installed a Database Data App and created a widget with filters in the dashboard. These were an example of connecting to externally hosted database where Omniata uses the specific database as a data source. The other type of Data Apps supported by Omniata uses event streams as data sources. These are called Event Based Data Apps. Examples of these are mobile apps and websites that create a stream event data.
In the following exercise you will install an Event Based Data App, and in the following chapters we will review all parts of the Data App from exploring your data to building and launching targeted user campaigns. Let’s start with installing the Data App.
Go to Omniata Store and select ‘Custom Data App’. You will see this:
All Data Apps come with a predefined set of reports (widgets), event types, and reporting tables. You can also select which widgets you want to include in the Data App. Add name to your Data App and install. After that the Data App is being installed and you can find it in the ‘All Data Apps’.
If you bookmark your Data App, you will find the Data App in your Favorites.
Select the Data App you just created. You will see the following, which indicates that there is no data available for the widget in question. The most common reason for this is that no data has been sent to the Data App.
In the next chapter, we will start connecting your application to the Data App.
In the previous chapter you sent a standard event to your Data App. Omniata does not limit what kind of data you can sent, as long as you follow the formatting rules. Any data you are sending to Omniata can be visualized and potentially take actions based on the results.
In the following exercise you will add a new event to you Data App and add the new event to your Data App by performing an event scan.
Copy another event (for example om_user) and modify the parameter names. It does not matter what parameters and values you put there, as long as the om_event_type is somethins new. Below we are usinng 'banner_view' as an example of what you will see after sending the event.
You can see that the new event has been highlighted. You can add the new event to the Data App by clicking on the ‘Add’ button. This will open up the following:
Just review the details and if everything seems as it should be, you can simple add it to your Data App. The ‘Required’ indicates whether the parameter is required by the Developer Console. If selected, and more events are send but without the parameter will be indicated in the panel with red color. The data type is automatically detected, but it is good practice to review them. Non-numeric values are always strings, and numeric values can have several different data types. You can also leave some parameters unchecked, in order to not to include them in the Data App.
You can review all the event types by going to Data -> Event Types
Details of each event can be found by selecting the event name
OK. You have now added a custom event to your Data App. In the next chapter you learn how these events and parameters are transformed to actionable items called Data fields and what role they have in the Data App.