The next step is to identify users, install any relevant one-click integrations and begin tracking custom actions that are relevant to your business. This includes actions such as signups, payments, subscription updates, product feature usage, video views and so on.
There are two types of custom data you can track:
- Action Data - Custom actions are tracked by the built-in events installed automatically when you install an Integrations 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.
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. You can do this by installing the one-click integrations relevant to your business or through custom Action tracking. This action data allows you to analyze critical customer behavior that is immediately relevant to you across your various touchpoints.
Once tracking action data, you can immediately use it throughout Woopra’s features. For example:
- Segmentation– The custom actions you are tracking will become filtering options, allowing you to segment based on this criteria
- Journey Steps- 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
Defining Action Data in Your Schema
Once you’re tracking custom actions, Woopra will automatically create a 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.
To get the full value out of Woopra, you should also identify your visitors using custom visitor data. Custom visitor data allows you to track any kind of customer information that’s important to your business. Start by identifying visitors by email address whenever they sign up if at all possible, as this will give you more accurate data about each individual’s behavior. Additionally, many of our Integration apps require visitors to be identified by email in order to assign the actions to the correct profile.
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.
Beyond this, you can integrate customer account information or any other critical customer data that you would like to analyze and use this as criteria for segmentation.
Once you start identifying your customers in Woopra, you will see the information set to the ‘Group’ aggregation in your schema in the customer profiles. You will also be able to use any custom visitor data you send to Woopra throughout Woopra’s features, such as in the filtering options, allowing you to segment based on this criteria. Any properties set to ‘Group’ Aggregation will also pre-generate analytics reports.