Goal introduction

What is a goal？ #

The “goal” is a feature in Ptengine that measures user behavior on your website on a per-user basis. These behaviors represent your website's operational objectives. By setting up trigger conditions such as membership registrations, inquiries, or successful purchases as Goals, you can use them as metrics to evaluate website business performance and operational conversion effectiveness.

Why "conversion" and "goal" counts may not match #

Ptengine Experience uses "Goals," while Ptengine Insight uses "Conversions" – both are features designed to analyze user behavior on your website. However, due to differences in their analytical purposes, they employ distinct measurement logic. Consequently, even with identical settings, measurement results may differ.

How to set up the goal #

Defining the goal:

Navigate to "Goals" via the Experience navigation menu.

Configure the Following Settings in Order:

• Goal Name: Set a clear and easily understandable name for your Goal.
• Goal Notes: Add notes to provide your team members with a quick understanding of the Goal criteria.
• Set Goal: Define your Goal using URL or Event triggers.
• Save: Click "Save" to finalize. The corresponding Goal data will then populate within the Goals tab.

How to Configure Goal Conditions:

URL-Based Conditions:

Define a Goal by specifying a particular page URL condition that you want to guide users towards, such as a "Thank You" page URL or a checkout completion page URL. When a user visits the specified URL, it will be counted as a Goal completion.

Tip: To specify multiple URLs, use "OR" to connect them.

If you have questions regarding URL/Regular Expression configurations, please refer to this article.

Event-Based Conditions:

Create Events in Insight:Visual Event Setup (Simple and Recommended): Configure events visually (refer to this article).Manual Setup: Configure events manually (refer to this article).Warning: Events configured in Insight with a collection count of less than 1 will not synchronize to Experience.

Difference Between Goals in Reports and Overall Goals: #

Goals under the "Goals" tab are used to track general user behavior, while Goals in Experience reports are used to validate the effectiveness of a specific Experience. Therefore, their measurement definitions differ:

Overall Reports (Goals Tab): Count the total number of users who achieve the Goal.Experience Reports: Count the number of visits that achieved the Goal within visits that viewed or clicked on that specific Experience.

Example Setup:

Tag Goal (under Goals tab): Reaching the checkout page.Experience X Goal: Reaching the checkout page (same as Tag Goal).

Based on the above setup, if the following visits occur: Overall Goals will count the total number of users reaching the checkout page, resulting in a count of +2. However, the Experience report Goals will only count conversions attributed to the Experience, thus recording a count of +1.

Detailed User Visit Behavior Examples

- First Visit: Experience A was displayed, then user reached the checkout page.
- Second Visit: Experience A was displayed again, then user reached the checkout page.

- First Visit: User first reached the checkout page, then interacted with the Experience.
- Second Visit: User only reached the checkout page without interacting with the Experience.

- Fifth Visit: User did not interact with the Experience and did not reach the checkout page.

Measurement Results:

Overall Goal Data (Goals Tab): 2 (User A, User B)Experience X Report Goal Data: 1 (User A)