How To Set Up Woopra Schema & Customer Profile Editing

If you’ve been using Woopra, you must be familiar with the Custom Visitor & Event Properties. For those of you who aren’t yet, Woopra supports two types of data about your customers: Visitor Data and Event Data. Visitor Data is properties about your visitor that stick to their profiles (e.g. Name, Company, Email, Phone, Subscription Value, etc) and Event Data is types of actions supported with extra meta data (e.g. signup, click, login, payment etc). You can read our documentation to learn more about sending Custom Visitor Data and Custom Event Data.

Important: The email address is used as the unique identifier for your customers, which allows you to aggregate their visits from multiple browsers and devices into one profile. If the email address is not provided, Woopra will fall back to tracking the visitor by cookies.

Introducing Schema

Woopra Schema are used to organize your custom information in a readable way and to tell Woopra how this information should be read and displayed. Schema can be accessed and edited by administrators under Settings (the Settings button is in the website’s sidebar).

Visitor Info Schema

The Visitor Info Schema defines the fields that are critical for your business and that you want to show on every profile. Of course, the rest of the properties for every visitor will show as extra properties, but the properties in the Schema will always show regardless of whether or not they’re defined for that visitor. By default Woopra has enabled three fields in the visitor schema that cannot be deleted and are useful for every business (name, email and company). It’s up to you to customize this schema and add additional fields that make sense for your business.

Action Schema

Action Schema defines the types of visitor actions that you’d like to track. Every action consists of a name and multiple meta data that support this action. For example, if you’re tracking the action “payment”, you may want to include “amount”, “package type”, etc.

By defining an action in the schema, you will also be able to write a template that holds any profile wide visitor data or specific action data. For example, a payment template can looking similar to the following: ${} paid ${action.amount} for ${action.package} which makes the payment action readable by your colleagues. You will also want to add an icon for every type of action to help you spot specific actions on the fly as you’re viewing a visitor’s profile.

Editable Profiles

As many of you have noticed, we have removed the Tagging functionality in the last update to replace it with a new solution that works well with the new Customer Profiles. Now, you can edit any custom visitor property from within the app, giving you even greater capability than was available with the Tagging feature.

Let us know how you’re using Woopra’s Schema to customize Customer Profiles for your business.

Leave a Reply