{"id":20416,"date":"2020-01-30T12:45:49","date_gmt":"2020-01-30T12:45:49","guid":{"rendered":"https:\/\/www.arimetrics.com\/glosario-digital\/event"},"modified":"2026-09-14T10:37:06","modified_gmt":"2026-09-14T10:37:06","slug":"event","status":"publish","type":"encyclopedia","link":"https:\/\/www.arimetrics.com\/en\/digital-glossary\/event","title":{"rendered":"Event"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/www.arimetrics.com\/wp-content\/uploads\/2020\/01\/event.jpg\" alt=\"Event\" class=\"boxpad alignright\" style=\"margin-top:0\" width=\"300\" height=\"300\" \/><strong>Definition:<\/strong><\/p>\n<p>An <strong>event<\/strong>, in digital analytics, is an interaction or occurrence recorded on a website or in an application to measure what happens. It may represent a page view, a click, a purchase or an application error.<\/p>\n<p>Events make it possible to analyse specific actions, beyond counting visits. Not every event corresponds to a deliberate user action: events can also record automated processes or system behaviour.<\/p>\n\n<h2>What events are used for in digital analytics<\/h2>\n<p>Events help you understand how a website or application is used and where a process is completed or interrupted. In a <a href=\"https:\/\/www.arimetrics.com\/en\/digital-analytics-agency-spain\">digital analytics<\/a> project, event selection starts with the questions the business needs to answer.<\/p>\n<p>For example, a store can measure when a product is viewed, added to the cart and purchased. Comparing these steps helps identify where participation drops, although the data alone does not explain why.<\/p>\n<p>Recording more events does not mean having better information. Each event should represent an identifiable action and serve a purpose in the analysis.<\/p>\n<h2>How an event is described<\/h2>\n<p>An event usually includes a name that identifies what happened and additional data that provides context. In Google Analytics 4, this data is called <strong>parameters<\/strong>.<\/p>\n<p>For example, the <code>purchase<\/code> event records a purchase. It can include parameters such as <code>transaction_id<\/code>, which identifies the transaction; <code>value<\/code>, which specifies its value, and <code>currency<\/code>, which identifies the currency.<\/p>\n<p>The name tells you what happened; the parameters describe that particular transaction. There is no need to create a different event name for every product or amount.<\/p>\n<h2>Types of events in Google Analytics 4<\/h2>\n<p><a href=\"https:\/\/www.arimetrics.com\/en\/digital-glossary\/google-analytics\">Google Analytics 4<\/a> uses an event-based measurement model. Events fall into these groups according to how they are collected or defined:<\/p>\n<ul>\n<li><strong>Automatically collected events:<\/strong> recorded when the tool is implemented, such as the start of a session.<\/li>\n<li><strong>Enhanced measurement events:<\/strong> measure certain website interactions when this feature is enabled, such as outbound link clicks or downloads of supported file types.<\/li>\n<li><strong>Recommended events:<\/strong> have names and parameters defined by Google for common actions, such as <code>purchase<\/code> for purchases or <code>generate_lead<\/code> for lead generation. They require an appropriate implementation.<\/li>\n<li><strong>Custom events:<\/strong> defined when the previous groups do not cover the interaction you need to measure.<\/li>\n<\/ul>\n<p>Using a recommended event does not mean it is recorded automatically. Choosing the name and configuring what triggers it are separate matters.<\/p>\n<p>This <a href=\"https:\/\/support.google.com\/analytics\/answer\/9322688?hl=en\" target=\"_blank\" rel=\"noopener\">classification of GA4 events<\/a> helps you check which options cover each requirement before creating your own events.<\/p>\n<h2>The difference between an event and a key event<\/h2>\n<p>A <strong>key event<\/strong> is an event considered particularly important to business objectives and marked as such in GA4. It is not a different interaction: it is a classification that highlights its importance for measurement.<\/p>\n<p>A purchase or a request for a quote can be a key event. A menu click may be useful for studying navigation without having the same business importance.<\/p>\n<p>Marking an event as a key event does not fix its implementation. If it is recorded twice or triggered before the action is completed, it will still produce incorrect measurement.<\/p>\n<h2>Example: measuring a request for a quote<\/h2>\n<p>A company wants to know how many people request a quote through its form. Measuring only clicks on the submit button is not enough: the form could contain errors and fail to submit.<\/p>\n<p>The event should be recorded when the request is confirmed as successfully completed. If this interaction represents lead generation, <code>generate_lead<\/code> can be used and marked as a key event.<\/p>\n<p>Useful information, such as the type of service requested, can also be included without sending names, email addresses or other personally identifiable information to Google Analytics.<\/p>\n<p>This distinguishes between attempting to submit the form and actually completing a request.<\/p>\n<h2>Setting up and checking events<\/h2>\n<p>Events can be implemented through website code, platform integrations or tools such as <a href=\"https:\/\/www.arimetrics.com\/en\/digital-glossary\/google-tag-manager\">Google Tag Manager<\/a>. Applications also use the relevant measurement SDKs.<\/p>\n<p>Before considering an implementation complete, check these points:<\/p>\n<ul>\n<li><strong>Trigger condition:<\/strong> the event is sent when the intended action occurs.<\/li>\n<li><strong>Duplicates:<\/strong> the same interaction does not generate extra records because of an incorrect configuration.<\/li>\n<li><strong>Parameters:<\/strong> the values sent describe the action correctly.<\/li>\n<li><strong>Testing:<\/strong> events appear with the expected data in debugging tools such as GA4 DebugView.<\/li>\n<li><strong>Privacy:<\/strong> data collection respects consent and the restrictions applicable to the data sent.<\/li>\n<\/ul>\n<p>The number of events is not the same as the number of people. A single user can perform the same action several times, so it is important to distinguish between repetitions and users who complete it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Definition: An event, in digital analytics, is an interaction or occurrence recorded on a website or in an application to measure what happens. It may represent a page view, a click, a purchase or an application error. Events make it possible to analyse specific actions, beyond counting visits. Not every event corresponds to a deliberate [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":79325,"template":"","encyclopedia-tag":[1294],"class_list":["post-20416","encyclopedia","type-encyclopedia","status-publish","has-post-thumbnail","hentry","encyclopedia-tag-behavior-measurement"],"_links":{"self":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia\/20416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia"}],"about":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/types\/encyclopedia"}],"author":[{"embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/users\/6"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/media\/79325"}],"wp:attachment":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/media?parent=20416"}],"wp:term":[{"taxonomy":"encyclopedia-tag","embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia-tag?post=20416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}