Tracking Overview

As with any analytics tool, the data is only as good as what you put into it. Setting up Woopra properly from day one will lay the foundation for clean, organized and consistent analysis. Woopra is designed as a complete customer journey analytics tool that you can leverage to not only track a user's journey on your website, but also across multiple devices and platforms.

So how do we track in Woopra? Woopra employs the use of the Javascript Tracking API as a primary way to get data into Woopra from your website or product. The API code is loaded in the browser as the result of running the Javascript Snippet. This implementation is generally done by developers using any number of tools including the Javascript Tracker, for events on your website, server side SDKs for backend events, and HTTP Tracking API which accepts events from any source with access to http. The last way you will get data into your Woopra instance is by installing Apps in our integrations hub, which will allow you to bring in events and data from other services such as CRMs and email marketing tools.

It's important to understand the difference between the Snippet and the Tracker. The Snippet is a short simple function that should never need to be changed or be updated that loads the Tracker code itself from the Woopra servers. The Tracker Object itself is the javascript code that sends events into Woopra.

There are many ways to begin tracking in Woopra. The most common way is the client-side API. If you would like to get started with our technical documentation, please see our technical getting started page:

When you are using one of the tracking SDKs or APIs, there are some main concepts that you need to grasp and tasks to do to get going:

  • Installing your tracking code
  • Configuring your tracker
  • Tracking events and event properties
  • Tracking user properties

These tasks are completed differently depending on the SDK or API you are going to use to track your data.