Note: This documentation is for Opentracker's events engine, please contact us if you think you need an upgrade.

Using properties with javascript

Introduction

Opentracker enables you to customize your data with properties. A property is a piece of information that give events, sessions and users meaning. You can add as many properties as you need.

Info For more detailed information please see adding properties

Examples of properties

The following properties are examples of what can be sent to Opentracker's event engine.

email

Tag users by assigning them a name or custom id

example

map.put("email", "user@mysite.com");

Visible in:

  • Visits/Users Online: user profile hover, user profile expanded, column selector
  • Click/Event stream: user profile
  • Top Events

video

Currently only visible in visits/ users online column selector

If a visitor/ user watched a video

example

map.put("video", "Product presentation");

Visible in:

  • Visits/Users Online: user profile hover, user profile expanded, column selector
  • Click/Event stream: user profile
  • Top Events

audio

Currently only visible in Visits/Users Online column selector

If a visitor/ user listened to a audio file

example

map.put("audio", "Podcast week 12");

Visible in:

  • Visits/Users Online: user profile hover, user profile expanded, column selector
  • Click/Event stream: user profile, separate event with icon for easy identification
  • Top Lists: audio files

download

Currently only visible in Visits/Users Online column selector

If a visitor/ user downloaded file

example

map.put("downloadType", "pdf");
map.put("downloadName", "spec sheet");

Visible in:

  • Visits/Users Online: user profile hover, user profile expanded, column selector
  • Click/Event stream: user profile, separate event with icon for easy identification
  • Top Lists: audio files

print

Currently only visible in Visits/Users Online column selector

If a visitor/ user used a print button on your site

example

map.put("print", "page12");

Visible in:

  • Visits/Users Online: column selector
  • Click/Event stream: separate event with icon for easy identification
  • Top Lists: printed pages

exit link/ destination/ ad

If a visitor/ user used a link or add, leaving your site

example

map.put("p", "3"); // required for identification of exit event
map.put("ms", "http://www.ibm.com/add-destination.html");

Visible in:

  • Users Online: column selector
  • Click/Event stream: serparate event with icon for easy identification
  • Navigation: Ads / exit links

Segments

Adding Custom segments is limited by your account type. See pricing page for details.

Opentracker allows you to specify custom segments so you can segment your data in the reporting interface. This will allow you to look at your data according to the segments you specify. You need to define your segment for each page-view/ event with our map functions.

You can add multiple segments for each event. There is a limit of 3 segments per event.

To activate your segments in the report drop-down, you need to add an exclamation mark (!) to the segment-name

example

map.put("section!", "frontend");
map.put("gender!", "male");

Visible in:

  • All reports based on Opentracker's events engine
  • Visits/ users online: column selector

Custom event url

Overwrite or replace the url that is recorded and shown in the interface

This url will also be used for generating thumbnails, if turned on.

example

map.put("lc", "http://my.domain.com/myurl.html");"

Visible in:

  • Visits/Users Online
  • Click/Event streams
  • Navigation: multiple reports

Initial load url

Javascript Modification

Use this to overwrite or replace the initial loading url that is recorded and shown in the interface

This url will also be used for generating thumbnails, if turned on.

The parameter ot_url should be appended to the script. The value should be a valid url (http://domain/path/file.html)

example

<script src="http://script.opentracker.net/?site=www.opentracker.net&ot_url=http://www.domain.com/path/filename.html"></script>

Visible in:

  • Visits/Users Online
  • Click/Event streams
  • Navigation: multiple reports

 

Requirements:

  • The Opentracker tracking javascript needs to be in the page and loaded before you submit the custom events.

Cookies:

For details on how to read Opentracker cookie data see here

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