Stape
Tracking e dados
Alojamento e ferramentas para Google Tag Manager server-side
- To verify
- Free plan
Measure · Custom events
Ecommerce events tell you what was bought. Custom events help explain why: which filters people use, which searches return nothing, where checkout fails. I define and implement the ones that genuinely matter to your store.
In short
I define and implement custom GA4 events for WooCommerce stores, beyond the standard ecommerce events. Examples include filter use, site searches with no results, coupon or payment errors at checkout, newsletter sign-ups and size guide clicks. It is for stores that want to understand visitor behaviour and feed tests, audiences and UX decisions with data.
Every click is tracked, but nobody knows what for. Reports fill up with useless events and the handful that matter get lost.
The same behaviour shows up as ‘newsletter_signup’, ‘Subscription’ and ‘form_submit’. Without a convention there is no way to aggregate or compare over time.
Events carry useful parameters, but they were never registered as custom dimensions in GA4, so they don't appear anywhere.
Every event starts with a business question and a decision the data will support. From there I set the name, parameters and trigger, follow a consistent convention and register in GA4 only the dimensions that will actually be used.
A table listing each event, the question it answers, its parameters, trigger and where it will be used.
Tags, triggers and variables set up in Google Tag Manager following the agreed convention.
Relevant parameters registered as dimensions or metrics so they can be used in reports and audiences.
GA4 explorations or Looker Studio pages that present the new events in a way your team can use.
A reference document of every active event, so future requests follow the same logic.
I meet your team to list the questions about visitor behaviour the data should answer.
I turn those questions into events, parameters and triggers, and agree the plan with you.
I implement in GTM, test in preview mode and DebugView, and register the dimensions in GA4.
Once enough data has come in, I prepare a first analysis and adjust whatever needs it.
It depends on your questions. Common ones include site search, especially searches with no results, filter use, coupon or payment errors, views of the size guide or delivery costs, and newsletter sign-ups. I always start from the questions rather than a fixed list.
There are limits on event names, parameters and registered custom dimensions per property, which Google documents and may change. In practice the bigger risk isn't the technical limit but tracking so much that the useful data becomes hard to find.
Yes, for example as secondary conversions or to build audiences. I advise against using micro-conversions as the main bidding goal for an online store, because the algorithm will optimise for that action rather than for sales.
Tracking e dados
Alojamento e ferramentas para Google Tag Manager server-side
Some links are affiliate links: if you sign up, I may earn a commission at no extra cost to you. It never changes my assessment. How this works

Customer Acquisition
Revenue is the number everyone celebrates: it climbs on the dashboard, it looks good in a board update, and it makes growth…
· 7 min read

Campaign Strategy
Most ecommerce teams have no shortage of website data. What they lack is a method for turning it into decisions. Dashboards fill…
· 7 min read

Campaign Strategy
Every conversion rate optimisation audit produces the same problem: a long list of things that could be improved and no obvious way…
· 7 min read
Book a discovery call. We will start from your questions and I will suggest which events would make a difference in your store.