Custom Actions and Visitor Data
Woopra has three data scopes or types of data that it tracks: event or action data, session data (aka visit data ), and visitor data .
After installing the basic Woopra Snippet, Woopra will automatically track pageview event data and visit data such as IP address, location, and even campaign data.
This section will cover tracking custom actions and visitor data that are relevant to your business. This includes actions such as signups, payments, subscription updates, product feature usage, video views and so on. This also includes visitor data such as emails and names.
Please see our technical documentation for custom actions and visitor data. As well as a more in-depth guide on what to track for eCommerce and SaaS.
Tracking Action Data
What: Custom 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.
Why: This data can be invaluable to your business. Knowing where user drop off occurs or how many users are clicking on a specific blog can greatly influence site improvement and user engagement. This action data allows you to analyze critical customer behavior that is immediately relevant to you across your various touchpoints. Data driven decisions can make or break a business — tracking actions in Woopra is imperative to get you the data you need.
Next: Once you're tracking action data, you can immediately use it throughout Woopra’s features. You can use this data to create various reports(report links), use it to filter customer segments, and even trigger automations. Woopra will automatically create “schemas” the moment the action is detected. Schemas are used to tell Woopra how to read and aggregate the data. More info can be found in our Schemas section (link).
Tracking Visitor Data
What: Visitor data allows you to track visitor information that is important to your business. This includes tracking visit durations and acquiring identity information such as names and emails when they sign up. Visitor properties are known in different systems as contact or user properties or fields. They are very simply, data describing properties of a particular person. In Woopra, an email property is considered a unique identifier for the visitor. If you don’t specify the email property for the visitor, Woopra will automatically fall back to the cookie as a unique identifier.
Why: To get the full value out of Woopra, you should identify your visitors using custom visitor data. You can use this data for campaigns or understanding user behavior. For example, knowing what companies your users are working for and which campaigns are driving your signups can save you time and money.
How: In order to track custom visitor data, you must send it to Woopra by identifying users in the tracking code you place on your website. For more info please see our technical documentation on visitor tracking, or the specific SDK you wish to use. Additionally, you can start 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. Lastly, many of our Integration apps require visitors to be identified by email in order to assign the behavioral data to the correct profile.
Next: Once you are tracking visitor data in Woopra, you can use this data throughout Woopra’s features. You can use this data to filter or segment users based on selected criteria, create detailed People reports, and create profiles that track a user's journeys through their engagement with your product. Similar to Action data, Woopra will automatically create “schemas” for these events as well.
Updated almost 4 years ago