The config function is used to tell the tracker which project you're tracking. It also allows you to set a number of options that can affect your default pageview tracking (woopra.track() No Args!!), the behavior, domains, and locations of cookies, how the ping works, etc.

The config function supports key/value singleton argument:

woopra.config("cookie_name", "my_business_cookie");

Or an object of keys and values:

woopra.config({
    download_tracking: true,
    outgoing_tracking: true,
    click_tracking: true
});

Auto tracking Configs

📘

Note on 'download_extentions'

The default list is: avi, css, dmg, doc, eps, exe, js, m4v, mov, mp3, mp4, msi, pdf, ppt, rar, svg, txt, vsd, vxd, wma, wmv, xls, xlsx, zip

If you override the default, you this stops using our default list. You can use our list and include others like:

JavaScript

woopra.config({
  domain: 'woopra.com',
  initialized: function () {
    woopra.config(
      'download_extensions',
      woopra.config('download_extensions').concat('xml')
    );
  }
});

Custom Button Click Tags

📘

When enabling 'click_tracking', this automatically tracks all button clicks. It's possible to add custom attributes to the button's HTML using data-woopra-<property name> in the code.

For example: data-woopra-hello="world"

Woopra will automatically pick up these attributes and send a new property 'hello' with the value 'world' with the button click event.

You can also track a custom button click event by using data-woopra="custom button click event" as well.

This will send a separate event to Woopra ('custom button click event') instead of sending the standard 'button click' event for that particular button.

Configuring your Tracker

The Woopra tracker can be customized using the config function. The config options have some defaults for normal website tracking and with the exception of "domain", can usually be left un-customized.

The tracker will not work, however without a domain which is your project name in Woopra.

Find the list of options below: