Event tracking
Event tracking records selected actions on websites or in apps. A clearly defined trigger explains what a counted event actually establishes.
Event tracking records selected actions as events in a measurement system. An event might describe a click, an interaction or a technical operation. Its name and additional parameters define what information is transmitted.
Define the trigger precisely
In a fictional project, a team counts clicks on “Send enquiry”. That number alone does not establish confirmed receipt of the enquiry on the server. If receipt is what needs measuring, the trigger must actually represent that state. Document the event name, trigger, parameters and purpose together.
Check the recording and its meaning
Google Analytics describes events as measurements of interactions or occurrences on websites and in apps. An event arriving in the measurement system and its business meaning need separate checks. Plan test cases for the intended trigger and unwanted duplicate counts. A metric marked as important gains its meaning from its definition and appropriate technical recording.
Sources
Related terms
- UTM parametersUTM parameters label a campaign link with information such as source, medium and campaign.
- Repeat purchase rateRepeat purchase rate is the share of customers who buy again. A report needs an explicit period, customer identity and distinct orders.
- Customer retention rateCustomer retention needs a fixed starting group. A SaaS report must count customers distinctly and separate new accounts from reactivated ones.
- Average order valueAverage order value needs an order-level calculation. An import with multiple line items per order must not inflate the order count.
Articles on this topic



Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.


