Goal Definition Guide for Templates

Creating a dashboard from a template requires you to have some of your important goals defined. Below, you can find a guide on defining each goal.

If there is a goal you don’t have or you want to skip, feel free to do so. However, keep in mind that missing goals will be removed from reports, and a whole report may be removed from the dashboard if its goal requirements are not met.

View Content Goal

Define a view contains goal with your blog URL schema.

For HockeyStack, since our blog URLs are all hockeystack.com/blog/post-name, we define the goal as:

view contains /blog/

If our URL schema was blog.hockeystack.com/post-name, we would instead integrate blog.hockeystack.com as a connected domain and then define the goal as:

view contains blog.hockeystack.com /

Sign Up / Book Demo Goal

Some businesses let users sign up by themselves, and some require a meeting with sales. Depending on what method you use, find a button on your website that matches the desired signup or demo booking action, and define a click with selector or click with text goal.

Activation Goal

To define this goal, you first need to identify what your activation action is. An activation event is defined as the action that a user takes to be able to use your product. For HockeyStack, the activation event is the customer integrating our code to their website.

Next, you should find a button associated with this event. For HockeyStack, this is the Test Integration button coupled with viewing the dashboard. If there is no such button for you, you can use a custom goal.

Paid Conversion Goal

When someone signs up with your platform, it usually isn’t a paid conversion, so we need to track a different event for it. While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your payment provider (you can do so from your domain settings). After you receive your first paid conversion, a “Subscription Created” custom goal will emerge, which you can use to define the paid conversion goal.

Expansion Goal

While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your payment provider (you can do so from your domain settings). After you receive your first expansion, a “Subscription Updated” custom goal will emerge, which you can use to define the expansion goal with its “update_type” property set to “expansion”

Subscription Payment Goal

While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your payment provider (you can do so from your domain settings). After you receive your first subscription payment, a “Payment Received” custom goal will emerge, which you can use to define the subscription payment goal with its “recurring” property set to “true”.

Churn Goal

While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your payment provider (you can do so from your domain settings). After you receive your first churn, a “Subscription Cancelled” custom goal will emerge, which you can use to define the churn goal.

Feature Usage Goals

Feature usage goals usually stem from certain button clicks or page views on your UI. At HockeyStack, for example, we have a goal called “Created a Goal” which is tied to the Define Goal button in the dashboard. You should identify important features you want to track on your product, and define all of them as goals.

Generic Activity Goal

The generic activity goal is used to track active users, and it should include all signed-in activity. Generally, this is a view contains goal with your product URL schema. HockeyStack’s in-product URLs always start with /dashboard/, so we define the generic activity goal as:

view contains /dashboard/

If our URL schema was app.hockeystack.com/page, we would instead integrate app.hockeystack.com as a connected domain and then define the goal as:

view contains app.hockeystack.com /

Support Request Goal

While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your support provider (you can do so from your domain settings). After you receive your first support request, a “Message Sent by User” custom goal will emerge, which you can use to define the support request goal.

Agent Response Goal

While this goal can be defined by a button click on your UI, it is most easily defined by integrating HockeyStack with your support provider (you can do so from your domain settings). After you receive your first agent response, a “Message Sent by Operator” custom goal will emerge, which you can use to define the agent response goal.

Meeting Goal

This goal is most easily defined by integrating HockeyStack with your CRM (you can do so from your domain settings). After you log your first meeting, a “Meeting” custom goal will emerge, which you can use to define the meeting goal.

Contact Creation Goal

This goal is most easily defined by integrating HockeyStack with your CRM (you can do so from your domain settings). After you create your first contact, a “Contact Created” custom goal will emerge, which you can use to define the contact creation goal.

Opportunity Creation Goal

This goal is most easily defined by integrating HockeyStack with your CRM (you can do so from your domain settings). After you create your first contact, a “Deal Created” or “Opportunity Created” custom goal will emerge, which you can use to define the opportunity creation goal.

Email Sent Goal

This goal is most easily defined by integrating HockeyStack with your email marketing provider (you can do so from your domain settings). After you send your first email campaign, an “Email Sent” custom goal will emerge, which you can use to define the email sent goal.

Email Opened Goal

This goal is most easily defined by integrating HockeyStack with your email marketing provider (you can do so from your domain settings). After you receive your first email open, an “Email Opened” custom goal will emerge, which you can use to define the email opened goal.

Email Link Clicked Goal

This goal is most easily defined by integrating HockeyStack with your email marketing provider (you can do so from your domain settings). After you send your first email campaign, an “Email Link Clicked” custom goal will emerge, which you can use to define the email link clicked goal.