There are two types of custom data:
- Action Data – Custom actions are tracked by the built-in events installed automatically when you install an AppConnect app, or by adding code to send Woopra data on specific behaviors that a user might take while on your site or app, such as “signup”, “play video”, “add product to cart”, etc.
- Visitor Data – Custom visitor data can be any type of information you want to track about your customers. For example, when identifying your customers by sending their email addresses to Woopra when they sign up, you may also want to send Woopra which company they are coming from, what their title or position at their company is, and so on.
Tracking Action Data
Action 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 and reports.
To get the full value out of Woopra, it is imperative to send additional action data from AppConnect or custom Action tracking. This action data allows you to analyze critical customer behavior that is immediately relevant to your business across your various touchpoints.
Once tracking action data, you can immediately 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 actions
- Funnel Goals – You will be able to use the actions you are tracking as goals in your funnels
- Retention Reports – You will be able to use the actions you are tracking as initial and secondary events in Retention Reports
- And much more
Properties are built in to AppConnect Apps, but when you set up custom tracking to send actions to Woopra, you should also consider sending any properties attached to the event. These properties serve to describe the event much more richly than just the action itself.
For example, if you are tracking a “payment” action, you can send properties that describe the payment event, such as “amount” and “product name”. These two properties tell you the amount the customer paid and exactly which product they purchased.
We recommend that you immediately install any apps for products that you use, to monitor user activity on those apps. To begin thinking through the actions that you might want to set up tracking code to monitor however, We recommend starting by considering one or two actions that can occur on your site or application which indicate an engaged user. For E-commerce sites, this might be a purchase. For games, you might be interested in visitors that install your game, and begin to play. SaaS companies might want to consider those users who sign up for a trial, and then convert to a paid subscription.
Whatever your actions, think through the 3 or 4 key steps that are essential to successfully complete this event. These are the actions that you’ll want to set up tracking code to monitor.
Defining Action Data in Schema
Once you are tracking custom events, Woopra will automatically create default schema the moment the action is detected. You should visit the default schema to customize your definition, action type and aggregation options for the action being sent. By defining these details 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.
Also imperative to get the full value out of Woopra, you should identify your visitors using custom visitor data. Custom visitor data allows you to track any kind of customer information that is important to your business. Start by identifying visitors by email addresses whenever they sign up if at all possible, as this will give you more accurate data about each individual’s behavior. Additionally, many of AppConnect’s apps require visitors to be identified by email in order to assign the actions to the correct profile.
Beyond this, you can integrate customer account information, or any other critical customer data that you would like to analyze and use as criteria for segmentation.
Once you start identifying your customers in Woopra, you will see any information set to ‘Group’ aggregation in your schema in your customer profiles, and you will be able to use any custom visitor data you send to Woopra throughout Woopra’s features as filtering options, allowing you to segment based on this criteria. Any properties set to ‘Group’ Aggregation will also pre-generate analytics reports.