Hourly Trends

Display and analyse hourly trends in website traffic through time.

Display and analyse hourly trends in website traffic through time.

API Usage

This API produces a json array. Use this URL to perform GET or POST requests.


At least one of the following parameters are required:

date Calculate hourly trends from specified date entered as yyyy-MM-dd. Default is the current date.
unixTime Calculate hourly trends from specified unix timestamp. Default is current unix timestamp.
period Specify the trend period. Default is the 24 hours of the specified date

    • "x"h for hours, eg: period=6h will show 6 rows with hourly trends
    • "x"d for number of hours in x days, eg: period=2d will show 48 rows with hourly trends (24 hours for each day X 2)

timezone The timezone used. Use this option if more than one timezone is being recorded, by default the site's defined timezone is used.
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.
segment This is the property field based on which you want to segment the data. By default there are no segments. You can find more information here.
filter You can choose to see no segments [none] (default), see all segments showAllSorts, or by specifying the name of the segment.
site The site for which to display data. The 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.


To calculate the hourly trends of today to the website www.opentracker.net for the user "demo@opentracker.net" with password "demo123":
HTTP GET/ POST: trends_hourly.jsp?login=demo@opentracker.net&password=demo123&site=www.opentracker.net&trend=hourly

To calculate the hourly trends between the time-range of 4 days from 2023-12-11 and display in html:
HTTP GET/ POST:trends_hourly.jsp?trend=hourly&date=2023-12-11&period=4d


This last example returns a json array with 'n' entries starting from the specified date and period formatted as:

{ "resultsList": [
"hour":"23:00 - 23:59 (Mon)",
"visit time (avg)":"01m 31s",
"first time visitors":"106",
"single event sessions":"47",
"hour":"22:00 - 22:59 (Mon)",
"visit time (avg)":"01m 47s",
"first time visitors":"140",
"single event sessions":"74",
"hour":"21:00 - 21:59 (Mon)",
"visit time (avg)":"01m 38s",
"first time visitors":"128",
"single event sessions":"71",
"hour":"20:00 - 20:59 (Mon)",
"visit time (avg)":"01m 54s",
"first time visitors":"174",
"single event sessions":"88",
"hour":"19:00 - 19:59 (Mon)",
"visit time (avg)":"02m 28s",
"first time visitors":"280",
"single event sessions":"187",
"hour":"18:00 - 18:59 (Mon)",
"visit time (avg)":"01m 38s",
"first time visitors":"201",
"single event sessions":"95",
"hour":"17:00 - 17:59 (Mon)",
"visit time (avg)":"01m 34s",
"first time visitors":"238",
"single event sessions":"97",
"hour":"16:00 - 16:59 (Mon)",
"visit time (avg)":"02m 15s",
"first time visitors":"250",
"single event sessions":"107",
"hour":"15:00 - 15:59 (Mon)",
"visit time (avg)":"01m 58s",
"first time visitors":"234",
"single event sessions":"113",
"hour":"14:00 - 14:59 (Mon)",
"visit time (avg)":"01m 56s",
"first time visitors":"212",
"single event sessions":"104",
"hour":"13:00 - 13:59 (Mon)",
"visit time (avg)":"01m 25s",
"first time visitors":"173",
"single event sessions":"92",
"hour":"12:00 - 12:59 (Mon)",
"visit time (avg)":"02m 14s",
"first time visitors":"216",
"single event sessions":"87",
"hour":"11:00 - 11:59 (Mon)",
"visit time (avg)":"02m 25s",
"first time visitors":"226",
"single event sessions":"100",
"hour":"10:00 - 10:59 (Mon)",
"visit time (avg)":"01m 59s",
"first time visitors":"199",
"single event sessions":"92",
"hour":"09:00 - 09:59 (Mon)",
"visit time (avg)":"02m 10s",
"first time visitors":"187",
"single event sessions":"93",
"hour":"08:00 - 08:59 (Mon)",
"visit time (avg)":"02m 18s",
"first time visitors":"189",
"single event sessions":"93",
"hour":"07:00 - 07:59 (Mon)",
"visit time (avg)":"01m 53s",
"first time visitors":"172",
"single event sessions":"94",
"hour":"06:00 - 06:59 (Mon)",
"visit time (avg)":"02m 33s",
"first time visitors":"161",
"single event sessions":"88",
"hour":"05:00 - 05:59 (Mon)",
"visit time (avg)":"02m 42s",
"first time visitors":"172",
"single event sessions":"96",
"hour":"04:00 - 04:59 (Mon)",
"visit time (avg)":"02m 27s",
"first time visitors":"163",
"single event sessions":"103",
"hour":"03:00 - 03:59 (Mon)",
"visit time (avg)":"01m 49s",
"first time visitors":"135",
"single event sessions":"84",
"hour":"02:00 - 02:59 (Mon)",
"visit time (avg)":"01m 39s",
"first time visitors":"114",
"single event sessions":"60",
"hour":"01:00 - 01:59 (Mon)",
"visit time (avg)":"01m 55s",
"first time visitors":"100",
"single event sessions":"47",
"hour":"00:00 - 00:59 (Mon)",
"visit time (avg)":"01m 48s",
"first time visitors":"106",
"single event sessions":"41",
"visit time (avg)":"0",
"single event sessions":"2,153",
"first time visitors":"4,276",


If errors are encountered, the first encountered error will be returned of form "Error: exception: message

Error: java.lang.RuntimeException: Login/ site combination is not valid

We would love to hear your feedback. Please use the facebook comment box below