Track Events in Workevo

Record the specific actions a user takes in your product - tracking first, last time, and the total number of times a user does something.

You can track the actions your contacts take as events, both while logged into the product and while visiting your website.

Events that record the first, last time, and the total number of times a contact performed an action. When you start tracking events in Workevo, you can filter your contacts and send them automated messages based on their actions, including:

  • When they have done an action a certain number of times.

  • The first time they acted.

  • When it was "X days" since the last time they took action.

You can track the actions that the logged-in contact and the logged-out visitor are performing. For example, you can track:

  • The last time the contact performed an action. For example, the last time they exported PDF or visited your help center.

  • First time contacts choose a paid plan or use a discount code.

  • When contacts invite others to your service.

  • When (and what) someone ordered on your website.

Important: The events described here are only examples and may require assistance from an engineer or developer to perform. 👌 It's easy with the Workevo JavaScript API, REST API, or one of our mobile SDKs.

These are just some of the ways you can use events to better segment contacts based on their actions and send both visitors and users messages by behavior.

Note: Events under 90 days in a timeline can only be viewed, both in user-profiles and via the API. However, you can still filter and message users based on events older than 90 days. This will not affect the first/last dates that occur if they were more than 90 days ago.

Events versus custom attributes

Custom attributes are the data you track about your contacts, for example, how many projects they have created in your product. That is a unique value about a piece of information.

Events are information about what your customers do and when they do it, for example, the first time they created a project and when they most recently created a project.

Check out this article for more details on when to use custom attributes versus events.

Filter and message based on events

By filtering your contacts based on events, you can see:

  • The contact has created more than two reports.

  • User-created their first report more than five days ago.

  • All pages lead visitors before registering.

  • The most massive contact of specific features in your application.

Or, with event filters on your automated messages, you can target:

  • Visitors have added a product to their cart, but have not been tested.

  • Visitors have downloaded your white paper.

  • The visitor encountered an error when submitting the form on your website.

  • Contacts have never used a feature, encouraging them to try it out.

You can combine these rules with some standard Workevo filters like the "Last seen" filter if you want to send a message to a more specific set of active customers.

Note: It is currently not possible to filter your guests based on event metadata or include it in messages.

More ways to use events

You can capture many types of activities in Workevo by events.

1. Upgrade the subscription

In this example, a user changed their subscription from Starter to Dynamite Pro. You can think of it as a single event, like this:

You can also add context to the event by tracking some metadata with it, such as:

  • New plan name

  • Price new plan

  • Name of the plan in advance

  • Price plan in advance

  • Date of change

You can use this event to send automated messages to thank contacts for the upgrade.

2. Use product features

In this example, the contact has used the new mail feature. By following this type of event, you can conduct product research on new mail features and contact your contacts to learn things like "what works well?" and "what could be improved?".

3. Purchase

In this example, you recorded that contact bought a video game. This will allow you to send a cross-selling message, or a thank you to the contact. Also, note that a purchase has occurred, you will send some additional metadata:

  • The name of the item to be ordered.

  • A serial number links back to the retail site. We can use a rich link here because that allows us to display the number as the link title.

  • Time Order. You can send it as a timestamp and display an easy-to-read date for the event.

  • A number of orders. You can send the amount in dollars.

  • Invoice Stripe, we will create a link to it.

4. Viewed page

You may want to know which visitors viewed a particular page and how many times they viewed that page. For example, if visitors visit your pricing page multiple times, they may be interested in buying a subscription. Or, when a contact visits your confirmation page after a purchase flow, you may want to activate the thank you message.

If you want to filter the audience for a message for every visitor who has viewed your price page more than twice, you can, if you track your price page view as an event.