Have a question?

Custom Events & Visitor Data

Overview

Woopra tracks certain things out of the box, like pageviews and customers’ IP addresses. However, Woopra is designed so that you may also track actions and information that are specifically important to your business, such as signups, payments, and customers’ email addresses. These pieces of data are called custom data because they are customized by you in your Woopra Javascript tracking code.

Please note that in order to track custom data, you will need basic knowledge of Javascript and the language(s) that your site is programmed in (e.g. Ruby).

There are two types of custom data:

  • Custom Event Data – Custom events are actions like “signup”, “play video”, “add product to cart”, etc.
  • Custom Visitor Data – Custom visitor data can be any type of information you want to track about your customers. For example, you may want to identify your customers by sending their email addresses to Woopra when they sign up, or you may want to send Woopra which company they are coming from.

Custom Event Data

Custom event data allows you to track any kind of action that is important to your business. For example, you could track “signup”, “play video”, “payment”, and any other critical actions that you would like to analyze and use as criteria for segmentation.

In order to track custom events, you must send them to Woopra in the Javascript tracking code you placed on your website. For further instructions on how to do this, please see the Javascript tracking setup tutorial.

If you want to get the full value out of Woopra, it is imperative to track custom event data. Custom event data allows you to analyze customer behavior that is immediately relevant to your business.

Once you track custom event data, you will be able to use it throughout Woopra’s features. For example:

  • Segmentation – The custom events you are tracking will become filtering options, allowing you to segment based on this criteria
  • Analytics Reports – Woopra will automatically pre-generate analytics reports based on your custom events
  • Funnel Goals – You will be able to use the custom events you track as goals in your funnels
  • And much more

Sending Properties

When you send a custom event to Woopra, you may also send certain properties attached to the event. These properties serve to describe the event.

For example, if you are tracking the custom event “payment”, you can send properties that describe the payment event, such as “amount” and “product”. These two properties tell you the amount the customer paid and which product they purchased.

To learn more about how to send properties with your custom events to Woopra, please see the Javascript tracking setup tutorial.

Keep in mind that each business will have a unique set of custom events it should track, but this spreadsheet, which is organized by type of business, will give you a good starting point.

Defining Custom Event Data in Schema

Once you are tracking custom events, you will need to define the events in your schema. By defining the events in your schema, you are essentially telling Woopra how to read and aggregate the data. For more information on defining custom events in schema, please see the schema tutorial.

Custom Visitor Data

Custom visitor data allows you to track any kind of customer information that is important to your business. For example, you could track visitors’ email addresses when they sign up, you can integrate customer account information, or any other critical customer data that you would like to analyze and use as criteria for segmentation.

In order to track custom visitor data, you must send it to Woopra in the Javascript tracking code you placed on your website. For further instructions on how to do this, please see the Javascript tracking setup tutorial.

If you want to get the full value out of Woopra, it is imperative to identify your visitors using custom visitor data.

Remember that the email property is considered a unique identifier for the visitor. If you don’t specify the email property for the visitor, Woopra will fall back to the cookie as a unique identifier.

Once you start identifying your customers in Woopra, you will see this information reflected in your customer profiles.

In addition, you will be able to use any custom visitor data you send to Woopra, such as your customers’ gender or age group, throughout Woopra’s features. For example:

  • Segmentation – You will be able to use the custom visitor data you are sending as filtering options, allowing you to segment based on this criteria
  • Analytics Reports – Woopra will automatically pre-generate analytics reports based on your custom visitor data
  • And much more

Defining Custom Event Data in Schema

Once you are tracking custom visitor data, you will need to define the data in your schema. By defining the data in your schema, you are essentially telling Woopra how to read and aggregate the data. For more information on defining custom visitor data in schema, please see the schema tutorial.

Now that you understand what custom events and visitor data are, it’s time to setup your Schema:

Setup your schema

Need any help? Contact our Data Jedis