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
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.
Imagine you have a contact form on: https://example.com/contact-us
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.
URL Match Type | When to use | Example | What it tracks |
Simple URL | When tracking a single static page | Only that specific page | |
Exact URL | When the URL must match exactly | Tracks only the exact URL entered | |
URL contains | When tracking multiple related options | Tracks all URLs containing “/product” | |
Starts with | When tracking a section or a folder | Tracks all blog pages | |
Ends with | When tracking pages with a common ending | Tracks any URL ending in ''thank-you'' | |
Matches with | For flexible partial matching | https://zylkerautomation.zohocommerce.com/offer | Tracks URL matching similar patterns |
| Regex | For dynamic or complex URL structures | Tracks product pages with numeric IDs | |
| Page Groups | When tracking a predefined group of URLs | Zylker – Marketing Campaign Pages | Tracks all URLs inside the defined group |
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.
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.
You can:
Choose from previously created custom events if available.
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.
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.
Before launching:
Confirm page targeting rules
Check exclusion conditions (if any)
Ensure the event name matches exactly
Confirm code is implemented correctly
PageSense will begin tracking conversions whenever the event is triggered.
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
All-in-one knowledge management and training platform for your employees and customers.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.