A decade ago we started measuring page-views generated by mouse-clicks. The definition of what we track has now expanded. We track a broader range of signals which we call events. Examples are a page-view, playing a movie, making a tweet, getting a download, or an ajax call. Other examples include the temperature measured by a sensor, a purchase at a grocery store or my heart rate while jogging.
Any activity that takes place on an Internet-connected device can be defined as an event. This web-service securely tracks, monitors, and generate real-time analytical reports for any device connected to the Internet.
Opentracker defines an event as any signal sending a http(s) request to our servers for collection.
An event can represent any type of activity.
At Opentracker we group the events we receive into sessions and users.
A session is made up of a series of events.
A user is made up of a series of sessions. A single user can generate multiple sessions.
The following diagram illustrates this:
For more in depth info see Users, Sessions and Events explained.
A property is a piece of information you can send with your events. Properties have a
name and a
An example of a property is the
title of this webpage and its value
Opentracker Web API - Inserting
event data. A property describes an event, giving it meaning.
You can add as many properties to an event as you want.
Some property names have been reserved with pre-defined meanings. Examples include
ti for title and
sh for the
Click here for a full list of properties and detailed explanations.
We have a advanced SDK for support for Apple Inc. devices.
We have a advanced SDK for support for Android powered devices.
By implementing this API, you can securely track, monitor, and generate real-time reports for any device connected to the Internet.
Please read about the Inserting events with a url page if you would like to
make use of this technology.