Products Solutions Templates Pricing Resources

Custom event setup: tracking actions that matter to your business

Home / Everything About / Everything About Analytics / Custom event setup: tracking actions that matter to your business

Your analytics system knows when someone visits a page. It knows how long they stayed and where they came from. But it does not automatically know when a visitor clicked your pricing button, watched your demo video, or downloaded your product guide. Those actions matter more than pageviews for most businesses.

Custom event setup bridges that gap. You define which interactions to track, configure the tracking rules, and start collecting data on the behaviors that connect visitor activity to business outcomes. Done well, custom event tracking turns a generic analytics setup into a measurement system built around your goals.

What custom events are and why they matter

A custom event is a tracked interaction you define beyond the default pageview and session data. Every event has a name that describes the action and optional parameters that add context.

Clicking a call-to-action button might fire an event named cta_click with a parameter showing which button was clicked. Submitting a contact form might fire form_submit with a parameter for the form type. Starting a video might fire video_start with the video title attached.

Without custom events, your analytics shows traffic but hides intent. You see five hundred visitors on your pricing page but cannot tell how many clicked the buy button. With custom events, you see the full picture. Traffic plus action plus outcome.

Choosing which events to track

The temptation is to track everything. Resist it. Too many events create noisy data that nobody reviews. Start with the actions that directly connect to your business goals.

Ask one question: what do visitors need to do on my website for my business to succeed? For a service business, that might be submitting a contact form or booking a call. For an online store, adding to cart and completing checkout. For a content site, signing up for a newsletter or downloading a lead magnet.

List five to ten actions maximum for your initial setup. You can add more later once these core events are tracking reliably and you are actually using the data.

High-value events most websites should track

Form submissions are the most common custom event for lead-generation sites. Track each form separately if you have multiple forms with different purposes.

Button and link clicks on key calls to action reveal whether visitors engage with your most important prompts. Track clicks on primary buttons, not every link on the site.

File downloads show which resources visitors value. Track PDF downloads, template downloads, and guide downloads separately.

Scroll depth on long-form pages and video interactions reveal whether visitors engage deeply with your content rather than skimming and leaving.

How custom event tracking works technically

Custom events require a trigger and a tag. The trigger defines when the event fires. The tag sends the event data to your analytics system.

A click trigger fires when a visitor clicks a specific element. A form submission trigger fires when a form is successfully submitted. A scroll trigger fires when a visitor reaches a defined depth on the page. A visibility trigger fires when an element enters the viewport.

When the trigger condition is met, the tag sends an event with a name and any parameters you configured. The analytics system records the event and makes it available in your reports.

In WEMASY, much of this configuration happens through the built-in analytics interface. You select the interaction type, define the event name, and the system handles the technical implementation on your pages.

Setting up your first custom events

Follow a consistent process for every event you create. Skipping steps leads to duplicate events, missing data, and reports you cannot trust.

Step 1: Define the event clearly

Write down the event name, what action triggers it, and what parameters you need. Example: event name contact_form_submit, triggered when the main contact form is successfully submitted, with a parameter for form_location set to the page URL.

Step 2: Check if automatic tracking already covers it

Before creating a custom event, check whether enhanced measurement or automatic tracking already captures the interaction. Scroll depth, outbound link clicks, and file downloads often track automatically. Creating a duplicate custom event for something already tracked doubles your data and confuses reports. See our guide on enhanced measurement to see what your system may already handle.

Step 3: Create the trigger and tag

Configure the trigger conditions in your tag management or analytics settings. Match the trigger precisely to the interaction. A click trigger on a CSS class is more maintainable than one on a specific element ID that changes when you edit the page.

Step 4: Test before going live

Trigger the event yourself and confirm it appears in your real-time reports. Submit the form. Click the button. Download the file. Verify the event name and parameters are correct. Testing takes five minutes and prevents weeks of bad data.

Step 5: Document what you created

Document every custom event in a tracking plan with event name, trigger, parameters, and date created.

Naming conventions that keep your data clean

Event names should be consistent, descriptive, and lowercase with underscores. Use form_submit instead of Form Submit or formSubmit. Use cta_click instead of Button Clicked or click1.

Consistent naming makes filtering and reporting straightforward. When every form event starts with form_, you can pull all form data with a single filter. When names are random, you spend time deciphering your own reports.

Our guide on event naming structure provides a full framework for naming events and parameters across your entire analytics setup.

Using custom event data in decisions

Custom events become valuable when you connect them to decisions. Look at event counts alongside traffic data. If your pricing page gets two hundred visits per week but only five cta_click events, the page attracts attention without driving action. That is a clear signal to improve the call to action.

Compare event rates across traffic sources. If email visitors submit forms at three times the rate of social visitors, your email audience is more qualified.