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 submit. 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 Goal
- Consider when a user sign-ups, a pop-up appears with two options, one takes the user to the dashboard and the other to verify the account. Verification is not mandatory for every sign up. But verification adds security to an account. You can bind the custom event to the verify process and track this event.
- AJAX form submit that loads elements dynamically.
- To identify drop-offs in form submission and get insights on fields which triggered the user to leave. You can bind the event to the actions taken in specific input fields.
Adding Custom Event Goal
Adding New Custom Event Goal
The Custom event is essentially a call to the Freshmarketer JS snippet. Now the snippet identifies the event (Eg: eventName) and generates appropriate HTTP request.
Freshmarketer JS snippet has to be integrated into the page, where the custom event is triggered.
To set the custom event goal as a primary goal, click the icon. The goal that is set as primary is indicated by:
NOTE: By default, the first goal is set as the primary goal.