Concepts & Definitions

TrackZero allows you to store analytics data related to your product usage and enable your customers/partners/users to use TrackZero for all of their Business Intelligence and reporting needs. We have built this platform because we know how difficult it is to predict the needs of your users.

In this document, we will go through some definitions so you would understand how TrackZero works.

Account #

An account is the account you create to access TrackZero yourself, this is your organization account. Using the account’s email & password, you can manage your subscription and API Keys.

API Key #

A secret code used to grant your application access to TrackZero and thus perform the tasks that needs to be performed. Like storing/deleting data, creating/deleting analytics spaces and many others.

Analytics Space #

Analytics spaces are areas of data separation, it allows you to create boundaries between the data you send to TrackZero. Typically, each of your partners will have their own Analytics Space where all of their data resides. TrackZero allows each of your partners to access their data and their data only using Analytics Spaces Session.

Entity #

An entity is a record of information which contains data. Think of it like an object, it has properties attached to it (Attributes) and these attributes contain values. For example, let’s take the Entity “Product”, the product has a name, price, color, maybe stock quantity…etc. TrackZero doesn’t limit you to specific attributes. You design your attributes based on your customer needs.

These attributes have both “Key” (the attribute name) and Value “The value of the attribute”. For example, the Entity “User” will have the attribute “Age” which has the “Value” of “43”. The values can be of any of the following types: String, Number (With or without decimal point), Boolean and DateTime (Including ISO 8601).

In addition to Attributes, TrackZero supports “Referenced Attributes”. Which are similar to attributes but instead of holding a specific value like name or price, they link to another entity with all of it’s attributes.

Let’s take an example of the “Order” entity. The order entity will have it’s own attributes like “Order Time”, “Total Value” and will also have Referenced Attributes to the “User” using the “Ordered By” attribute. And to multiple “Products”.

This means you don’t have to duplicate data in TrackZero. Only send the changes in data, and everything get’s updated.

Any Entity must have 2 important attributes, “Type” and “Id”. The type represents the direct type of the entity like “User”, “Employee”, “Customer”, “Product”, “Order”…etc. While the “Id” is the unique identifier for this specific type. The “Id” attribute can be of any of the following types: STRING, INT, LONG, GUID/UUID.

One important feature of TrackZero is the ability to pin an entity to a physical location (Geo Translation). This allows the user to visualize data on a map. All you need to do is to specify the latitude and longitude and TrackZero will automatically translate these into a Country/State Mapping.

Analytics Space Session #

Each Analytics Space data can be accessed using an Analytics Space Session. A session is valid for a specific period of time. When you generate a new Analytics Space Session, you will get a session key and a URL. The URL can be used to redirect the users to TrackZero Spaces site where they can run BI on the data in that space.

Conclusion #

Integrating with TrackZero is quite simple and easy once the above concepts are understood. More details can be found in the next documentation items. So please continue reading and remember we are always here to help.