A Project is a set of configurations that define how to structure and deal with a specific source of data, and extract information from it. In other words, a Project is a schema on how to process data to be used within Omniata.

There are three types of Projects in Omniata:

  • Application Projects: Uses events as source of data, and defines how to transform the events and aggregate the data.
  • External Database Projects: Uses external relational databases as source of data, such as MySQL or PostgreSQL. Project defines how to connect to these databases and how to use the data from the database tables.
  • External Services Projects: Used for visualizing data from service partners such as User Acquisition attribution partners and ad networks

Projects can be accessed from the homepage. The homepage allows you to access all Projects, as well as selecting "favorite" Projects. A Project can be favored by clicking the star icon the Projects icon.

Application Projects

Application Projects build on event data sent from an application to Omniata Event API. Omniata directs the data to appropriate Application using the API key.

Creating an Application Project

To create a new Application Project, navigate to the homepage and select 'New Project'.

  1. Select Blank Project to create an Application Project which will expanded later with Packages that have be predefined settings, for example standard Event Types, Data Fields and User Fields.
  2. (Optional) Select Standard Metrics to create a global Project that summarizes key metrics from all other Application Projects.

Applications and API Keys

Application defines API keys per Application and per Environment. The API key is passed along in each event and it will determine, which Project/Application/Environment will process and transform the event.

You can access them by navigating to Settings > Applications > 'My App'.

Creating a New Application

The default mode of creating a new Application is to have one per app. Only in specific use cases, such as cross-platform analytics, does a Project only a single Application (this requires you sending 'platform' as a parameter within the om_load event).

To create a new Application, select 'New Application' on the Applications page. The API keys are automatically generated for all Environments. Please contact our Customer Support to complete the set up.

Creating a new API Key

If needed, you can create new API keys by navigating to Settings > Applications > 'My App' > 'Add API Key. You first select which Application the new API keys are associated to, and then select API keys for all Environments, or only for a specific one.

Project Settings

Project Settings can be found by navigating Settingz > General. There you can:

  • Change Project Name
  • Identify Machine Name (for custom SQL)
  • Used ID Parameter: Parameter used to identify the user (the default is 'uid').
  • Event Type Parameter: Parameter to identify the Event Type (default is 'om_event_type').
  • Show in Dashboard. Unselecting will hide the Project.
  • Type (default is OmniataDataModel)
  • Project Icon: Add an icon to your Project. It will be shown on the front page. (Optional)
  • Permissions: Set up Permissions for the Project.
  • Remove Project
    • Please note that deleting a Project will erase everything related to it from the Omniata Panel. The deletion of a Project is permanent and cannot be reversed. Deleting a Project will delete associated Data Fields, Tables, Charts, and all Engagement objects. Please note that this only effects the panel, all underlying raw data will still be stored by Omniata.

External Database Projects

Omniata supports accessing several different databases, which allows visualization of almost any data in the platform. Currently Omniata supports the following databases:

  • MySQL
  • PostgreSQL
  • Redshift
  • Vertica
  • BigQuery

To gain access to these databases, simply select the right External Database Project from the New Application, provide a name for it, and add the requested credentials. Once connected, Omniata requests to confirm the schema to ensure that the data can be used for data visualization.

An important aspect to remember is that using database connections only provides a view option of the data stored externally. No modifications can be made to the SQL tables from Omniata. Furthermore, the Database Connections are static in a sense that they do not enable Campaigns or User Acquisition marketing information. To use these Omniata features, an application needs to be connected to Omniata with real-time event data.

As the External Database Projects only read from externally hosted databases, there are only limited options for data modeling. The only aspect that can be managed is use of Table Fields. Please go to sections on Fields to review the options available for Table Fields.

This article was last updated on July 12, 2016 11:37. If you didn't find your answer here, search for another article or contact our support to get in touch.