Custom Event Goal in Zoho PageSense | Setup Guide & Event Tracking Implementation

Custom Event Goal


What is a Custom Event Goal?

A Custom Event Goal allows you to track specific user actions that cannot be measured using standard click-based or time-based tracking.

Unlike Element Click or Link Click goals, which track visible interactions, a Custom Event Goal tracks a JavaScript event that is triggered only when a defined condition is successfully completed.

Every time the defined event fires, PageSense records it as a conversion. Each visitor is counted once per goal, ensuring accurate and reliable reporting.

This goal type is ideal when the conversion:

  • Does not redirect to a new page

  • Happens after backend validation

  • Occurs within dynamic content

  • Requires confirmation before counting as success

When Should You Use a Custom Event Goal?

Use a Custom Event Goal when:

  • A form submission does not redirect to a thank-you page

  • A success message appears on the same URL

  • You want to track newsletter signups

  • You want to track webinar registrations

  • You want to track contact form submissions

  • A payment confirmation happens without page reload

  • You need to track success inside login areas

  • The conversion happens after backend processing

If your website does not change URLs after a successful action, Custom Event is the most accurate way to measure conversions.

Example Scenario

Imagine you have a contact form on: https://example.com/contact-us

When a visitor submits the form successfully, a “Thank You” message appears on the same page, but the URL does not change. Since there is no new destination page to track, Element Click or Link Click will not accurately measure real submissions. In this case, you add a Custom Event inside the form’s success function. When the form submission succeeds, the event triggers, and PageSense records it as a conversion.

Goals Dashboard Overview

When you open the Goals tab under the Track module, you’ll see a complete overview of all the goals created for your project. This view helps you quickly understand goal performance and manage tracking efficiently.
Here’s what each section shows:

  • Goal Name
    Displays the name of each goal, making it easy to identify what action is being tracked.

  • Status
    Indicates whether the goal is currently running or inactive.

  • Visitors
    Shows the number of visitors who were eligible for the goal during the selected time period.

  • Conversions
    Displays how many visitors successfully completed the goal action.

  • Average Conversion Time
    Represents the average time taken by visitors to complete the goal after landing on the page.

  • Created Date
    Helps you track when the goal was set up, useful for audits and performance comparisons.

  • Sorting and Filters
    Allows you to sort goals by name, visitors, conversions, average conversion time, or recently created goals for quicker analysis.

How to Set Up a Custom Event Goal

Step 1: Click New Goal
  1. In the Track module, click New Goal to start creating your goal.

  1. This opens the goal configuration setup.


Step 2: Choose Custom Event as the Goal Type
  1. Enter a clear and descriptive name for your goal. 
    Example: Zylker Custom
  1. From the list of available goal types, select Custom Event.

  1. Click Next to proceed.
Step 3: Define Pages to Track
  1. In this step, you define where the custom event may be triggered. These are the pages where the success action can occur.

  1. PageSense provides an Advanced option that gives you flexibility through 8 URL match types.


Below is the explanation of each: 


 URL Match Type
When to use
Example
What it tracks
Simple URL
When tracking a single static page
https://zylkerautomation.zohoecommerce.com/services
Only that specific page 
Exact URL
When the URL must match exactly
https://zylkerautomation.zohoecommerce.com/pricing
Tracks only the exact URL entered
URL contains
When tracking multiple related options
https://zylkerautomation.zohoecommerce.com/product
Tracks all URLs containing “/product”
Starts with
When tracking a section or a folder
https://zylkerautomation.zohoecommerce.com/blog/
Tracks all blog pages
Ends with
When tracking pages with a common ending
https://zylkerautomation.zohoecommerce.com/thank-you
Tracks any URL ending in ''thank-you''
Matches with
For flexible partial matchinghttps://zylkerautomation.zohocommerce.com/offer
Tracks URL matching similar patterns
Regex
For dynamic or complex URL structures
https://zylkerautomation.zohoecommerce.com/product/[0-9]+
Tracks product pages with numeric IDs
Page GroupsWhen tracking a predefined group of URLsZylker – Marketing Campaign Pages
Tracks all URLs inside the defined group

How to Configure

  • Select the appropriate match type.

  • Enter the corresponding URL value.

  • Add multiple conditions if the event can trigger across different sections.

Choose carefully to avoid over-tracking or missing conversions.



Step 4: Add Pages Not to Track ( optional )

If the event may trigger on multiple sections but should not count everywhere:

  • Use Pages Not to Track

  • Apply the same URL match types to define exclusions.

  1. This prevents invalid or inflated conversions.

Step 5: Select or Create the Custom Event
  1. In this step, you define the event that will trigger the conversion.

You can:

Select an Existing Event

Choose from previously created custom events if available.


Create a New Custom Event

  • Type the event name in the input field.
    Example: form_success

  • Click + Create 'form_success'.

The event will now be created and saved.


Once created, the same custom event can be reused across other experiments in PageSense.

The event name must exactly match the name used in your website code.



Step 6: Copy and Implement the Event Tracking Code

After creating the event, PageSense generates a custom event API code.

You must copy this code and paste it into your website’s JavaScript.

The code should be placed inside the function that runs after the action is successfully completed.


For example:

  • Inside the success callback of a form submission

  • Inside an AJAX success response

  • After payment confirmation

  • After backend validation

The event should fire only after the action is successfully completed.

If placed incorrectly, conversions may:

  • Not be recorded

  • Be recorded prematurely

  • Be triggered multiple times

It is recommended to implement this with developer assistance.



Step 7: Review and Launch

Before launching:

  • Confirm page targeting rules

  • Check exclusion conditions (if any)

  • Ensure the event name matches exactly

  • Confirm code is implemented correctly


Once verified, click Launch.

PageSense will begin tracking conversions whenever the event is triggered.


 



We’ve designed this documentation to guide you every step of the way. If you need further assistance or have any questions, don’t hesitate to contact us at support@zohopagesense.com - we’re always here to help!