Tracker SDKs

Objectiv currently supports four trackers:

By default, Trackers automatically track:

And, while developing with Developer Tools, automatically validate:

  • ApplicationContext
    • must be present once in the Global Contexts of every Event
  • RootLocationContext
    • must be present once in the Location Stack of every Interactive Event
    • must be the first context in Location Stack
  • PathContext
    • must be present once in the Global Contexts of every Interactive Event

React Tracker​

The React Tracker is available via npm to be directly installed into your React application. It relies on React Context Providers for Location tracking and hooks for Event tracking. Tracking Locations with React Tracker is much easier and reliable than with BrowserTracker.

React Native Tracker​

The React Native Tracker is available via npm to be directly installed into your React Native application.

Browser Tracker​

The Browser Tracker is available via npm to be directly installed into your JavaScript Web application. It relies on the DOM for Location tracking and can be used with any framework relying on HTML templates or pre-generated content.

Angular Tracker​

The Angular Tracker is available via npm to be directly installed into your Angular application. It's a module built on top of Browser Tracker coming with a Directive to ease tagging in HTML templates.

Extensibility: Plugins​

Trackers are extensible through plugins. Each plugin can control when it's enabled, e.g. only if a Web environment is available. Some Plugins may be available only for a specific SDK.

These plugins are supported out of the box, and automatically enabled when the environment supports it:

application-context​

http-context​

  • adds a Global HttpContext to each Event
  • its remote_address attribute is enriched server-side by the Collector
  • included in React, Browser and Angular SDKs

path-context-from-url​

react-navigation​

root-location-context-from-url​