The custom event goal is different from the default goals. Default goals are subjected to the main business objective. It includes clicks on links, elements, page visits, page engagement, and form submission. Unlike default goals, custom event goals track elements other than page views and clicks.
Why need a custom event goal?
A site’s conversion rate depends on the various conversion goals, that are set based on the business requirement. A website may have certain elements that have a significant impact but do not contribute to the conversion rate of a site. Still, a need arises to track those elements.
Examples of Custom Event Goals
- When you sign-up on a website, a pop-up appears with two options. While one option routes the user to the dashboard, the other takes you to verify the account. Verification is not mandatory for every signup. However, verification adds security to your account. You can bind the custom event to the verification process and track this event.
- AJAX form submits that load elements dynamically.
- To identify drop-offs in form submission and get insights on fields that triggered the user to leave. You can bind the event to the actions taken in specific input fields.
Adding Custom Event Goal
To add a custom event goal,
Go to WEB ANALYTICS AND MANAGEMENT > A/B Testing.
Choose an experiment and click Pause.
Click on the paused experiment to open it.
Click the Edit Experiment button.
Click the Goals tab > + Add another goal
Choose the metric to be measured:
Enter the event name. Freshworks CRM identifies the event and generates an HTTP request.
Note: 1) The Custom event is essentially a call to the Freshworks CRM JS snippet. 2) Now the Freshworks CRM JS snippet has to be integrated into the page, where the custom event is triggered.
Custom Event Goal as Primary Goal
To set the custom event goal as a primary goal, click the ‘Set as primary goal’ link. The goal that is set as primary is indicated by:
Note: By default, the first goal is set as the primary goal.