Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Analytics · 17 Nov 2026 · 7 min read

Analytics events vs conversions: what to count as a win

Your tracking records many actions. Only a few of them mean the business gained something. This guide helps you separate the two.

The short answer

An analytics event is any action your tracking records, such as a click or page view. A conversion is an event you have chosen because it signals a business result, like a paid order or a sent enquiry. Record many events, mark only two or three outcomes as conversions, and test each one before you trust the reports.

Analytics events and conversions: the difference

Analytics events are the individual actions your tracking records, such as a page view, a click on a button, a video play or a form submission. A conversion is an event you have decided matters to the business. Every conversion is an event, but most events are not conversions.

That distinction sounds small, yet it decides what your reports say. If every click is marked as a win, the dashboard looks healthy and tells you nothing. If only the final sale is counted, you may miss the earlier steps that explain why people leave. The job is to record plenty of events and to mark very few of them as conversions.

Different tools use different names for these ideas, and the names change from time to time. Check the current documentation for your own tool before you copy a setup from another site. The principle stays stable: record actions, then choose the ones that stand for progress.

A simple way to sort events

Think of events in three layers. Sorting yours this way is quick with a spreadsheet and saves many arguments later.

LayerWhat it showsExamplesMark as conversion?
ContextHow people move aroundPage views, scroll depth, menu clicks, video playsNo
InterestA visitor is leaning inPricing page viewed, brochure opened, product added to basket, calculator usedSometimes, as a secondary goal
OutcomeThe business gains somethingEnquiry sent, booking made, order paid, subscription startedYes

Most small sites need only two or three outcome events. A consultancy might count a completed contact form and a booked call. A shop might count a paid order and a newsletter sign-up. A charity might count a donation and a volunteer application. The right list comes from what the business actually wants, not from what the tool makes easy to count.

Which events are worth marking as conversions

Mark an event as a conversion when it meets three conditions. It happens after a deliberate choice by the visitor, it is close to revenue or to a real business result, and you would change what you do if the number rose or fell.

Apply those conditions to common candidates:

  • A completed enquiry form passes. A click on the "Contact" menu item does not, because it only shows that the person looked.
  • A paid order passes. Adding to the basket is a useful interest event, but it is not an outcome.
  • A newsletter sign-up passes if the list is part of your plan. Otherwise keep it as an interest event.
  • A click on a phone or email link passes for service businesses, with a note that it records intent to contact, not a finished conversation.
  • Scrolling to the bottom of a page fails. It is easy to trigger and says little.

Give each conversion a rough value if you can defend one, or leave the value blank. An invented value makes reports look precise when they are not. If someone asks what an enquiry is worth, you can work that out separately from your own sales records.

The funnel gives a useful frame for where each event sits. Our explanation of the marketing funnel describes awareness, consideration and decision stages, and you can attach one or two events to each stage.

Naming events so you can still read them next year

Names are easy to ignore and expensive to fix. Pick a pattern and keep to it. A common approach is object followed by action, in lower case with underscores, for example form_submit, quote_request or checkout_start. Write the pattern in a shared document, along with who set up each event and why.

Avoid names that describe the page rather than the action, such as thank_you_page_visit when form_submit would do. Avoid names that mix languages or abbreviations only one person understands. If a team member leaves, the next person should be able to read the list and understand it in a few minutes.

Keep a short log of changes. When you add a conversion, change a form or rebuild a page, write down the date. A sudden jump or drop in a chart often has a boring cause such as a duplicated tag, and the log lets you find it quickly.

How to check that events fire correctly

A tracking setup is only as good as its testing. Run through these steps after any change to a page, form or tag.

  1. Use the preview or debug mode your tracking tool provides, and complete the action yourself on a real device.
  2. Confirm the event appears once, not twice. Double counting is common when a tag is installed both in the page code and in a tag manager.
  3. Check the event carries the right details, such as the form name or product category.
  4. Submit a test enquiry or test order, then look for it in the live or real-time view of your reports and in your own inbox or shop system.
  5. Repeat on a phone, since mobile layouts sometimes use different buttons and forms.
  6. Try it with a content blocker or after declining cookies, to see how consent choices change what is recorded.

Compare the totals against a source you trust. If your reports show a certain number of enquiries last week, your inbox or CRM should show roughly the same. A large gap means something is firing wrongly or failing to fire. Small gaps are normal, because some visitors decline tracking and some browsers limit it.

Consent and privacy rules affect what you may record and how you must ask. They differ by country and change, so ask a qualified lawyer or read the official guidance for each place you operate, and keep the setup in line with your cookie and privacy notices.

Common mistakes that spoil the numbers

Several mistakes appear again and again on small sites.

  • Counting the thank-you page and the form submission as separate conversions, so one enquiry counts twice.
  • Including your own visits and your team's test orders, which inflate the total. Filter them out where the tool allows.
  • Changing the definition of a conversion midway through a campaign, then comparing before and after as if nothing moved.
  • Marking a dozen events as conversions, so the headline figure no longer relates to anything the business cares about.
  • Reading a single week as a trend. Small sites have noisy data, and a handful of enquiries can swing a percentage a long way.

Our guide to getting started with email marketing for a small business shows one place where this matters in practice: a sign-up counted at the form is not the same as a subscriber who confirms and reads. Decide which of those is your conversion before you build the report.

Using events to build audiences and judge campaigns

Events do more than fill a report. Many ad platforms can build audiences from the actions people take on your site, such as everyone who viewed a product but did not buy. That is the basis of remarketing, covered in retargeting explained for small businesses and in the more detailed retargeting basics guide. The events you choose to record become the groups you can reach later, so name and test them with that in mind.

Events also help you judge work that is hard to measure from sales alone. If a creator or partner sends traffic to your site, the events show what those visitors did when they arrived. The guide to influencer collaborations shows where a tracked link and a clear conversion fit into a partnership brief.

If you would like help deciding what to track and setting it up properly, the digital marketing service page explains what Liftup Technologies works on. A good first step either way is a one-page list: three outcome events, five interest events, and a note on who checks them each month.

Related guides

Questions and answers

What is the difference between an event and a conversion?

An event is any action your analytics tool records. A conversion is an event you have chosen to count as a business result. A button click is an event. A paid order or a submitted enquiry is a conversion. Every conversion is an event, but most events are not conversions.

Which events are worth marking as conversions?

Pick events that follow a deliberate choice, sit close to revenue or a real outcome, and would change your decisions if they moved. Completed enquiries, paid orders and confirmed bookings usually qualify. Scrolling and menu clicks usually do not.

How do I check they fire correctly?

Use your tool's preview or debug mode and complete each action yourself on desktop and phone. Confirm the event appears once, carries the right details and matches your inbox or order records. Repeat the test after any change to a form, page or tag.

How many conversions should a small site track?

Two or three outcome events are enough for most small sites. More can be tracked as secondary interest events, but a long list of conversions makes the headline number meaningless and hides the changes you care about.

Why do my analytics and my inbox show different numbers?

Small gaps are normal because some visitors decline tracking and some browsers limit it. Large gaps suggest an event is firing twice, failing to fire, or counting your own test visits. Check each step with the preview mode and filter internal traffic.

Should I give conversions a money value?

Only if you can defend the figure from your own sales records. An invented value makes reports look precise when they are not. Leaving the value blank is acceptable, and you can estimate worth separately outside the analytics tool.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote