Event tracking shows what people actually do on a website after they arrive. Page views can tell you which pages were loaded, but they do not tell you whether someone clicked a quote button, started a form, opened a phone link, downloaded a document or moved deeper into a buying journey.
This guide focuses on the planning and checking side of website event tracking. It is written for businesses that want better evidence before making decisions about PPC tracking, SEO content, landing pages or paid social campaigns.
What is event tracking?
Event tracking is the process of recording important user interactions in a measurement tool such as GA4, Google Tag Manager, Google Ads, Meta Pixel or a reporting dashboard. The goal is not to track everything. The goal is to track the actions that help you understand intent, quality and commercial value.
- Button clicks: Tracking calls to action, such as quote, contact, booking or checkout buttons.
- Form submissions: Monitoring how often users complete forms.
- Link clicks: Understanding the effectiveness of internal or external links.
- Video interactions: Recording when users play, pause, or finish watching a video.
- Downloads: Tracking file downloads, such as PDFs or software.
- Scroll depth: Measuring how far down a page users scroll.
- Mouse hover: Capturing mouseover events on particular elements.
By monitoring these interactions, you can see whether traffic is producing useful behaviour. That matters when you are judging ad spend, page quality, calls to action or whether a page is doing enough to help a visitor take the next step.
What should you track first?
Start with the actions closest to a real enquiry or sale. For a service business, this usually means completed contact forms, phone number clicks, quote button clicks, email link clicks and booking actions. For ecommerce, it may include product views, basket additions, checkout starts and purchases.
Secondary events can still be useful, but they should not be treated as equal to real leads. Scroll depth, video plays, accordion opens and content downloads can help you understand engagement. They are weaker signals unless you can show that they regularly lead to better enquiries.
A simple event plan might group actions into three levels:
- Primary conversions: actions that represent a lead, purchase, booking or other valuable outcome.
- High-intent events: actions that show strong interest, such as quote button clicks, pricing page clicks or phone link taps.
- Engagement events: useful behaviour such as downloads, video plays, scroll depth or guide interactions.
Why is Event Tracking Important?
Event tracking goes beyond simply monitoring user sessions and page views. It offers detailed insights that are vital for improving both user experience and website performance. Here are several key reasons why event tracking is important:
1. Optimise Conversion Paths
By understanding which elements users interact with the most, you can optimise conversion funnels. For example, tracking which CTAs (call-to-action buttons) generate the most clicks can inform you about the placement and design of those elements. You can adjust your layout to highlight the actions that lead to the highest conversions.
2. Measure Engagement
Page views alone don’t tell you how engaged your audience is. Event tracking provides a more nuanced view by capturing data on actions like video plays, file downloads, or clicks on outbound links. This data helps you understand how well your content is performing and whether it resonates with your audience.
3. Improve User Experience
By analysing the events on your website, you can discover user pain points. For instance, if you notice a high number of form starts but few form completions, this could signal that the form is too long or confusing. This kind of information is invaluable for refining the user experience and addressing potential barriers to engagement.
4. Data-Driven Decision Making
Event tracking empowers you to make informed decisions based on actual user behaviour rather than assumptions. It helps answer important questions, such as which pages users are most likely to drop off, or which promotional banners are most effective.
5. Monitor Key Performance Indicators (KPIs)
For businesses, tracking KPIs such as click-through rates, bounce rates, or conversion rates is essential. Event tracking provides a mechanism to tie user interactions directly to business goals, making it easier to measure the success of specific strategies.
Plan events before setup
Good event tracking starts before anyone adds tags. Write down the action, where it happens, what it should be called, whether it is a primary conversion and where the result needs to be reported. This prevents a messy account full of similar events such as button_click, contact_click and click_contact_us that all mean different things.
Keep event names plain and consistent. A name such as generate_lead or quote_button_click is easier to understand than a vague label such as cta_1. Add useful context with parameters, such as the page, button label, form type or service category.
For paid search, make sure the tracked actions match the decision you want to make. If a campaign is being judged on leads, completed forms and qualified calls matter more than every button click. Our PPC management services page explains how conversion quality should feed into campaign decisions rather than being treated as a vanity metric.
Event tracking plan checklist
- Event name: a clear name that can be understood in reports.
- Trigger: the click, form submission, page view, download or interaction that should fire the event.
- Value: whether the event should count as a conversion, a supporting signal or a diagnostic event.
- Reporting destination: GA4, Google Ads, Meta, Looker Studio, CRM, spreadsheet or another reporting setup.
- Test action: the exact action you will take to confirm the event fires once and carries the right detail.
Understand the event structure
In GA4, events are usually built around an event name plus optional parameters. The event name describes what happened. Parameters add context such as the page, button text, link URL or form name.
- Event name: the main action, such as form_submit, phone_click or file_download.
- Parameters: supporting detail, such as page location, link text, form ID or service area.
- Conversion setting: whether the event should be treated as a key business action.
- Source reporting: whether the event needs to be imported into Google Ads, Meta or another platform.
Older analytics setups often used category, action and label fields. If your reports still use those terms, translate them into a clear GA4 structure before making new changes.
Avoid tracking noise
It is tempting to track every possible interaction, but too much data can make reports harder to use. Before adding a new event, ask whether it will change a decision. If the answer is no, keep it out of the main reporting view or treat it as a diagnostic event only.
GA4 or Google Tag Manager?
Some events can be measured directly in GA4, especially enhanced measurement events such as scrolls, outbound clicks, file downloads and video engagement. More specific events often need Google Tag Manager, custom site code or help from the platform that powers the form, booking tool or ecommerce checkout.
Google Tag Manager is usually the better choice when you need to track clicks on specific buttons, pass extra context into GA4, send the same action to more than one platform or update tags without asking a developer to edit the site each time.
Direct implementation can still be right for some websites. Ecommerce platforms, booking tools and custom applications may need developer-led events so the data is accurate and not dependent on fragile button selectors.
When Google Tag Manager helps
- You need to track several buttons, forms or outbound clicks across the site.
- You want one action to be sent to GA4, Google Ads and Meta.
- You need to test changes in preview mode before publishing.
- You want clearer control over triggers, variables and consent settings.
How to Set Up Event Tracking in GA4 (Step by Step)
GA4 records many events automatically, but the ones that matter most – enquiries, calls and form submits – usually need setting up. Here is the simplest route:
- Turn on Enhanced Measurement. In GA4, go to Admin > Data streams and open your web stream, then switch on Enhanced Measurement. This captures page views, scrolls and outbound clicks with no code.
- Create the event. For a custom action, use Admin > Events > Create event, or mark an existing event so you can use it later.
- Mark it as a key event. In Admin > Key events (formerly Conversions), toggle the event so GA4 and Google Ads treat it as a goal.
- Link Google Ads. Under Admin > Product links > Google Ads, connect the account so your key events can be imported as conversions.
Setting up an event with Google Tag Manager
For clicks, form submits and anything GA4 cannot see on its own, Google Tag Manager (GTM) is the flexible option:
- Add the GTM container to your site (or through a plugin), then create a GA4 Configuration tag so GTM talks to GA4.
- Create a trigger for the action – for example a Click trigger on your “Call now” button, or a Form Submission trigger.
- Create a GA4 Event tag, give the event a clear name such as
generate_lead, and attach your trigger. - Preview and publish. Use GTM’s Preview mode to watch the tag fire, then publish the container.
Common events to track (checklist)
- Contact form submitted
- Phone number clicked (click-to-call)
- Email address clicked
- Quote or booking request completed
- Add to basket, and checkout started or completed
- Key button clicks (for example “Book a call”)
- File or brochure downloaded
- Outbound clicks to booking or partner sites
How to verify event tracking
Verification is the step that protects you from bad decisions. An event should not be marked as a conversion, imported into Google Ads or used in a report until someone has tested it on the real website journey.
Use preview or debug tools to check that the event fires when it should, does not fire when it should not, and passes the right information into the reporting platform. If the same enquiry can happen through a form, phone click and quote button, test each route separately.
Verification checklist
- Trigger check: the event fires from the intended action only.
- Duplicate check: one user action does not produce two or more conversion events.
- Parameter check: the page, button label, form name or source detail is passed correctly.
- Platform check: GA4, Google Ads, Meta or the reporting dashboard receives the event.
- Consent check: the event respects the consent setup and privacy requirements for the site.
- Business check: the event is useful enough to influence reporting, budgets or page improvements.
If you are already running ads, connect this check to your paid media reporting. The aim is to understand which campaigns generate valuable enquiries, not just which campaigns generate the most clicks. For Meta campaigns, the same thinking applies to Pixel and conversion events; our Facebook Pixel guide explains the wider role of that data.
Useful event tracking ideas
Once the primary events are reliable, you can add supporting events that answer specific questions. These should help you improve pages, campaigns or reporting rather than simply making the analytics account look busy.
1. Custom dimensions and metrics
You may want to pass extra detail that is specific to the business, such as service type, enquiry route, customer type or landing page group. This can make reporting more useful when you need to compare the quality of different campaign or content routes.
For example, a web design enquiry could carry a page category such as website design, ecommerce, SEO or PPC. That makes it easier to see which routes generate the most useful leads.
2. Tracking scroll depth
Scroll depth tracking can help you understand whether people reach key sections of a long guide, pricing page or landing page. It is most useful when you compare it with other actions, such as quote clicks or form starts.
If a page gets traffic but few people reach the call to action, the page may need a clearer opening, better internal links or a stronger route into the next step.
3. Outbound link tracking
Outbound link tracking is useful when important actions happen away from the website, such as booking portals, payment platforms, document downloads, support systems or third-party quote tools.
For Corsto, this is especially relevant where a visitor moves from the main website into a quote route such as the paid advertising quote form.
4. Single page application views
If a website or app changes content without loading a new URL, normal page-view reporting may miss important steps. In that case, virtual page views or screen-view style events can help show how people move through the experience.
This needs careful setup so reports do not inflate page views or hide the difference between a real page load and an in-page state change.
5. Ecommerce event tracking
For ecommerce websites, tracking events related to transactions is essential. Google Analytics provides enhanced ecommerce tracking, which allows you to capture detailed information about user interactions with products, from viewing products to completing a purchase.
Ecommerce event tracking usually needs platform-specific setup, custom code or a tested plugin. With the right setup, you can compare product views, basket additions, checkout steps and purchases without guessing where buyers drop out.
Common event tracking issues
Most tracking problems are not dramatic. They are small mismatches between the action, the trigger and the report. The important part is finding them before they affect campaign decisions.
1. Events Not Showing in Google Analytics
If events are not showing up in GA4 or your reporting platform, check the trigger, consent state, browser blocking, publishing status and whether you are looking at the right property or data stream.
- Preview the action: use preview or debug mode and take the same action a real visitor would take.
- Check real-time reporting: confirm the event appears in the right property, stream and report.
- Check the selector or condition: make sure the trigger matches the actual button, form or link on the live page.
2. Duplicate Events
Sometimes events fire more than once. This can happen when a tag is attached to the wrong element, a thank-you page reloads, a form submits through more than one route or the same action is tracked in both site code and Google Tag Manager.
To avoid duplicate events:
- Make sure each important action has one clear trigger.
- Use stable selectors, form IDs or destination URLs where possible.
- Test the action more than once and check whether repeated form refreshes create extra conversions.
3. Event Data Not Categorised Correctly
If events are hard to understand in reports, the naming structure probably needs work. Use names and parameters that match how the business thinks about enquiries, channels and services. Do not make a future report reader decode a private naming system.
Use cases for event tracking
Event tracking is most useful when it connects a user action to a business question. These are common examples where the data can make a practical difference.
1. Lead Generation Websites
For lead generation websites, it’s essential to track how users engage with forms, buttons, and CTAs. By setting up event tracking for form submissions, button clicks, and even interactions with chatbots, you can gain insights into how leads are generated and optimise the paths users take to convert.
Example: a website design or marketing agency can track quote button clicks, enquiry form completions, call clicks and support-system handoffs. If quote clicks are high but form completions are low, the problem may be the form, the offer or the expectation set on the page.
2. Ecommerce Websites
For ecommerce businesses, tracking user interactions is critical for understanding the purchasing process. In addition to tracking purchases, event tracking can help monitor key actions like adding products to the cart, viewing product details, and applying discount codes.
Example: an online shop can compare product views, add-to-basket actions and checkout starts to find the point where buyers lose confidence. That evidence can support better product pages, shipping information or checkout changes.
3. Content-Driven Websites
For content-heavy websites like blogs or news sites, event tracking can help you understand how users engage with your articles, videos, and other media. Tracking scroll depth, social sharing buttons, and video plays can offer valuable insights into content consumption patterns.
Example: a guide or resource page can track whether readers reach the section with a quote route, related service link or next-step button. That can show whether internal links are helping readers continue their journey.
4. Paid advertising landing pages
Paid advertising landing pages should track primary conversions and supporting events. A page may generate a strong click-through rate from ads but still fail if visitors do not click the form, phone link or next-step button.
Example: if paid traffic clicks a quote button but does not complete the form, the campaign may need a landing page change before more budget is added. This is where event tracking connects directly with Facebook Ads management, Google Ads and landing-page optimisation.
Next step
If you are already investing in ads or planning to do so, review the events before you judge campaign performance. Check that the right conversions are being tracked, that duplicate events are not inflating results and that reports separate real enquiries from softer engagement signals.
Corsto can help plan the measurement side alongside PPC, Meta ads and landing-page improvements. Start with a paid advertising quote if you want the tracking, campaign and reporting work joined up properly.
