All

Writing data

• Docs
  • Inserting data [general]
    • Inserting event data
    • Users, sessions & events
    • Adding properties
    • Reserved properties
  • Opentracker Implementation
    • Javascript implementation
    • Tracking native iOS app events
    • Android app tracking
    • Inserting Raw Data with a url

Reading data

• Visits
  • classic
    • visits
    • visits first time
    • visits returning
    • visits referrer
    • visits searches
    • visits exit link
    • unique visitors
    • browsers
    • platform
    • source
    • goal
    • ip number
    • isp/ company / org.
    • pageviews
    • geo location
  • Next generation
    • sessions (nt)
    • sessions by user (nt)
    • event (nt)
• Trends
  • trends
  • hourly trends
  • pages
  • summary
• Top lists
  • pages
  • paths
  • referrers
  • search engines
  • search terms
  • entry pages
  • exit pages
  • exit links
  • properties
• Technical data
  • OS/ platform
  • browsers
  • display color
  • display resolutions
  • routers
  • domains
• Geo-location data
  • companies
  • isps
  • country /region /city
  • continent
  • sub-continent
  • postal codes
  • area codes
• Management
  • find user
  • add user
  • find server
  • find server (xml)
  • Get timezone for site
  • check if site exists
  • generate ticketId
  • is valid ticket?

Inserting event data the basics

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.

What are events?

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.

What about session and users?

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.

Adding more details to your events by using properties

A property is a piece of information you can send with your events. Properties have a name and a value.
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 screen height.
Click here for a full list of properties and detailed explanations.

What do I need to do?

We invite you to use this for the technology of your choice, we have created multiple libraries so you can achieve maximum output with minimum effort. The SDKs are geared towards JavaScript (Web browsers), Objective C (iPhone) and Java (Android), and a general url-based method for the Internet of all things.

Javascript

We have a javascript library that has been intensively used and updated with improvements for over 10 years.
Javascript implementation

iOS/ iPhone/ iPad/ iPod /AppleTV

We have a advanced SDK for support for Apple Inc. devices.
iOS implementation

Android

We have a advanced SDK for support for Android powered devices.
Android implementation

Internet of things (IOT)

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.