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?

First time visits

View all one-time visits (within a 24 hour period). This specific api call is turned off by default, please contact support@opentracker.net to turn this api call on.

API Usage

This API produces a json array. Use this URL to perform GET or POST requests. Visits can also be retrieved based on a visit_id, and/ or a machine_idx.

Parameters

One or more of the following parameters are required:

filterByMachineId Display data for these machine ids. Machine id is a unique identifier of each visitor. Default is all machine ids.
filterByVisitId Display data for these visit ids. Visit id is a unique identifier of each visit. Default is all visit_ids.
from Find all visits from the specified unix timestamp. Default is all unix timestamps.
to Find all visits up to the specified unix timestamp. Default is all unix timestamps.
offset The starting point from which records will display. Default is [0] (most recent chronological event).
limit The maximum number of records to be displayed in the output. Default is [40]. The maximum is 10,000.
login Your opentracker login email. Default is [demo@opentracker.net]
password Your password.
ticketId A ticketId can be used to provide credentials with an expiring token. A ticketId can be used instead of a login/ password combination. Further information can be found here. Default is [demo123]
site The site for which to display data. Default is [www.opentracker.net].
locale The locale parameter is an identifier for a particular combination of language and region (e.g. en_US) and determines the format of the data returned. Default is [en_US]. A list of locales can be found here.
ignoreLocale Display columns without language translation. [false]|true.
dataType The dataType parameter determines the format of the data returned. Values can be [json] | html | jsondatatable | jsonjqgrid
dateFormat The dateFormat parameter determines the format of dates returned. An example is dateFormat=yyyy-dd-MM. The syntax can be found here.

-------------
usecase0: i'm looking for the last 40 (limit) visits of people who are visiting for the first (the first session is < 24 hours ago) -> one index (session table) -> . -> last 40 sessions * bucket issue needs to be addressed, buckets are indexing the session cf (table).
-------------
-------------
usecase1: i'm looking for a machine id's visits always for a site 40 (limit) -> one index -> .123142.* @-> x sessions (no bucket issue, immediately get from sessions cf (table)).
usecase2: i'm looking for a machine id's visits one year ago -> one index -> .1234341.2009* @-> sessions
-------------
-------------
usecase3: i'm looking for a visit_id for a site -> one index -> .123142 -> session column family (table).
-------------
-------------
usecase4: i'm looking for a machine_id with this visit_id -> not available query
-------------
-------------
or deprecate offset, and just use next tokens. so implement a next token.
offset: we just iterate through. eg offset = 300, limit = 100 -> we need to iterate through first 301 keys, and use 301 - 400, preferably no memory problems = memory / key size = iteration size. 
-------------