Global Settings

Omniata has built-in tools for managing common settings. It can be accessed by selecting the main navigation on the left top corner, and selecting Global Settings all the way down. Here the following can be configurated:

  • Environments
  • Lookup Tables
  • Platforms
  • Service Status
  • User Management (covered in a separate section)
  • Organization Settings


Environments are used for separating data from different phases of your application development. Three Environments exist by default: Development, Staging, and Production.

  • Development: your local development machine.
  • Staging: your staging server. A staging server is usually used to QA a new version of your application, before pushing it to production.
  • Production: Your production servers. Production servers are the ones that provide the services to your consumers.

The following should be taken into account with Environments:

  • You can modify the display names of the environments. For example, Staging Environment can be renamed as QA.
  • Dashboards show data from one Environment at a time.
  • Reporting Tables can be scoped to contain data from only certain Environments.
  • Data for each Environment is stored physically isolated from the other Environments. If you track Events from one user ID in environment A (e.g. Development), and then track Events with the same user ID in environment B (Production), those will be considered different users. The acquisition date of the user the day when the user ID sent first Event to the respective Environment.

Following actions can be taken with Environments:

  • Create new Environment.
  • Move the Environment up or down in the hierarchy. This affects the order of the Environments when selecting one in the Dashboards.
  • Edit the display name of the Environment.
  • Delete the Environment.

Lookup Tables

Lookup Tables allow you to make a “lookup” of a value received in an Event, and store the returned value in a Data Field. This can be very useful in the case where you only send the id of an object of which you have more information offline, or you want to normalize data. There are some built-in Lookup Tables, for example for converting two-character country codes (e.g. DE) to country names (e.g. Germany). These cannot be modified. For custom use cases you can create new Lookup Tables.

Managing Lookup Tables

Lookup Tables page and actions are presented in the following picture.

  • Search Lookup Tables by their name.
  • Create new Lookup Table.
  • Show the content of Lookup Table.
  • Upload data into Lookup Table using CSV file. This is applicable only for custom Lookup Tables.
  • Export the content of Lookup Table as CSV file. This is applicable only for custom Lookup Tables.
  • Edit the Lookup Table. This is applicable only for custom Lookup Tables.
  • Delete the Lookup Table. This is applicable only for custom Lookup Tables.

Creating Lookup Table

Select New Lookup Table. Page for creating new Lookup Table and its options are presented in the following picture.

  • Enter name for the Lookup Table. Note that the machine name for the table will be generated automatically.
  • Move the Column up of down in the list.
  • Enter name for the Column. Only alphanumeric (A-Z, 0-9) or underscore characters can be used.
  • Select data type of the Column.
  • Select whether the Column is part of Primary Key. One or several Primary Keys define unique items in the Lookup Table.
  • Delete the Column.
  • Add new Column in the Lookup Table.
  • Save the Lookup Table.

Loading Data into Lookup Table

Option 1: Enter records manually by entering records manually as presented in the following picture.

  1. Enter the content of one Row in the Columns. (Pay attention that the content matches the data type defined for that column)
  2. Add new Row in the Lookup Table. (The content of the Lookup Table is saved and stored automatically)

Option 2: Load records in batch using a CSV file as presented in the following picture.

  1. Prepare the CSV file.

    1. Columns in the file are separated by comma.
    2. The first row of the file must contain the headers of the columns. These correspond to the machine names of the columns of the Lookup Table.
    3. The order of the columns is not relevant.
  2. Download the existing content of the Lookup Table as CSV file, if needed.
  3. Choose the file to be uploaded.
  4. Select whether the existing content of the Lookup Table should be removed before uploading the CSV file.
  5. Upload the selected CSV file.


Platforms is legacy support and refers to the platforms on which your application runs on. For example, iOS, Android, or Web.

The current best practice to include Platform information to your metrics is to create an Application per Platform (e.g. My App - iOS).

If you track events from a user in platform A, and then track events with the same user id in platform B, those will be considered different users. If you wish to track your users across different platforms, they need to have the same UID, the om_platform parameter should be used to idenfity the platform of the user, and all the data should to a single Application (with API keys per Environment).

Service Status

Access to reports on Omniata's Event API and Channel API status.

User Management

See the separate section on this.

Organization Settings

Allows you have an option to change the organization name showed in the panel. In addition, you have an option to choose an icon for the organization.

This article was last updated on February 25, 2016 00:14. If you didn't find your answer here, search for another article or contact our support to get in touch.