What is an event in web analytics?

Your report doesn't understand your customer. That part is your job.

Data isn't smart. Only the way you read it can be. An event isn't a sale. It's a trace. Let's learn to read it.

Zarezerwuj termin na bezpłatne naprawcze konsultacje.

Book a free call

An event is not an intention. An event is just a trace.

The most common mistake: confusing events with results

I wrote this for people in e-commerce who look at reports regularly, see „events”, „user actions” and „funnel steps”, but aren’t sure how to read them in business terms.
It’s for store owners, PMs and agency clients who don’t want to know how something gets implemented, only how to understand it and what to ask.

This article:

  • explains what an event is as a record of customer behavior,
  • sorts out how to think about events vs. conversions,
  • shows where wrong conclusions are most often born,
  • gives you the words for a conversation with an analyst or an agency.

On purpose, it does not solve:

  • data quality problems,
  • implementation bugs,
  • or the question „what exactly should I fix in my store”.

If after reading you feel:
„OK, I get the problem, but I still don’t know where exactly it sits in my store”,
that is the moment when you need a deeper analysis, not another article.


Event: what it really means in business practice

The simplest and most honest version:

An event is a record of a specific action a user took in the store.

Not an intention.
Not traffic quality.
Not a verdict on whether something „worked”.

It’s a dry piece of information: what the user did at a given moment.

If someone:

  • added a product to the cart,
  • checked the shipping cost,
  • changed the variant,
  • compared two products,

then each of those actions leaves a trace.
That trace is the event.

Analytics systems such as Google Analytics 4, Google Ads or the Meta Pixel don’t „understand” the user.
They only record the traces.

All the interpretation happens later, on the business side.

That’s where it gets slippery.


What an event is not, and why the difference has real consequences

An event is not a conversion.
This isn’t hair-splitting. It changes how you read every report.

A conversion is your business decision that a given action carries special weight for you.
An event is only a record of a fact.
You save that decision in the interface: how to set up a conversion in GA4.

A purchase is an event.
Adding to cart is an event too.
So is checking the shipping cost.

The trouble starts when we treat events as „almost results” instead of a tool for spotting the steps where users drop out of the buying process 2.

In analytics practice this is one of the most common mistakes:
companies look at add-to-carts or checkout starts as proof that their marketing works.

But those are the middle of the decision process, not its ending.

By tracking events, you can find the step where users abandon the buying process 2.


The first real observation from practice: overrating events that look „close to a purchase”

We hear sentences like this very often:

„Traffic is fine, add-to-carts are growing, but sales aren’t. Something’s wrong with the conversion.”

At first glance it sounds logical.
In practice it’s the wrong diagnosis.

Adding to cart doesn’t mean the user had made up their mind to buy.
Very often it means:

  • they wanted to see the full price,
  • they were comparing it with another offer,
  • they were saving the option „for later”.

If you treat this event as „almost a sale”, you start overrating traffic quality and underrating the problems that show up later.

The business consequence:
instead of fixing the real barriers in the decision process, you pour more budget into the spot where users already hit a wall. Where to look for those barriers is something I describe in the article why an online store isn’t selling despite Google Ads.

Keep in mind that for the purchase event to give you full analytical value, it should include transaction parameters such as a unique transaction ID, purchase value, currency, product details and extra information (for example coupons, shipping costs, taxes) 1.


The second observation: ignoring the events that say the most

The paradox is that the events that look least impressive in reports are often the most informative.

Comparing products, switching variants, filtering the catalog or checking shipping costs often get dismissed as „noise”.

Yet these are exactly the events that show:

  • where the user hesitates,
  • what they’re missing to decide,
  • at which point they have to fill in the blanks on their own.

Ignoring them leads to decisions based only on the end of the path, without understanding why the path breaks off in the first place.


An example of a wrong conclusion and what it leads to

Take this line of thinking:

„Lots of users check the shipping cost, so the product price is fine.
The problem must be the ad.”

It’s a conclusion that sounds reasonable, but it doesn’t follow from the event.

The „checked shipping cost” event says only one thing:
at this moment the user needs the full cost to move on.

It doesn’t say whether the price is acceptable.
It doesn’t say whether shipping is expensive.
It says nothing about the quality of the campaign.

If you change your ad messaging or raise the budget based on a conclusion like that, you can spend months optimizing something that isn’t the source of the problem.


Where an event’s job really ends

Events aren’t supposed to answer everything.
Their job is to show where the user makes decisions, and where they back out of them.

If:

  • you see a lot of activity but don’t understand what it means,
  • the events „look nice” but don’t add up to a story,
  • the reports show traffic, but not decisions,

then the number of events isn’t the problem.
It’s a signal that you need interpretation in the context of the whole buying process, not another metric.


One position worth remembering

Events aren’t there to prove that „something works”.
They’re there to help you understand why the user does what they do, and why they stop going further.

And here’s the sentence that ties it all together:

If you only look at purchases today, you don’t know why they’re missing.

Events exist so you can finally see it, before you make your next business decision.

How to go from GA4 events to decisions about budget and the website is something I show with two cases in the article GA4 events and business decisions. And if you’d like me to check what your store really measures, here’s what analytics and tracking setup looks like.


Footnotes:

Author - Michał Wojciechowski

Who writes this?

I have run Google Ads accounts myself since 2019 and I create the ads and copy for them. I have run campaigns on 9 markets and worked on projects on 8 more.

I started in graphic design and film, so I look at an ad the way a viewer does. I work directly with business owners: regular calls, decisions based on data, and work on the offer and the landing page, not only on the ads.

Michał Wojciechowski

Campaign not working?

One hour on a call is usually enough to see why the sales are not coming in.